IJS20110167287A1
`
`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2011/0167287 A1
`Walsh et al.
`(43) Pub. Date: Jul. 7, 2011
`
`
`(54)
`
`PROVIDING POWER TO AN ACCESSORY
`DURING PORTABLE COMPUTING DEVICE
`HIBERNATION
`
`(75)
`
`Inventors:
`
`Robert Walsh, Sunnyvale, CA
`(US); Jeff Terlizzi, San Francisco,
`CA (US); Jahan Minoo, San Jose,
`CA (US); Lawrence G. Bolton,
`Fremont, CA (US)
`
`(73)
`
`Assignee:
`
`Apple Inc., Cupertino, CA (US)
`
`(21)
`
`Appl. No.:
`
`12/793,364
`
`(22)
`
`Filed:
`
`Jun. 3, 2010
`
`Related US. Application Data
`
`(60)
`
`Provisional application No. 61/292,626, filed on Jan.
`6,2010.
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`G06F 1/32
`G06F 1/26
`
`(2006.01)
`(2006.01)
`
`(52) U.S.Cl. ......................................... 713/323;713/300
`
`(57)
`
`ABSTRACT
`
`A portable computing device (PCD) can selectively supply
`power to an accessory during PCD hibernation. In some
`embodiments, the PCD’s default behavior is to disable acces-
`sory power output during hibernation, and this default behav-
`ior can be overridden in response to a request from a con-
`nected accessory. The accessory can use the power supplied
`during PCD hibernation to detect user input (or other) events
`and wake the PCD from hibernation in response to a detected
`event. Some accessories can wake the PCD by emulating
`accessory detachment and reattachment.
`
`400
`
`(
`
`\<
`
`STORAGE
`DEVICE
`
`NETWORK
`INTERFACE
`
`422
`
`/
`
`PROCESSOR
`
`DISTRIBUTION
`
`ACCESSORY
`
`M
`
`PCD |/O
`INTERFACE
`
`CONTROLLER
`
`JOWER
`
`APPLE 1060
`
`1
`
`APPLE 1060
`
`

`

`Patent Application Publication
`
`Jul. 7, 2011 Sheet 1 0f 7
`
`US 2011/0167287 A1
`
`104
`
`106
`
`100
`
`
`
`206/108
`
`
`
`
`FIG. 25
`
`2
`
`

`

`Patent Application Publication
`
`Jul. 7, 2011 Sheet 2 0f 7
`
`US 2011/0167287 A1
`
`430
`E
`
`\
`
`STORAGE
`DEVICE
`
`NETWORK
`INTERFACE
`
`I
`
`POWER
`
`MANAGER
`
`II
`SENSOR
`
`ACCESSORY |/O
`INTERFACE
`
`HibNotify
`
`ACCESSORY
`M
`
`PCD I/O
`|NTERFACE
`
`COMMAND
`
`DIRECTION
`
`HibPowerRequest
`
`3
`
`

`

`Patent Application Publication
`
`Jul. 7, 2011 Sheet 3 0f 7
`
`US 2011/0167287 A1
`
`PCD I/O
`
`INTERFACE
`m GND
`
`612(1)
`610(1)\
`
`ACCESSORY |/O
`
`INTERFACE
`m
`
`GND
`
`,,,,,,,
`
`612(2)
`610(2)»
`/
`. /612(3)
`610(3)/
`
`//612(8)/ i
`610(4)/
`610(5)\\
`612(5)
`
`\
`
`WAKE EVT
`
`GENERATOR
`
`610(7)\\
`W; \ 612(7) mm
`
`
`
`
`
`W: W
`
`610(10)~\\
`— \612(10)
`
`L-
`
`FIG. 6
`
`61%(6)
`
`\
`
`WAKE EVENT GENERATOR
`704
`
`700
`_
`
`PCDHib
`
`708
`l
`
`’/
`
`CSOVNITTSEIL
`LOGIC
`
`'
`
`710
`//
`
`/
`
`\
`
`UserEvent
`
`FIG. 7
`
`4
`
`

`

`Patent Application Publication
`
`Jul. 7, 2011 Sheet 4 0f 7
`
`US 2011/0167287 A1
`
`800
`i
`
`\
`
`\V
`
`/ 802
`
`/ 804
`
`806
`
`
`I Hibernation
`
`810
`
`YES
`
`80:3
`.
`
`\
`Dld
`accessory request hibernation
`power?
`
`812
`
`
`
`FIG. 8
`
`Communicate to PCD that accessory should
`continue to receive power while PCD is in
`
`hibernation mode
`
`5
`
`

`

`Patent Application Publication
`
`Jul. 7, 2011 Sheet 5 of 7
`
`US 2011/0167287 A1
`
`M
`
`Establish connection to accessory
`
`1004
`
`
`Configure power
`
`manager based on
`
`power instruction
`
`Accessory sends
`power instruction?
`
`Operate with accessory in normal mode
`
`Enter hibernation mode?
`
`YES
`
`
`
`
`Notify accessory of hibernation
`
`1014
`
`Set power output to hibernation power level or
`off, based on accessory request
`
`/1016
`
`
`
`
`
`
`Wake event detected?
`
`YES
`
`Enable normal power output
`
` Accessory attached?
`
`FIG. 10
`
`/1022
`
`1026
`
`/
`
`Operate without
`accessory
`
`6
`
`

`

`Patent Application Publication
`
`Jul. 7, 2011 Sheet 6 of 7
`
`US 2011/0167287 A1
`
`/1102
`
`Establish connection to PCD
`
`Send power instruction requesting
`hibernation power
`
`OperatewithPCD
`
`PCD signals hibernation?
`
`YES
`
`Wait for user input event
`
`y/
`
`/1104
`
`
` /1106
`
`/ 1108
`
`ll
`
`
`/ 1112
`
`
`
`
`
`
`
`
`
`
`
`Generate waking signal to PCD
`
` 41114
`
`FIG. I]
`
`7
`
`

`

`Patent Application Publication
`
`Jul. 7, 2011 Sheet 7 0f 7
`
`US 2011/0167287 A1
`
`NETWORK
`INTERFACE
`
`/
`
`/
`
`422
`
`ACCESSORY |/O
`INTERFACE
`
`ACCESSORY
`fl
`
`PCD I/O
`INTERFACE
`
`USER INPUT
`DEVICE
`
`ACCESSORY 2
`
`1206
`
`/
`1 258/
`
`STORAGE
`MEDIUM
`READER
`
`DISTRIBUTION
`
`ER
`
`POW
`TRI
`BUTION
`
`IS
`
`POWER
`
`FIG. 12
`
`8
`
`

`

`US 2011/0167287 A1
`
`Jul. 7, 2011
`
`PROVIDING POWER TO AN ACCESSORY
`DURING PORTABLE COMPUTING DEVICE
`HIBERNATION
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application claims the benefit of US. Provi-
`sional Application No. 61/292,626, filed Jan. 6, 2010, entitled
`“Providing Power to an Accessory During Portable Comput-
`ing Device Hibernation,” the disclosure of which is incorpo-
`rated by reference herein in its entirety.
`BACKGROUND
`
`[0002] The present disclosure relates generally to portable
`computing devices that interact with accessories and in par-
`ticular to providing power from a portable device to an acces-
`sory during hibernation of the portable computing device.
`[0003]
`In recent years, a number of portable computing
`devices (PCDs) have been developed. Examples of PCDs
`include portable media players, mobile phones, personal digi-
`tal assistants (PDAs), portable e-mail devices, Video game
`players, portable navigation units relying on Global Position-
`ing System (GPS) satellite data, and multi-function devices
`that can integrate numerous functions such as media storage
`and playback, mobile phone, Internet access, e-mail, personal
`information management, game play, GPS/navigation capa-
`bility, and the like. Examples ofmulti-function PCDs include
`various iPhone® and iPod® models manufactured and sold
`
`by
`[0004] Apple Inc., assignee of the present application, as
`well as other portable electronic devices made and sold by
`other manufactures and distributors under their respective
`brand names.
`
`PCDs often obtain operating power from a battery
`[0005]
`within the device. Since a battery can provide only a finite
`amount of energy before requiring recharging or replace-
`ment, PCDs often employ various power-saving techniques
`to extend battery life. In one such technique, a PCD can be
`designed to transition into a “hibernation” mode in which
`some components of the deviceisuch as components that
`consume significant fractions ofthe total energy (e. g., display
`screen, primary processor, etc.)iare powered down. Other
`components of the PCD can continue to receive power during
`hibernation, and these components generate wake-up events,
`or wake event signals, in response to which power is restored
`to the powered-down components. Thus, for example, the
`user can press a button on the PCD to wake it from hiberna-
`tion, or a PCD can automatically wake itself from hibernation
`in response to an incoming phone call.
`[0006]
`PCDs are frequently docked with other electronic
`devices, referred to herein as “accessories.” For example,
`from time to time, a user may dock a PCD with a personal
`computer to synchronize media content and/or metadata, per-
`sonal data, and the like. A user may at other times dock the
`same PCD with other electronic devices, such as an in-vehicle
`media system, a speaker dock, or the like. Some accessories
`may provide power to the PCD from an external source, e. g.,
`to recharge the PCD’s battery or for use as operating power,
`and may also use power from an external source for their own
`operations. Other accessories draw their operating power
`from the PCD.
`
`BRIEF SUMMARY
`
`[0007] Certain embodiments ofthe present invention relate
`to PCDs that can selectively supply power to an accessory
`
`during PCD hibernation. In some embodiments, the PCD’s
`default behavior is to disable accessory power output during
`hibernation, but this default behavior can be overridden in
`response to a request from a connected accessory. The acces-
`sory can use the power supplied during PCD hibernation to
`detect user input or other events and wake the PCD from
`hibernation in response to a detected event. An accessory can
`wake the PCD, e.g., by emulating physical detachment and
`reattachment of the accessory.
`[0008] One aspect ofthe invention relates to accessories for
`portable computing devices and methods of operation
`thereof. For example, an accessory can establish a connection
`to a portable computing device and receive operating power
`from the portable computing device via the connection. The
`accessory can communicate to the portable computing device
`that that the accessory should receive power from the portable
`computing device when the portable computing device is in a
`hibernation mode. While the portable computing device is
`hibernating, the accessory can continue to receive power from
`the portable computing device. The accessory can detect an
`“accessory event” (such as user input or any other event or
`circumstance that should result in waking the portable com-
`puting device), in response to which it can signal the portable
`computing device to wake from hibernation mode.
`[0009]
`For example, an accessory can include an input/
`output (I/O) interface configured to connect to a portable
`computing device and to receive power from the portable
`computing device and a controller coupled to the I/O inter-
`face. The controller can be configured to send a request to the
`portable computing device to request that the accessory
`receive power while the portable computing device in a hiber-
`nation mode, to receive a notification from the portable com-
`puting device indicating that the portable computing device is
`entering the hibernation mode, to determine that the portable
`computing device should be awakened from the hibernation
`mode, and to generate a wake event signal in response to
`determining that the portable computing device should be
`awakened. For example the I/O interface can include a wake
`event generator, and the controller can be configured to con-
`trol the wake event generator to generate the wake event
`signal. In some embodiments, the wake event signal can
`emulate detachment and reattachment of the accessory; in
`other embodiments, other wake event signals can be used.
`[0010]
`In some embodiments,
`the portable computing
`device can have multiple hibernation modes, and the acces-
`sory can request to receive hibernation power in any or all of
`these modes. Further, in some embodiments, the accessory
`can also request a particular level of hibernation power for a
`given hibernation mode.
`[0011] Another aspect of the invention relates to portable
`computing devices and methods of operation thereof. For
`example, a portable computing device can establish a con-
`nection to an accessory and provide power to the accessory,
`e.g., via a power pin. The portable computing device can
`determine whether the accessory requests hibernation power.
`When the portable computing device enters the hibernation
`mode, it can continue to provide power to the accessory ifthe
`accessory requested hibernation power or discontinue pro-
`viding power to the accessory if the accessory did not request
`hibernation power.
`[0012]
`For example, a portable computing device can
`include a processor, an accessory input/output (I/O) interface
`coupled to the processor and configured to connect to an
`accessory, and a power manager configured to deliver power
`
`9
`
`

`

`US 2011/0167287 A1
`
`Jul. 7, 2011
`
`from a power source to the accessory I/O interface and the
`processor. The power manager can be further configured to
`enter a hibernation mode and to return from the hibernation
`
`mode to a normal operating mode. The processor can be
`configured to instruct the power manager to provide power
`from the power source to the accessory Via the accessory I/O
`interface and also configured to receive a request for hiber-
`nation power from the accessory Via the accessory I/O inter-
`face. In response to such a request, the processor can instruct
`the power manager to continue to provide power to the acces-
`sory while in the hibernation mode. The power manager can
`be further configured such that upon entering the hibernation
`mode, providing of power to the accessory is discontinued
`unless the instruction to continue to provide power to the
`accessory was received prior to entering the hibernation
`mode.
`
`[0013] The following detailed description together with the
`accompanying drawings will provide a better understanding
`of the nature and advantages of the present invention.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a front view ofa portable computing device
`[0014]
`(PCD) according to an embodiment of the present invention.
`[0015]
`FIGS. 2A and 2B are, respectively, a front perspec-
`tive view and side view of a dock for a PCD according to an
`embodiment of the present invention.
`[0016]
`FIG. 3 is a side view ofa PCD docked with a dock
`according to an embodiment of the present invention.
`[0017]
`FIG. 4 is a simplified block diagram of a system
`including a PCD connected to an accessory according to an
`embodiment of the present invention.
`[0018]
`FIG. 5 is a table listing power-management com-
`mands that can be provided according to an embodiment of
`the present invention.
`[0019]
`FIG. 6 is a simplified connection diagram illustrat-
`ing connections that can be provided between an accessory
`and a PCD according to an embodiment of the present inven-
`tion.
`
`FIG. 7 is a simplified block diagram of a wake event
`[0020]
`generator for an accessory according to an embodiment ofthe
`present invention.
`[0021]
`FIG. 8 is a flow diagram of a power management
`process that can be implemented in a PCD according to an
`embodiment of the present invention.
`[0022]
`FIG. 9 is a flow diagram of a process that can be
`implemented in an accessory according to an embodiment of
`the present invention.
`[0023]
`FIG. 10 is a flow diagram ofa power management
`process that can be implemented in a PCD according to an
`embodiment of the present invention.
`[0024]
`FIG. 11 is a flow diagram of a process for operating
`an accessory according to an embodiment of the present
`invention.
`
`FIG. 12 is a block diagram of a system including a
`[0025]
`PCD connected to two accessories in a daisy chain according
`to an embodiment of the present invention.
`
`DETAILED DESCRIPTION
`
`[0026] Certain embodiments ofthe present invention relate
`to PCDs that can selectively supply power to an accessory
`during PCD hibernation. In some embodiments, the PCD’s
`default behavior is to disable accessory power output during
`hibernation, but this default behavior can be overridden in
`
`response to a request from a connected accessory. The acces-
`sory can use the power supplied during PCD hibernation to
`detect user input or other events and wake the PCD from
`hibernation in response to a detected event. An accessory can
`wake the PCD, e.g., by emulating physical detachment and
`reattachment of the accessory.
`[0027]
`FIG. 1 is a front view ofa portable computing device
`(PCD) 100 according to an embodiment of the present inven-
`tion. PCD 100 can have a touchscreen display 102 surrounded
`by bezel 104. Control buttons 106 are provided in bezel 104
`and can be used, e. g., to wake PCD 100 from hibernation, to
`put PCD 100 into hibernation, or to provide other input to
`PCD 100.
`
`PCD 100 can have a connector 108 recessed into a
`[0028]
`bottom surface thereof, allowing PCD 100 to become
`attached to an accessory device. Connector 108 can include a
`number ofpins for carrying power, analog, and digital signals
`between PCD 100 and a connected accessory. In one embodi-
`ment, connector 108 can be implemented as a 30-pin docking
`connector as used in existing iPod® and iPhone® products
`sold by Apple Inc., assignee of the present application. In
`some embodiments, connector 108 is recessed into the hous-
`ing of PCD 100 and is referred to as a “receptacle” connector.
`Other connectors can also be used.
`
`[0029] As shown in inset 110, PCD 100 can have a power
`manager 112 and a battery 114 to provide power for the
`operation of PCD 100. Power manager 112 can provide
`power to various components of PCD 100 and to a connected
`accessory via connector 108. Power manager 112 can be
`configured to allow PCD 100 to enter a hibernation (i.e.,
`reduced-power) mode under various conditions such as after
`a sufficiently long period of inactivity, thereby extending the
`operating life of battery 114. As described below, power
`manager 112 can also control whether accessory power con-
`tinues to be supplied via connector 108 when PCD 100 enters
`the hibernation mode.
`
`In the embodiment shown, PCD 100 can be a tablet
`[0030]
`computer with, e. g., a lO-inch screen. In other embodiments,
`PCD 100 can have a variety of form factors and configura-
`tions, e.g., smart phone, personal digital assistant, media
`player, portable web browser, etc.
`[0031]
`FIGS. 2A and 2B are, respectively, a front perspec-
`tive view and side view of a dock 200 for PCD 100 according
`to an embodiment of the present invention. Dock 200 has a
`base section 202, a keyboard 204, a PCD connector 206 and
`an accessory connector 208.
`[0032] Base section 202 can include electronic components
`as well as mechanical ballast to provide stability to dock 200.
`Keyboard 204 can include a conventional QWERTY key-
`board, numeric keypad, and/or other user input controls. Key-
`board 204 can be mechanically and electrically coupled to
`base section 202, allowing keystroke information to be passed
`to PCD 100, e.g., via PCD connector 206.
`[0033]
`PCD connector 206 can be designed to mate with
`connector 108 of PCD 100 of FIG. 1. For example, PCD
`connector 206 can be a “plug” counterpart of receptacle con-
`nector 108, extending outward from base section 202.
`[0034] Accessory connector 208, shown in FIG. 2B, can be
`identical to connector 108 ofPCD 100 of FIG. 1 and can allow
`
`an additional accessory to connect to dock 200. In this con-
`figuration, any accessory with a connector capable of con-
`necting to connector 108 of PCD 100 can also connect to
`accessory connector 208 of dock 200. Use of complementary
`PCD connector 206 and accessory connector 208, while not
`10
`
`10
`
`

`

`US 2011/0167287 A1
`
`Jul. 7, 2011
`
`required, permits another accessory to connect to PCD 100
`either directly (by connecting to connector 108) or indirectly
`(by connecting to accessory connector 208 when connector
`206 is connected to PCD 100).
`[0035]
`In some embodiments, dock 200 need not have its
`own power supply. Instead, power can be provided to dock
`200 by another device connected to accessory connector 208,
`or dock 200 can draw power from a connected PCD Via
`connector 206.
`
`FIG. 3 is a side view of PCD 100 docked with dock
`[0036]
`200 according to an embodiment of the present invention.
`Connector 108 of PCD 100 is engaged with connector 206 of
`dock 200, providing electrical connections that allow power,
`data, and other signals to be exchanged between the two
`devices. Thus, for example, dock 200 can draw operating
`power from PCD 100. In some embodiments, as described
`below, dock 200 can draw operating power from PCD 100
`while PCD 100 is hibernating; PCD 100 can supply this
`“hibernation power” to dock 200 in response to a request from
`dock 200.
`
`It will be appreciated that the devices and configu-
`[0037]
`rations described herein are illustrative and that variations
`
`and modifications are possible. For example, as noted above,
`the term PCD refers generally to a broad category of personal
`computing and/or communication devices that can easily be
`carried by a user, not limited to any particular form factor or
`combination of capabilities.
`[0038] The keyboard dock described herein is just one of
`many accessories that can be used with a PCD. For example,
`another accessory can provide a reader/writer for removable
`storage media such as flash memory media (e.g., Secure
`Digital, or “SD,” cards; USB drives) or optical media (e.g.,
`compact disc or DVD), and a PCD can be operated to direct
`the accessory to read data from and/or write data to the stor-
`age media. An accessory can provide output devices such as
`speakers and/or a display screen, allowing a user to view
`and/or hear content from the PCD through the accessory. A
`printer accessory can also be provided for printing documents
`or other data under control of the PCD. Still other accessories
`
`can provide enhanced functionality such as radio frequency
`(RF) tuners or transmitters that can be controlled by a PCD,
`remote user interfaces to control a PCD, still or video cameras
`that can be controlled by a PCD, and so on. Some accessories
`can provide multiple functionalities within a single device
`(e. g., keyboard plus storage media reader/recorder).
`[0039]
`Further, while FIG. 3 shows PCD 100 and accessory
`200 as being directly connected, indirect connections are also
`possible. For example, PCD 100 and accessory 200 can be
`connected using a cable that provides a connector comple-
`mentary to connector 108 at one end and a connector comple-
`mentary to connector 206 at the other end. Where a cable is
`used, connectors 108 and 206 need not be complementary to
`each other, as the cable can serve as an adapter between
`different connector form factors and/or pin arrangements.
`[0040]
`FIG. 4 is a simplified block diagram ofa system 400
`including PCD 402 and accessory 404 according to an
`embodiment of the present invention. In this embodiment,
`PCD 402 (e.g., implementing PCD 100 ofFIG. 1) can provide
`computing, communication and/or media playback capabil-
`ity. PCD 402 can include processor 410, storage device 412,
`user interface 414, power manager 416, network interface
`418, accessory input/output (I/O) interface 420, and battery
`422. PCD 402 can also include other components (not explic-
`itly shown) to provide various enhanced capabilities.
`
`Storage device 412 can be implemented, e.g., using
`[0041]
`flash memory, or any other non-volatile storage
`disk,
`medium. In some embodiments, storage device 412 can store
`media assets such as audio, video, still images, or the like, that
`can be played by PCD 402. Storage device 412 can also store
`other information such as a user’s contacts (names, addresses,
`phone numbers, etc.); scheduled appointments and events;
`notes; and/or other personal information. In some embodi-
`ments, storage device 412 can store one or more application
`programs to be executed by processor 410 (e.g., video game
`programs, personal
`information management programs,
`media playback programs, etc.).
`[0042] User interface 414 can include input devices such as
`a touch pad, touch screen, scroll wheel, click wheel, dial,
`button, switch, keypad, microphone, or the like, as well as
`output devices such as a video screen, indicator lights, speak-
`ers, headphone jacks, or the like, together with supporting
`electronics (e.g., digital-to-analog or analog-to-digital con-
`verters, signal processors, or the like). A user can operate
`input devices of user interface 414 to invoke the functionality
`of PCD 402 and can view and/or hear output from PCD 402
`via output devices of user interface 414.
`[0043]
`Processor 410, which can be implemented as one or
`more integrated circuits (e.g., a conventional microprocessor
`or microcontroller), can control the operation of PCD 402. In
`various embodiments, processor 404 can execute a variety of
`programs in response to program code and can maintain
`multiple concurrently executing programs or processes. At
`any given time, some or all ofthe program code to be executed
`can be resident in processor 410 and/or in storage media such
`as storage device 412.
`[0044] Through suitable programming, processor 410 can
`provide various functionality for PCD 402. For example, in
`response to user input signals provided by user interface 414,
`processor 410 can operate a database engine to navigate a
`database of media assets stored in storage device 412 in
`response to user input and display lists of selected assets.
`Processor 410 can respond to user selection of an asset (or
`assets) to be played by transferring asset information to a
`playback engine also operated by processor 410, thus allow-
`ing media content to be played. Processor 410 can also
`execute other programs to control other functions of PCD
`402, including application programs that may be stored in
`storage device 412.
`[0045]
`Power manager 416 provides power management
`capability for PCD 402. For example, power manager 416 can
`deliver power from battery 422 to accessory I/O interface 420
`via line 417 and to other components of PCD 402 (power
`connections not shown). Power manager 416 can also receive
`power via accessory I/O interface 420 and line 419 and
`deliver received power to various components of PCD 402;
`power received via accessory I/O interface 420 can also be
`delivered to battery 422, thereby allowing battery 422 to be
`recharged via accessory I/O interface 420. As shown, power
`manager 416 can also deliverpower to accessory I/O interface
`420 via line 417, allowing PCD 402 to provide power to a
`connected accessory. In some embodiments, power manager
`416 can be implemented using programmable or controllable
`circuits operating in response to control signals generated by
`processor 41 0 in response to program code executing thereon,
`or as a separate microprocessor or microcontroller.
`[0046]
`Power manager 416 can also control power distri-
`bution to effect a hibernation mode for PCD 402. As used
`
`herein, “hibernation” refers generally to a reduced-power
`
`11
`
`11
`
`

`

`US 2011/0167287 A1
`
`Jul. 7, 2011
`
`operating mode (or state) that is entered by selectively pow-
`ering down some components of a PCD. Power manager 416
`and some components of PCD 402 can remain partially or
`fully operational during hibernation, allowing PCD 402 to be
`awakened from hibernation. During hibernation, the user’s
`ability to interact with PCD 402 can be limited. For example,
`during hibernation, display screens can be turned off, and
`some user input controls (e. g., a touchscreen) can be disabled.
`One or more user input controls (e.g., a button) can remain
`enabled, and operation of those controls during hibernation
`can signal PCD 402 to wake from hibernation and return to
`normal operation.
`[0047]
`Power manager 416 can also provide other power
`management capabilities, such as regulating power consump-
`tion of other components of PCD 402 based on the source and
`amount of available power, monitoring stored power in the
`battery and generating user alerts if the stored power drops
`below a minimum level, and so on.
`[0048] Network interface 418 can provide voice and/or data
`communication capability for PCD 402. In some embodi-
`ments network interface 418 can include radio frequency
`(RF) transceiver components for accessing wireless voice
`and/or data networks (e. g., using cellular telephone technol-
`ogy, advanced data network technology such as 3G or EDGE,
`WiFi (IEEE 802.11 family standards), or other mobile com-
`munication technologies, or any combination thereof), GPS
`receiver components, and/or other components. In some
`embodiments network interface 418 can provide wired net-
`work connectivity (e.g., Ethernet) in addition to or instead of
`a wireless interface. Network interface 418 can be imple-
`mented using a combination of hardware (e.g., antennas,
`modulators/demodulators, encoders/decoders, and other ana-
`log and/or digital signal processing circuits) and software
`components.
`[0049] Accessory I/O interface 420 can allow PCD 402 to
`communicate with various accessories. For example, acces-
`sory I/O interface 420 can support connections to a computer,
`an external keyboard (e.g., as shown in FIG. 2), a speaker
`dock or media playback station, a digital camera, a radio tuner
`(e.g., FM, AM and/or satellite), an in-vehicle entertainment
`system, an external video device, a memory card reader, and
`so on. In some embodiments, accessory I/O interface 420 can
`include a connector, such as a 30-pin connector correspond-
`ing to the connector used on iPod® and iPhone® products, as
`well as supporting circuitry. The connector can provide con-
`nections for power and ground as well as for various wired
`communication interfaces such as Universal Serial Bus
`
`(USB), FireWire (IEEE 1394 standard), and/or universal
`asynchronous receiver/transmitter (UART). The connector
`can also provide connections for audio and/or video signals,
`which may be transmitted to or from PCD 402 in analog
`and/or digital formats. Thus, accessory I/O interface 420 can
`support multiple communication channels, and a given acces-
`sory can use any or all of these channels.
`[0050] Accessory I/O interface 420 can include a sensor
`424 that can detect whether an accessory is connected to
`accessory I/O interface 420. For example, sensor 424 can
`detect whether a specific pin of a connector of accessory I/O
`interface 420 is grounded or floating, and grounding of this
`pin can indicate the presence of an accessory. In some
`embodiments, sensor 424 can measure the resistance value
`when a resistance is connected. The resistance value can
`
`indicate of the type of accessory connected, and sensor 424
`can communicate the resistance value (or accessory-type
`
`information determined from the resistance value) to power
`manager 416, processor 410, and/or other components of
`PCD 402. In some embodiments, power manager 416 can use
`this information to determine, e. g., whether to distribute
`power from the battery or power received from accessory I/O
`interface 420 to other components of PCD 402, whether to
`use power provided via accessory I/O interface 420 to charge
`battery 422, whether to deliver power to accessory I/O inter-
`face 420 and so on. In some embodiments, sensor 424 can
`remain active during PCD hibernation and can generate sig-
`nals to power manager 416 to wake PCD 402 when a new
`connection to an accessory is detected.
`[0051] Accessory 404 (e.g.,
`implementing dock 200 of
`FIG. 2) can include controller 430, user input device 432,
`power distribution module 434, and PCD I/O interface 436.
`Accessory 404 is representative of a broad class of accesso-
`ries that can interoperate with a PCD, and such accessories
`can vary widely in capability, complexity, and form factor.
`Various accessories may include components not shown in
`FIG. 4, including but not limited to storage devices (disk,
`flash memory, etc.) with fixed or removable storage media;
`video screens, speakers, or ports for connecting to external
`audio/video devices; camera components such as lenses,
`image sensors, and controls for same (e.g., aperture, zoom,
`exposure time, frame rate, etc.); microphones for recording
`audio (either alone or in connection with video recording);
`and so on. In addition, some accessories may provide an
`additional interface that can connect to and communicate
`
`with another accessory. Some examples of accessories with
`additional interfaces are described in co-pending U.S. Provi-
`sional Patent Application No. 61/292,619, filed Jan. 6, 2010.
`[0052] Controller 430 can include, e.g., a microprocessor
`or microcontroller executing program code to perform vari-
`ous functions associated with accessory 404. For example,
`where accessory 404 incorporates a keyboard (e.g., as shown
`in FIG. 2A), controller 430 can interpret keyboard input and
`send corresponding information to PCD 402.
`[0053] User input device 432 may include user-operable
`controls such as a touch pad, touch screen, scroll wheel, click
`wheel, dial, button, switch, keyboard, keypad, microphone, or
`the like. A user can operate the controls of user input device
`432 to invoke the functionality of accessory 404, and such
`functionality may include exchanging control signals, data,
`or other communications with PCD 402, e.g., as described
`below.
`
`Power distribution module 434 can provide power
`[0054]
`to components of accessory 404, e.g., to controller 430 (indi-
`cated by line 435) and user input device 432 (indicated by line
`437). In some embodiments, power distribution module 434
`can receive power via PCD I/O interface 436 (indicated by
`line 439). In addition, in some embodiments, accessory 404
`can be connected to an external power source via power port
`440, and power from port 440 can also be provided to power
`distribution module 434 (indicated by line 441). Power dis-
`tribution module 434 can include control logic to determine,
`based on the available power sources at a given time, whether
`to draw operating power for accessory 404 from PCD 402 or
`from power port 440. Further, power distribution module 434
`can be configured to deliver power from power port 440 to
`PCD I/O interface 436 (indicated by line 443), thus allowing
`PCD 402 to charge battery 422 while connected to accessory
`404. In some embodiments, accessory 404 can draw operat-
`ing power from PCD 402 while providing charging power to
`PCD 402 on a separate path.
`
`12
`
`12
`
`

`

`US 2011/0167287 A1
`
`Jul. 7, 2011
`
`PCD I/O interface 436 can allow accessory 404 to
`[0055]
`communicate with PCD 402. In accordance with some
`embodiments of the invention, PCD I/O interface 436 can
`include a connector that mates directly with a connector
`included in PCD 402, such as a 30-pin connector complemen-
`tary to the connector used in various iPod® and iPhone®
`products. Such a connector can be used to supply power to
`PCD 402 and/or receive power from PCD 402, to send and/or
`receive audio and/or video signals in analog and/or digital
`formats, and to communicate information