(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2007/0006146A1
`Kwong et al.
`(43) Pub. Date:
`Jan. 4, 2007
`
`US 2007.0006146A1
`
`(54) SYSTEMS AND APPARATUS FOR
`ENHANCED MOBILE COMPUTING
`PLATFORMS
`
`(22) Filed:
`
`Jun. 24, 2005
`
`Publication Classification
`
`(76) Inventors: Wah Yin Kwong, Beaverton, OR (US);
`Prosenjit Ghosh, Portland, OR (US);
`Katie Mills, Portland, OR (US); Jim
`Trethewey, Hillsboro, OR (US);
`Robert Jacobs, Portland, OR (US);
`Tim Nguyen, Portland, OR (US); Asim
`Sadiq, Santa Clara, CA (US);
`Shreekant Thakkar, Portland, OR
`(US); Murali Veeramoney, Beaverton,
`OR (US); Truong Phan, Hillsboro, OR
`(US)
`Correspondence Address:
`BUCKLEY, MASCHOFF, TALWALKAR LLC
`SELM STREET
`NEW CANAAN, CT 06840 (US)
`(21) Appl. No.:
`11/165,815
`
`(51) Int. Cl.
`(2006.01)
`G06F 9/44
`(52) U.S. Cl. .............................................................. 717/114
`(57)
`ABSTRACT
`According to Some embodiments, systems and apparatus for
`enhanced mobile computing platforms are provided. For
`example, an apparatus or system may comprise a universal
`computational package, comprising a processor, a memory
`coupled to the processor, a plurality of instructions stored in
`the memory directed to at least one specific use of the
`universal computational package, and a plurality of interface
`controllers coupled to the processor, wherein each of the
`plurality of interface controllers is operable to cause the
`processor to execute the plurality of stored instructions in
`accordance with the presence of a use-specific user interface
`cover associated with the at least one specific use of the
`universal computational package.
`
`100
`
`N
`
`
`
`UNIVERSAL COMPUTATIONAL PACKAGE
`
`USE
`SPECIFIC
`USER
`INTERFACE
`COVER
`DEVICES
`
`12
`
`INTERFACE
`CONTROLLER
`
`INTERFACE
`CONTROLLER
`
`PROCESSOR
`112
`
`MEMORY
`
`APPLE 1012
`
`1
`
`

`

`Patent Application Publication Jan. 4, 2007 Sheet 1 of 9
`
`US 2007/000614.6 A1
`
`100
`
`N
`
`
`
`UNIVERSAL COMPUTATIONAL PACKAGE
`
`USE-
`SPECIFIC
`USER
`INTERFACE
`COVER
`DEVICES
`
`12
`
`INTERFACE
`CONTROLLER
`
`INTERFACE
`CONTROLLER
`
`PROCESSOR
`112
`
`MEMORY
`
`FIG. 1
`
`2
`
`

`

`Patent Application Publication Jan. 4, 2007 Sheet 2 of 9
`
`US 2007/000614.6 A1
`
`200
`
`N
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`BUSINESS
`SPECIFIC
`USER
`INTERFACE
`COVER
`DEVICE
`
`GAMING
`SPECIFIC
`USER
`INTERFACE"
`COVER
`DEVICE
`
`
`
`
`
`
`
`20b
`
`220a
`
`UNIVERSAL COMPUTATIONAL PACKAGE
`210 10
`
`GAMING
`INTERFACE
`CONTROLLER
`
`PROCESSOR
`212
`
`BUSINESS
`---------------------------------------------- INTERFACE
`CONTROLLER
`
`E-COMMERCE
`SPECIFIC
`USER
`
`
`
`
`
`
`
`NSE
`
`
`
`
`
`DEVICE
`
`| OER
`USE
`SPECIFIC
`USER
`INTERFACE
`
`
`
`
`
`
`
`COVER
`DEVICE
`
`220C
`
`22On
`
`E-COMMERCE |
`INTERFACE
`CONTROLLER
`
`OTHER
`INTERFACE
`CONTROLLER
`
`FIG. 2
`
`GAMING
`INSTRUCTIONS
`
`BUSINESS
`INSTRUCTIONS
`E-COMMERCE
`INSTRUCTIONS
`
`
`
`OTHER
`INSTRUCTIONS
`
`218n
`
`3
`
`

`

`Patent Application Publication Jan. 4, 2007 Sheet 3 of 9
`
`US 2007/000614.6 A1
`
`
`
`300
`
`FIG. 3B
`
`4
`
`

`

`Patent Application Publication a 4, 2007 Sheet 4 of 9
`
`US 2007/0006146 A1
`
`
`
`400
`
`F.G. 4
`
`5
`
`

`

`
`
`FIG. 5
`
`6
`
`

`

`Patent Application Publication Jan. 4, 2007 Sheet 6 of 9
`
`US 2007/000614.6 A1
`
`600
`N
`
`662
`
`
`
`UNIVERSAL COMPUTATIONAL
`PACKAGE
`
`ACCESSORY MODULE
`
`MODULE
`ELECTRONICS
`
`CONVERSION
`EECTRONics
`
`FIG. 6
`
`7
`
`

`

`Patent Application Publication Jan. 4, 2007 Sheet 7 of 9
`
`US 2007/000614.6 A1
`
`770 N
`
`772
`
`T
`
`
`
`s
`
`
`
`
`
`
`
`
`
`
`
`
`
`B. AB S.Ba-B hars (SB SEAH AaB 8
`
`(P.Sc.E CAR
`
`2
`
`s
`
`s
`
`s
`
`s's
`
`s
`
`s
`
`s
`
`s
`
`s
`
`O
`O
`o
`
`
`
`
`
`
`
`778
`
`776
`
`774
`
`780
`
`782
`
`FIG. 7
`
`8
`
`

`

`Patent Application Publication Jan. 4, 2007 Sheet 8 of 9
`
`US 2007/000614.6 A1
`
`800 N
`
`BLUETOOTHMODULE
`878a
`878b
`
`WIRELESS
`COMMUNICATION
`CIRCUIT
`
`
`
`
`
`
`
`
`
`KEYBOARD
`NROWS
`
`CONTROL
`CIRCUIT
`
`CONTROLLER
`
`
`
`
`
`Left Mouse
`button
`
`:
`Rigi Muse :
`
`870
`
`9
`
`

`

`Patent Application Publication Jan. 4, 2007 Sheet 9 of 9
`
`US 2007/000614.6 A1
`
`900
`
`N
`
`
`
`UNIVERSAL COMPUTATIONAL PACKAGE
`
`USE
`SPECIFIC
`USER
`INTERFACE
`COVER
`DEVICES
`
`920
`
`INTERFACE
`CONTROLLER
`
`PROCESSOR
`
`INTERFACE
`CONTROLLER
`
`MEMORY
`914
`
`BATTERY
`
`FIG. 9
`
`10
`
`

`

`US 2007/0006146 A1
`
`Jan. 4, 2007
`
`SYSTEMS AND APPARATUS FOR ENHANCED
`MOBILE COMPUTING PLATFORMS
`
`BACKGROUND
`0001 Mobile computing devices have continued to
`increase in variety, functionality, and numbers. Lighter and
`more compact portable computers, web tablets, digital music
`players, cellular telephones, and Personal Digital Assistant
`(PDA) devices, for example, are used throughout the con
`Sumer and business marketplaces. While some mobile plat
`forms have merged to create more powerful and multi
`functional devices, these devices fall short of offering a level
`of integration, ease of use, ease of manufacture, and/or
`user-friendly design that is required by modern users. Modu
`larity and use-specific design or configuration, for example,
`are typically absent in existing mobile computing platforms.
`For these and other reasons, typical mobile computing
`platforms may not be desirable.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0002 FIG. 1 is a block diagram of a system according to
`Some embodiments.
`0003 FIG. 2 is a block diagram of a system according to
`Some embodiments.
`0004 FIG. 3A and FIG. 3B are perspective diagrams of
`a system according to some embodiments.
`0005 FIG. 4 is a perspective diagram of a system accord
`ing to Some embodiments.
`0006 FIG. 5 is a block diagram of an apparatus according
`to Some embodiments.
`0007 FIG. 6 is a circuit diagram of a system according to
`Some embodiments.
`0008 FIG. 7 is a block diagram of an apparatus according
`to Some embodiments.
`0009 FIG. 8 is a circuit diagram of a system according to
`Some embodiments.
`0010 FIG. 9 is a block diagram of a system according to
`Some embodiments.
`
`DETAILED DESCRIPTION
`Referring first to FIG. 1, a block diagram of a
`0011
`system 100 according to some embodiments is shown. The
`various systems described herein are depicted for use in
`explanation, but not limitation, of described embodiments.
`Different types, layouts, quantities, and configurations of
`any of the systems described herein may be used without
`deviating from the scope of some embodiments. Fewer or
`more components than are shown in relation to the systems
`described herein may be utilized without deviating from
`Some embodiments.
`0012. The system 100 may comprise, for example, a
`Universal Computational Package (UCP) 110. The UCP 110
`may, for example, be or include various computational
`and/or processing components that Substantially and/or
`entirely comprise the electrical components of a computa
`tional device Such as a mobile computing platform (e.g., the
`system 100). According to some embodiments, the UCP 110
`may comprise a processor 112, a memory 114, and/or one or
`
`more interface controllers 116a-n. The processor 112 may,
`for example, comprise any number of processors, which
`may be any type or configuration of processor, micropro
`cessor, and/or micro-engine that is or becomes known or
`available. According to some embodiments, the processor
`112 may be an XScale R. Processor such as an Intel(R)
`PXA270 XScale R processor, an Intelg Pentium R. M. Pro
`cessor with a Mobile Intel R. 915GM/PM/GMS Express
`chipset, and/or any other type of processor that is or
`becomes known or practicable.
`0013 The memory 114 may be or include, according to
`Some embodiments, one or more magnetic storage devices,
`Such as hard disks, one or more optical storage devices,
`and/or one or more solid state storage devices. The memory
`114 may store, for example, applications, programs, proce
`dures, and/or modules that store instructions to be executed
`by the processor 112. The memory 114 may comprise,
`according to some embodiments, any type of memory for
`storing data, Such as a Single Data Rate Random Access
`Memory (SDR-RAM), a Double Data Rate Random Access
`Memory (DDR-RAM), or a Programmable Read Only
`Memory (PROM).
`0014. In some embodiments, the interface controllers
`116a-n may comprise any number of devices, paths, wires,
`cables, ports, Printed Circuit Board (PCB) devices, and/or
`other electrical and/or physical components configured to
`send, receive, transmit, and/or communicate interface sig
`nals. An interface controller 116a-n may, for example,
`comprise a circuit and/or device capable of receiving input
`signals from one of a plurality of Use-Specific User Inter
`face Cover (USUIC) devices 120 and/or capable of trans
`mitting such signals to the processor 112 of the UCP 110.
`According to some embodiments, the interface controllers
`116a-n may be coupled to an USUIC device 120 and/or
`various components thereof. The USUIC device 120 may,
`for example, provide input signals to the interface control
`lers 116a-n to cause the processor 112 to execute instruc
`tions stored in the memory 114.
`0015. In some embodiments, the USUIC device 120 may
`be directed to and/or configured for a specific use. The
`USUIC device 120 may, for example, be a user interface
`cover (e.g., a “skin') that, when coupled to the UCP 110, is
`operable to cause the UCP 110 to execute instructions
`directed to the specific use. The USUIC device 120 may,
`according to Some embodiments, be utilized to provide an
`indication to one or more of the interface controllers 116a-n,
`for example, and the one or more interface controllers
`116a-n may be directed to cause the processor 112 to execute
`instructions stored in the memory 114. The instructions (not
`shown in FIG. 1) may, for example, be directed to the
`specific use associated with the USUIC device 120.
`0016 Turning in more detail to FIG. 2, for example, a
`block diagram of a system 200 according to Some embodi
`ments is shown. The system 200 may, for example, be
`similar in functionality and/or configuration to the system
`100 described in conjunction with FIG. 1. In some embodi
`ments, the system 200 may comprise a UCP 210 that
`comprises a processor 212, a memory 214, and/or one or
`more interface controllers 216a-n. In some embodiments,
`the memory 214 may store various instructions 218a-n
`capable of being executed by the processor 212. The instruc
`tions 218a-n may, for example, be directed to causing the
`
`11
`
`

`

`US 2007/0006146 A1
`
`Jan. 4, 2007
`
`processor 212 to perform in accordance with one or more
`specific uses. As shown in FIG. 2, for example, the instruc
`tions 218a-n may be directed to specific uses such as gaming
`applications (e.g., gaming instructions 218a), business
`applications (e.g., business instructions 218b), e-commerce
`applications (e.g., e-commerce instructions 218c), and/or
`other applications (e.g., other instructions 218m). In some
`embodiments, fewer or more components than are shown in
`FIG. 2 may be included in the system 200.
`0017 According to some embodiments, the use-specific
`instructions 218a-n may be or include any number of
`commands, lines of code, procedures, packages, modules,
`applications, files, and/or other instructions or combinations
`thereof that are operable to cause the processor 212 to
`process data or information in accordance with a specific
`use. For example, the gaming instructions 218a may com
`prise code, that when executed by the processor 212, is
`operable to cause the processor 212 to perform one or more
`computational, procedural, and/or other processing acts
`associated with a gaming use. In some embodiments, the
`gaming use may simply involve the execution of various
`gaming applications and/or procedures. According to some
`embodiments, the gaming use may also or alternatively
`involve configuring the UCP210 in accordance with various
`gaming setups, configurations, and/or other gaming-related
`actS.
`0018. In some embodiments, the use-specific instructions
`218a-n may be associated with the interface controllers
`216a-n. The interface controllers 216a-n may, for example,
`comprise use-specific interface controllers 216a-n directed
`to the specific uses of the use-specific instructions 218a-n,
`respectively. According to some embodiments for example,
`a gaming interface controller 216a may be operable to cause
`the processor 212 to execute the gaming instructions 218a.
`The gaming interface controller 216a may, for example,
`comprise a set of wires and/or other circuit components that
`are operable to send a signal to the processor 212 to indicate
`that the gaming instructions 218a should be executed, ini
`tialized, and/or otherwise activated. Although the use-spe
`cific interface controllers 216a-n are shown in FIG. 2 as
`being paired in a one-to-one relationship with the use
`specific instructions 218a-in, respectively, other configura
`tions may also or alternatively be employed within the UCP
`210. One use-specific interface controller 216a-n may, for
`example, be associated with the execution of multiple use
`specific instructions 218a-in, or vice versa.
`0.019 According to some embodiments, the system 200
`may also comprise one or more USUIC devices 220a-n (e.g.,
`a plurality of USUIC device 220a-n). In some embodiments,
`the USUIC devices 220a-n may be associated with one or
`more of the use-specific interface controllers 216a-n. As
`shown in FIG. 2, for example, a gaming USUIC device
`220a, a business USUIC device 220b, an e-commerce
`device USUIC 220c, and/or an other USUIC device 220m
`may be associated with the gaming, business, e-commerce,
`and other interface controllers 216a-in, respectively (e.g.,
`associated upon coupling to the UCP210). For example, the
`gaming USUIC device 220a may be coupled to activate the
`gaming interface controller 216a (e.g., to cause the proces
`Sor 212 to execute the gaming instructions 218a). In some
`embodiments, any one of the USUIC devices 220a-n may be
`coupled to the UCP210. The system 200 may, for example,
`comprise a use-specific mobile computational platform
`
`directed to executing the use associated with the USUIC
`device 220a-n coupled to the UCP 210.
`0020. In some embodiments, any of the plurality of
`USUIC devices 220a-n may be coupled to the UCP 210 to
`cause the system 200 to be associated with a specific use
`(and/or with a plurality of specific uses). The UCP210 may,
`for example, be manufactured to be compatible with any of
`the plurality of USUIC device 220a-n. In some embodi
`ments, the system 200 may be defined as a "gaming system”
`(e.g., where gaming is the dominant and/or exclusive use) by
`coupling the gaming USUIC device 220a to the UCP 210.
`According to some embodiments, the selected USUIC
`device 220a-n may be coupled to the UCP210 to electrically
`couple the selected USUIC device 220a-n to one or more of
`the use-specific interface controllers 216a-n (e.g., that are
`directed to a use associated with the selected USUIC device
`220a-n) and/or to at least partially envelope and/or cover the
`UCP 210 and/or components thereof. The USUIC device
`220a-n may, for example, comprise a chassis and/or cover
`(not shown) that is configured to mate with a chassis (also
`not shown) of the UCP210 to define a mobile computational
`device (and/or an enclosure or body thereof). In some
`embodiments, the USUIC device 220a-n may be or include
`more structural definition than simply a portion of a chassis
`of the system 200. The USUIC device 220a-n may, for
`example, comprise and/or define Substantially the entire
`chassis of the system 200. The UCP 210 may, for example,
`be or include a motherboard and/or other module or unit that
`is operable to fit within, slide into, snap onto, and/or
`otherwise couple to (and/or within) the USUIC device
`220a-n.
`0021 According to some embodiments, the modular
`nature of the USUIC device 220a-n and of the UCP210 may
`provide enhanced manufacturing and/or assembly options
`and/or may reduce manufacturing and/or assembly costs.
`Many UCP210 devices may be produced, for example, and
`utilized as the electronic base for any of a wide variety of
`use-specific devices depending only upon which USUIC
`device 220a-n is coupled thereto. Standardization of the
`base electronics may, according to some embodiments,
`promote ease of manufacture and/or simplify any alterations
`(e.g., likely made in a modular nature) required and/or
`desired for any of the plurality of USUIC devices 220a-n. A
`gaming-specific device may, for example, include a higher
`capacity memory 214, for example, while otherwise main
`taining the same interface controllers 216a-n and/or instruc
`tions 218a-n as other use-specific UCP 210 setups. In some
`embodiments, the USUIC device 220a-n may comprise any
`number of interface devices (not shown in FIG. 2) such as
`input and/or output devices. According to some embodi
`ments, the positioning and/or configuration of these inter
`face devices may define which of the use-specific interface
`controllers 216a-n are activated by a particular USUIC
`device 220a-n (e.g., when coupled to the UCP 210).
`0022 Referring to FIG. 3A and FIG. 3B, for example,
`perspective diagrams of a system 300 according to some
`embodiments are shown. In some embodiments, the system
`300 may be similar in functionality and/or configuration to
`the systems 100, 200 described in conjunction with any of
`FIG. 1 and/or FIG. 2. The system 300 may, for example, be
`a modular mobile computing platform comprising a UCP
`310 and a USUIC device 320. As shown in FIG. 3A and FIG.
`3B, the combination of the UCP 310 and the USUIC device
`
`12
`
`

`

`US 2007/0006146 A1
`
`Jan. 4, 2007
`
`320 may define a physical structure of the system 300 (e.g.,
`a chassis, body and/or enclosure). The UCP 310 may, for
`example, comprise a rear portion of the system 300 while the
`USUIC device 320 may define the frontal and/or side
`portions of the system 300. According to some embodi
`ments, the body, chassis, and/or structure of the system 300
`may be substantially entirely defined by the USUIC device
`320 and/or the UCP 310 may reside within the chassis and/or
`be enclosed within the USUIC device 320. In some embodi
`ments, fewer or more components than are shown in FIG. 3A
`and/or FIG. 3B may be included in the system 300.
`0023. In some embodiments, the system 300 and/or the
`USUIC device 320 may further comprise one or more input
`devices 322. As shown in FIG. 3A, for example, the input
`devices 322 may comprise any number, type, and/or con
`figuration of buttons, Switches, toggles, joysticks, and/or any
`other input devices that are or become known or practicable.
`In some embodiments, the input devices 322 may be coupled
`to one or more interface controllers and/or use-specific
`interface controllers (not shown in FIG. 3A or FIG.3B). The
`input devices 322 may, for example, be utilized to provide
`indications to the interface controllers to cause the UCP310
`to execute instructions associated with a specific use.
`According to Some embodiments, the input devices 322 may
`be configured, located, and/or otherwise situated in accor
`dance with the specific use. As shown in FIG. 3A, for
`example, the input devices 322 may be laid out on the
`USUIC device 320 to enhance the ease and/or functionality
`of a gaming use. The layout and/or selection of the input
`devices 322 may, for example, be chosen based upon market
`research regarding how users utilize and/or desire to utilize
`devices for gaming purposes. In some embodiments, the
`input devices 322 may also or alternatively be laid out in
`accordance with ergonomic and/or other considerations.
`0024. According to some embodiments, the layout of the
`input devices 322 may define which of the interface con
`trollers are associated with the input devices 322. Certain
`interface controllers may, for example, be located in areas
`beneath the input device 322 and the coupling of the USUIC
`device 320 to the UCP310 may electrically couple any input
`devices 322 to any interface controllers residing in areas
`underneath and/or near the input device 322. In other words,
`the locations of the interface controllers (e.g., the interface
`controllers 116a-n, 216a-n) may be determined to coordi
`nate with the use-specific locations of input devices 322 on
`the USUIC device 320. Other non-gaming interface control
`lers may reside under other unused portions of the USUIC
`device 320, for example, and may accordingly not be
`coupled to any of the input devices 322 of the gaming
`specific USUIC device 320. Other USUIC devices 320 may
`be coupled to the UCP310, however, to activate other and/or
`additional use-specific interface controllers within the sys
`tem 300 and/or the UCP 310.
`0025. In some embodiments, the system 300 may also or
`alternatively comprise a touch screen 330 having an inter
`face surface 332. The touch screen 330 and/or the interface
`surface 332 may, for example be utilized to activate interface
`controllers of the system 300 and/or the UCP 310, and/or
`may be otherwise utilized to interact with, control, and/or
`command the system 300. The interface surface 332 may,
`according to some embodiments, be an input and/or an
`output surface. The interface surface 332 may, for example,
`allow a user to interface with the system 300 via touch
`
`and/or may provide information to the user (such as via a
`display). In some embodiments, the interface surface 332
`may comprise a display Screen Such as a Liquid Crystal
`Display (LCD) and/or may comprise one or more contacts
`(not shown) associated with receiving input via touch. The
`contacts may, for example, be located within and/or under
`neath the interface surface 322. According to some embodi
`ments, the interface surface 322 may extend substantially to
`the extents of the touch screen 330, the USUIC device 320,
`and/or the system 300.
`0026. The interface surface 332 may, for example, com
`prise contacts that permit Substantially the entire face and/or
`side of the system 300 to be utilized as a touch interface
`and/or display. In some embodiments, the interface Surface
`332 may also or alternatively be shaped and/or formed to
`comprise substantially the entire surface of the system 300.
`Whereas typical touch screen devices are square and/or
`rectangular in configuration (possibly with a cover and/or
`other device hiding the sharp edges), for example, the touch
`screen 330 and/or the interface surface 332 may be formed
`in various Smooth, circular, rounded, and/or other shapes
`and/or combinations thereof, as desired. The touch screen
`330 and/or the interface surface 332 may, for example, be
`aesthetically and/or functionally shaped to comprise Sub
`stantially an entire side and/or surface of the system 300
`(and/or of the USUIC device 320). In some embodiments,
`the touch screen 330 may also or alternatively comprise a
`diaphragm of a speaker. The touch screen 330 may, for
`example, be utilized to facilitate the generation of voice,
`music, and/or other Sounds associated with the operation of
`the system 300. According to some embodiments, one or
`more portions of the touch screen 330 may be utilized as
`speaker diaphragms and/or other Sound-generation compo
`nentS.
`0027. In some embodiments, the system 300 may also or
`alternatively comprise other features and/or components.
`The system 300 may comprise, for example, a retractable
`and/or folding stand 340. The retractable stand 340 may, for
`example, be a device coupled via a hinge to the system 300,
`the USUIC device 320, and/or the UCP 310. In some
`embodiments, the retractable stand 340 may be moveably
`positioned in various orientations. The retractable stand 340
`may, for example, be folded up against, retracted into, and
`or deployed from the system 300 (and/or the chassis or body
`thereof). According to Some embodiments, the retractable
`stand 340 may be deployed to allow the system 300 to be
`positioned on a Substantially planar Surface, for example,
`such that the touch screen 330 may be oriented in a manner
`similar to a traditional TV or computer monitor (e.g., for
`desktop viewing and/or use). The retractable stand 340 may
`be stowed, removed, retracted, folded, and/or otherwise
`un-deployed, according to some embodiments, to allow the
`system 300 to be more easily transported, stored, and or
`utilized as a "laptop' in a tablet configuration.
`0028. In some embodiments, the system 300 may com
`prise an accessory module 350. The accessory module 350
`may, as shown in FIG. 3B, for example, be a device that is
`removably coupled to the back of the system 300, the chassis
`thereof, and/or to the UCP 310 (and/or a chassis thereof).
`According to some embodiments, the accessory module 350
`may be or include a device such as a Digital Video Disk
`(DVD) player or Compact Disk (CD) drive, a memory
`device (such as a removable hard drive), a communications
`
`13
`
`

`

`US 2007/0006146 A1
`
`Jan. 4, 2007
`
`device (such as a wireless and/or satellite device), a power
`Supply (such as a battery), and/or any other device or
`combination of devices that is or becomes practicable.
`0029 Turning now to FIG. 4, a perspective diagram of a
`system 400 according to some embodiments is shown. The
`system 400 may, for example, be similar in functionality
`and/or configuration to the systems 100, 200, 300 described
`in conjunction with any of FIG. 1, FIG. 2, FIG. 3A, and/or
`FIG. 3B herein. In some embodiments the system 400 may
`be or include a mobile computational platform. The system
`400 may comprise, for example, a UCP 410, a USUIC
`device 420, and/or a touch screen 430. The touch screen 430
`may, according to Some embodiments, be similar to the
`touch screen 330 described in conjunction with FIG. 3A
`herein. The touch screen 430 may comprise, for example, an
`interface surface 432 and/or one or more interface areas 434.
`In some embodiments, fewer or more components than are
`shown in FIG. 4 may be included in the system 400.
`0030. According to some embodiments, the interface
`areas 434 of the touch screen 430 may be or include areas
`of the touch screen 430 and/or of the interface surface 432
`that are associated with performing various tasks and/or
`executing certain commands. The interface areas 434 may,
`for example, be areas defining one or more soft-keys that
`change functionality based upon the current display of the
`touch screen 430. The interface areas 434 may also or
`alternatively be or include areas that may be defined and/or
`programmed by a user in accordance with the user's needs
`and/or desires. In other words, the interface areas 434 may
`be dedicated touch button areas of the interface surface 432
`that may be defined and/or configured as needed and/or as
`desired (e.g., they may not change functionality based upon
`content of the touch screen 430). According to some
`embodiments, the interface areas 434 may be coupled to a
`controller (not shown) that is capable of managing signals
`received via the interface surface 432.
`0031. The controller may, for example, be a software
`controller (e.g., stored in memory of the UCP 410) that is
`configured to receive indications associated with input
`received via the interface surface 432 and/or via the interface
`areas 434. In some embodiments, the software controller
`may be operable to interpret signals received from the
`interface areas 434. The software controller may, for
`example, cause a processor (Such as the processor 112, 212)
`of the UCP 410 to execute instructions associated with the
`interface areas 434. In some embodiments, the software
`controller may also be operable to deactivate areas of the
`interface Surface 432. In the case that an input indication is
`received from an area of the interface surface 432 near, at,
`and/or adjacent to one of the interface areas 434, for
`example, the Software controller may deactivate the areas
`Surrounding the interface areas 434. This may, for example,
`substantially prevent a touch input intended for one of the
`interface areas 434 from being interpreted as an indication
`associated with another interface area 434 and/or with a
`different portion of the non-dedicated interface surface 432.
`In other words, the software controller may interpret touch
`screen 430 input to substantially prevent inaccurate touch
`inputs from unnecessarily and/or undesirably activating an
`unintended interface controller. In some embodiments, the
`deactivation by the software controller may be associated
`with various indications. The interface areas 434 and/or
`other portions of the interface surface 432 may, for example,
`
`comprise electro-luminescent material that may provide
`visual (e.g., light) indications associated with a users touch
`(e.g., selection of an interface areas 434) and/or with the
`deactivation of Surrounding portions of the interface Surface
`432.
`0032. In some embodiments, the system 400 may com
`prise a stand 440 and/or a camera 442. The stand 440 may,
`for example, be similar to the retractable stand 340 described
`in conjunction with FIG. 3A and FIG. 3B. The stand 440
`may, according to some embodiments, be removable (e.g., as
`opposed to retractable). The stand 440 may, for example, be
`a device that Snaps onto and/or otherwise mechanically
`couples to the apparatus 400 to facilitate standard desktop
`viewing orientations. In some embodiments, the stand 440
`may be or include a docking station and/or similar device
`that not only orients the system 400 for standard desktop
`and/or other viewing but also provides power and/or other
`electrical interfaces or connectors with which the system
`400 may couple.
`0033. The camera 442 may, in some embodiments, be a
`retractable camera 442 as shown in FIG. 4. The camera 442
`may, for example, be or include a digital still image and/or
`a digital video camera coupled to the UCP 410 and/or to the
`USUIC device 420. The camera 442 may, for example, be
`included only on those USUIC devices 420 that may be
`associated with camera usage (e.g., gaming, graphical
`design and/or editing, photo editing, and/or remote meeting
`USUIC devices 420), while the UCP 410 may simply
`comprise a connector (not shown) operable to interface with
`the camera 442 in the case that is present. The camera 442
`may be retractable for convenience and/or for protection
`from dust and/or traveling or transportation damage. In
`Some embodiments, the camera 442 may be substantially
`Smaller and/or more low-profile than Standard cameras. The
`camera 442 may, for example, be configured to include slim
`components and/or a slim profile Such that the camera 442
`may retract into the apparatus 442. According to some
`embodiments, the camera 442 may receive power from the
`UCP410. The connector in the UCP 410 operable to couple
`to the camera 442 may, for example, comprise a Universal
`Serial Bus (USB) connector capable of managing signals in
`accordance with the USB Specification Revision 2.0 (2000).
`The camera 442 may also or alternatively be configured to
`be coupled to an interface controller of the UCP 410. The
`interface controller may, for example, automatically activate
`the camera 442 in accordance with use-specific instructions
`being executed by the system 400. In some embodiments,
`the retraction of the camera 442 may automatically trigger
`power State management of the camera 442. The camera 442
`may be deactivated and/or set to a "power-saving mode, for
`example, to conserve power when the camera 442 is not
`being actively utilized (e.g., in the case that the camera 442
`is retracted).
`0034) Referring to FIG. 5, a block diagram of an appa
`ratus 550 according to some embodiments is shown. The
`apparatus 550 may, for example, be or include a module
`such as the accessory module 350 configured to be coupled
`to one of the systems 100, 200, 300, 400 described herein.
`In some embodiments, the apparatus 550 may be or include
`a DVD player and/or module. The apparatus 550 may, for
`example, be a DVD module operable to be removably and/or
`securely attached to a mobile computational platform Such
`as a platform including a UCP and/or a USUIC. According
`
`14
`
`

`

`US 2007/0006146 A1
`
`Jan. 4, 2007
`
`to some embodiments, the apparatus 550 may be configured
`to be removably attached to the back of a mobile platform
`as described herein. The apparatus 550 may, for example,
`comprise one or more latching mechanisms 552 to couple
`the apparatus 550 to a mobile platform. In some embodi
`ments, fewer or more components than are shown in FIG. 5
`may be included in the apparatus 550.
`0035) In some embodiments, a chassis (not shown) of a
`mobile platform (and/or of a UCP or a USUIC) may be
`configured to accept the apparatus 550. The apparatus 550
`may, for example, slide into one or more channels, detents,
`and/