Wide touchpad on a portable computer

Information

  • Patent Grant
  • 11379060
  • Patent Number
    11,379,060
  • Date Filed
    Tuesday, November 7, 2017
    6 years ago
  • Date Issued
    Tuesday, July 5, 2022
    a year ago
Abstract
In one exemplary embodiment, a portable computer having a display assembly coupled to a base assembly to alternate between a closed position and an open position. Palm rest areas are formed by a touchpad disposed on the surface of the base assembly. In an alternative embodiment, a touchpad disposed on the base assembly has a width that extends substantially into the palm rests areas of the base assembly.
Description
TECHNICAL FIELD

The invention relates generally to portable computers, and in one embodiment, a portable computer having a wide touchpad.


BACKGROUND

Advances in technology have enabled the size of personal computers to decrease. As a result, the use of portable computers, such as notebook computers, laptop computers, and notepad computers, is rapidly increasing. The portability of notebook computers and notepad computers enables a user to keep his or her computer readily accessible such that computing resources are effectively always at hand. FIG. 1 illustrates a typical notebook computer with two folding halves, with a display assembly in one half and a base assembly with input devices in the other half. Input devices include, among other things, a keyboard for inputting data and a touchpad for navigating a cursor control. Palm rest areas are areas positioned on the upper surface of the base assembly below the keyboard. They allow a user to rest the base or palm of his or her hands comfortably during typing activity. The vast majority of conventional touchpads that are integrated into portable computers are, in one way or another, isolated from unwanted contact with the user's hands (e.g., during a typing activity). This is usually done by centering the touchpad below the keyboard, and minimizing the size of the touchpad, for example, by not extending the touchpad to the palm rest areas to be formed on either side of the touchpad. The touchpad is also recessed beneath the plane of the palm rest, so that palms, the most common cause of unwanted activation of the touchpad, do not come in contact with the touchpad.


One trend in portable computers has been to make them as desktop computer replacements, which requires them to be larger, while still maintaining their portability features. The display assembly in particular, that includes a display screen, has become larger, to become comparable to the sizes of desktop computer monitors. This has caused the housing of the base assembly to increase proportionally. Large base assembly housings can easily accommodate full-size keyboards, but the size of the touchpads must still be limited because of the high risk of unwanted activation, as discussed above, as well as providing the necessary space for palm rests.


Moreover, in order for larger portable computers to be practical for portability purposes, they must still be relatively thin and light. One conventional method to reduce the overall thickness of portable computers is to mount the touchpad flush with the top surface of the base assembly housing (e.g., the palm rest areas). However, this increases the likelihood of accidental brushing by a user's palms, especially during typing.


SUMMARY

Embodiments of a portable computer having one or more input devices including a keyboard and an enlarged or wide touchpad are described herein. A portable computer includes a display assembly and a base assembly coupled by hinge assembly that allows display assembly to change (i.e., rotate) between an open position and a closed position. The display assembly includes a display screen which displays images, data, and a moveable cursor. The wide touchpad and keyboard disposed on the base assembly allow a user to interact with the display screen (e.g., enter data). In one embodiment, the wide touchpad may be a cursor control device having the capabilities of conventional computer mouse devices, such as the ability to point, drag, tap, and double tap objects on a graphical user interface, as well as more general purposes such as scrolling, panning, zooming, and rotating images on display screen. The wide touchpad extends into the areas on the surface of the base assembly that are normally reserved for palm rest areas (e.g., flat areas on the surface of the base assembly that support a user's palms and/or wrists while typing).


In one embodiment, the wide touchpad filters each contact or contact patch sensed to either accept the contact as an intentional input command (e.g., cursor control command), or reject the contact as unintentional (e.g., when operating as a palm rest). The wide touchpad can filter multiple contact patches in order to accept a particular contact patch in one area of the touchpad while rejecting a second contact patch elsewhere on the wide touchpad. In one embodiment, a sensor is disposed between the keyboard and touchpad. The sensor defines a planar sensing region extending upwards from the top surface of the base assembly. The sensor detects a user's hand that may be resting on the base assembly with a palm portion making contact with a portion of the wide touchpad and the fingers extending toward keyboard. When this detection is made, any contact made with a corresponding portion of the touchpad is rejected, having been interpreted as unintentional contact by the user. Alternatively, detection of fingers extending toward the keyboard may be evaluated as one of many factors used to decide whether and what significance to accord to contact with the touchpad. For example, other factors may include the profile of the contact with the touchpad, the level of keyboard activity at the time of contact, etc. In this way, the touchpad may effectively serve as a palm rest (e.g., the user may intentionally rest one or more palm or other part of a hand or aim on a portion of the touchpad, which is recognized as an unintentional input) in addition to a functional touchpad when an input is interpreted as being an intentional contact by the user.


There are numerous other embodiments which are described herein, and these embodiments generally relate to portable computers having a wide touchpad and the accepting or rejecting of contact patches on the touchpad based on, in one example, hand location.





BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not limitation, in the figures of the accompanying drawings in which:



FIG. 1 illustrates a conventional portable computer.



FIG. 2 illustrates one embodiment of a portable computer having a wide touchpad.



FIG. 3 illustrates a top view of the portable computer of FIG. 2 in the open position with a touchpad that extends into the palm rest areas.



FIG. 4 illustrates one example of a hand position during user activity with a portable computer.



FIG. 5 illustrates another example of a hand position during user activity with a portable computer.



FIG. 6 illustrates another example of a hand position during user activity with a portable computer.



FIG. 7 illustrates a side view of a hand in a typing position with the portable computer of FIG. 2.



FIG. 8 illustrates a cross-sectional view of FIG. 7 taken along line A-A through the base assembly, sensor, and hand with showing one embodiment of a sensor.



FIG. 9 illustrates a cross-sectional view of FIG. 7 taken along line A-A through the base assembly, sensor, and hand with showing another embodiment of a sensor.



FIG. 10 illustrates a logic diagram of one embodiment of a portable computer system that supports a wide touchpad and/or hand sensor.



FIG. 11 illustrates a flowchart of one embodiment of an operation for rejecting or accepting a contact patch.



FIG. 12 illustrates an alternative embodiment of a hand detecting sensor that may be disposed on a portable computer.





DETAILED DESCRIPTION

In the following description, numerous specific details are set forth such as examples of specific, components, circuits, processes, etc. in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that these specific details need not be employed to practice the present invention. In other instances, well known components or methods have not been described in detail in order to avoid unnecessarily obscuring the present invention.


The term “coupled” as used herein means connected directly to or indirectly connected through one or more intervening components, structures or elements. The terms “above,” “below,” and “between” as used herein refer to a relative position of one component or element with respect to other components or elements. As such, one component disposed above or below another component may be directly in contact with the other component or may have one or more intervening component. Moreover, one component disposed between other components may be directly in contact with the other components or may have one or more intervening components.


Various embodiments of a portable computer (also referred to as notebook computer or laptop computer) having enlarged touchpads are described. The touchpad provides input and conventional cursor control capabilities such as pointing, dragging, tapping, scrolling, panning, rotating, and zooming. In one embodiment of the present invention, the touchpad serves as palm rests for a user's hands during a typing activity. In another embodiment of the present invention, the touchpad is enlarged so as to expand along a substantial width of the portable computer base assembly, extending into the palm rest areas. The palm rest areas include those areas on the front, top portion of the base assembly, and the keyboard is located behind the palm rest areas on the base assembly. Thus, in normal use by a user, the palm rest areas are closer to the user than the keyboard, which is normally adjacent to the hinge which couples the base assembly to the display assembly. The palm rest areas typically include a left palm rest area and a right palm rest area with a central portion separating these left and right palm rest areas. In prior art portable computers, this central portion typically includes a touchpad or other cursor control device. Advantages of a large touchpad for a portable computer include increased area for dynamic input ranges, two-handed control of the touchpad, and advanced input based on more than one finger on the touchpad.


In one embodiment, the touchpad possesses the ability to reject accidental contact when a user does not intend to activate the touchpad (e.g., the touchpad is able to distinguish when a user is contacting the touchpad for intended use or is merely resting his or her palms on a particular portion of the touchpad during a typing activity). In one particular embodiment, a sensor is disposed near the touchpad and keyboard of the portable computer to sense hand location of a user, and subsequently determine whether the touchpad contact is intentional or accidental. The touchpad responds properly by either recognizing the action on the touchpad or rejecting the action. As a result, the user is able to work efficiently, allowing for typing and cursor control operations to occur seamlessly. In one embodiment, the enlarged touchpad/palm rest may be suitable for use with portable computers having base and display assemblies (e.g., display frame, base assembly housing) made entirely or partially of metallic materials, in particular, display and base housings made of metals such as steel, aluminum, titanium, or combinations thereof.



FIG. 2 illustrates a perspective view of one embodiment of a portable computer 200 that includes a display assembly 210 and a base assembly 220. Display assembly 210 is coupled to base assembly 220 with a hinge assembly 216 that allows display assembly 210 to change (i.e., rotate) between an open position (as illustrated in FIG. 2) and a closed position (not shown). Display assembly includes a display screen 212 and associated video circuitry (not shown). In one embodiment, display screen 212 may be a liquid crystal display unit. In an alternative embodiment, display screen 212 may be a video monitor or any well known display device. Display screen is centered and framed on display assembly 210 by bezel 214. In the open position, display screen 212 is exposed on display assembly 210. Input devices that include keyboard 222, touchpad 224, and actuation button(s) 226 (e.g., “mouse buttons”) are disposed on a top surface 232 of base assembly 220. Speakers 260, 262 may also be disposed on top surface 232 of base assembly 220.


In one embodiment, touchpad 224 may be an input device having the capabilities of conventional computer mouse devices, such as the ability to point, drag, tap, and double tap objects on a graphical user interface, as well as more general purposes such as scrolling, panning, zooming, and rotating images on display screen 212. Touchpad 224, along with keyboard 222 and actuation button 226, allows a user to communicate with portable computer 200 (e.g., interact with display screen 212 or enter data). In one embodiment, a touchpad is defined herein as any two dimensional surface sensor that can detect one or more objects on the touchpad surface (the touchpad input), and output information regarding the location, width, presence, and number of said objects, (the touchpad outputs), in a manner that can be interpreted by the computer system to generate cursor movement, or otherwise interpret a user's either intentional or unintentional input. In one embodiment, touchpad 224 may be a touchpad that utilizes capacitive sensing. The surface of the touchpad may include a grid of conductive metal wires covered by an insulator. When two electrically conductive objects come near each other without touching, their electric fields interact to form capacitance. Also, when another conductive material, such as a human finger, comes in contact with the touchpad surface, a capacitance forms.


The dimensions of touchpad 224, particularly the width (i.e., the distance parallel the row of keys on keyboard 222), are larger than conventional touchpads. In the embodiment illustrated in FIG. 2, touchpad 224 extends into the areas on the surface 232 of base assembly 220 that are normally reserved for palm rest areas (e.g., areas 252, 254, designated by circled hash marks), but still allows a user to rest his or her palms on the surface of touchpad 224. Alternatively, in addition to possessing conventional touchpad functionalities, all or particular portions of touchpad 224 may serve as palm rests for a user's hands. It should be noted that palm rest areas 252, 254 as described herein are not necessarily reserved only for a user's palms during a typing activity as other body parts may be placed on palm rest areas 252, 254. For example, a user's elbow or forearm may rest on any non-keyboard portion of base assembly 220 during use (e.g., leaning on the palm rest portion 254 with the left elbow or forearm while typing with the right hand).


As described in greater detail below, enlarged touchpad 224 is able to reject unintentional contact while accepting intentional contact related to input device functionality (e.g., cursor control commands). In one embodiment, a sensor 240 is disposed between keyboard 222 and touchpad 224. Sensor 240 defines a planar sensing region extending upwards from top surface 232. In one particular embodiment, sensor 240 detects a user's hand that may be resting on base assembly 220 with a palm portion making contact with a portion of touchpad 224 and the fingers extending toward keyboard 222. When this detection is made, any contact made with a corresponding portion of the touchpad is rejected, having been interpreted as unintentional contact by the user. Alternatively, detection of fingers extending toward keyboard 222 may be evaluated as one of many factors used to decide whether and what significance to accord to contact with touchpad 224. For example, other factors may include the profile of the contact with touchpad 224, the level of keyboard 222 activity at the time of contact, etc. In this way, touchpad 224 may effectively serve as a palm rest (e,g., the user may intentionally rest one or more palm or other part of a hand or arm on a portion of the touchpad and the system recognizes this and interprets the input as unintentional) in addition to a functional touchpad when an input is interpreted as being an intentional contact by the user. FIG. 3 illustrates a top view of portable computer 200 in the open position with touchpad 224 that extends into the palm rest areas on top surface 232. In one embodiment, touchpad 224, having particularly wide dimension, is divided into three regions, a left region 242, a center region 244, and a right region 246. Sensor 240, which in one embodiment is a sensor strip having a width substantially similar to a width of touchpad 224, is disposed between keyboard 222 and touchpad 224. The three regions of touchpad 224 may be activated or deactivated selectively, based on a particular touch region or “contact patch” sensed by touchpad 224 in association with the particular region of sensor 240 that detects a hand portion or fingers extending towards the keys of keyboard 222. In an alternative embodiment, only the specific contact patch in a region (and not the entire region) may be accepted or rejected selectively. It will be recognized that other configurations of sensor 240 are possible, for example, sensor 240 may be multiple sensors, or may not be coextensive with touchpad 224.



FIGS. 4-6 illustrate three of many possible scenarios (i.e., hand positions) of user activity with portable computer 200 and the recognition by the three regions of touchpad 224 that may either accept or reject contact. FIG. 4 illustrates a typical typing position by a user in which the fingers of left hand 280 and right hand 282 extend over keyboard 222 and both palms rest on regions of touchpad 224. In particular, left hand 280 rests entirely on left region 242, and right hand 282 rests on right region 246. Sensor 240 detects the extension of the fingers from left hand 280 and associates the fingers with the contact made on left region 242. Similarly, sensor 240 associates the fingers from right hand 282 with the contact made on right region 246. Accordingly, the contact patches on left region 242 and right region 246 are not recognized as any form of input or touchpad operation. The user's hands may rest comfortably on these regions of touchpad 224, and in doing so, left region 242 and right region 246 serve as palm rests. In contrast, center region 244 of touchpad 224 may be active and be responsive to touchpad sensing.



FIG. 5 illustrates another scenario in which the fingers of left hand 280 extend over the keys of keyboard 222 while a finger from right hand 282 makes contact with touchpad 224. In this scenario, the contact made by right hand 282 is intentional and meant to activate a touchpad action (e.g., pointing, dragging, tapping). Sensor 240 detects the extension of the fingers from left hand 280 and associates the fingers with the contact made on left region 242. For right hand 282, the fingers do not extend over keyboard 222 and no detection is made by sensor 240. Accordingly, the contact patch on left region 242 is not recognized as any form of touchpad operation. However, the contact patch on right region 246 of touchpad 224 is recognized as a valid touchpad activity, and responds with the appropriate touchpad command (e.g., dragging, pointing). The user's left hand 280 may rest comfortably on left region 242 of touchpad 224 and engage in typing activity, while the fingers from right hand 282 engage in touchpad activity. In one embodiment, center region 244 of touchpad 224 may also be active and be responsive to touchpad sensing.



FIG. 6 illustrates a third scenario in which both left hand 280 and right hand 282 do not extend over keyboard 222. This hand position may occur when the user engages only in touchpad activity. In this scenario, portions of left hand 280 rests on left region 242 while a finger from right hand 282 engages in touchpad activity, and no portions from either hand extend over keyboard 222. The contact patch made by the finger of right hand 282 is intentional and meant to activate a touchpad action/input (e.g,, pointing, dragging, tapping). The contact patches made by left hand 280 is unintentional. Although no detection is made by sensor 240, touchpad 224 recognizes various characteristics of the contact patches made by the user's hands. In this case, the multiple contact patches recognized in left region 242, taking into consideration the size of the patches and proximity, are interpreted by touchpad 224 as unintentional. Accordingly, the activity in left region 242 is disregarded. Alternatively, all of left region 242 may be inactivated or the inputs are ignored or filtered. However, the single contact patch on right region 246 of touchpad 224 is recognized as a valid touchpad activity, and responds with the appropriate touchpad command (e.g., dragging, pointing). In one embodiment, center region 244 of touchpad 224 may also be active and be responsive to touchpad sensing.


In an alternative embodiment, touchpad 224 is capable of multiple or two-handed input. With reference again to FIG. 6, touchpad 224 may accept the contact patch from the finger of right hand 282 for cursor control operation. The contact patches from left hand 280 may also be accepted when associated with touchpad input device functionality. For example, two fingers from left hand 280 may be used to control scrolling, panning, rotation, and zooming of objects or data on the display screen (e.g., display screen 212).



FIGS. 4-6 illustrate touchpad 224 as being divided into three distinct sensing regions. However, it may be appreciated that any number of sensing regions may be divided over touchpad 224, and not necessarily in the relative dimensions illustrated. For example, sensor 240 can detect the extension and retraction of one finger at a time to that a single finger can be moved back and forth between touchpad 224 and keyboard 222, being active in both places, without moving the entire hand. It will also be recognized that touchpad 224 can be activated/deactivated in portions. It can also be activated/deactivated one input (i.e., contact patch) at a time, by disregarding any particular input that is determined to be related to unintended contact rather than intentional interface activity. That is, touchpad 224 is “deactivated” if it disregards a particular input, even if the next input may be not disregarded.



FIGS. 7-9 illustrate in greater detail, in one embodiment, the sensing of a user's fingers over the keys of keyboard 222. In the side view of FIG. 7, left hand 280 is illustrated in a typing position with respect to portable computer 200 in the open position (i.e., display assembly 210 rotated open relative to base assembly 220). Palm 281 rests on touchpad 224, and fingers 283 extend over sensor 240 and keyboard 222. As described above, the palm rest for palm 281 includes touchpad 224 because of the extra-wide or elongated dimensions of touchpad 224. FIG. 8 illustrates a cross-sectional view of FIG. 7 taken along line A-A through base assembly 220, sensor 240, and left hand 280. In one embodiment, sensor 240 includes a first imaging sensor 275 and a second imaging sensor 276. The imaging sensors may be infrared (IR) sensors that look “upward” (designated by the dash lines) and “see” the cross-sectional view of A-A. First and second imaging sensors 275, 276 examine a planar region in space extending upwards from the general line of sensor 240. For example, the fingers 283 of left hand 280 that breaks the planar region examined by first sensor 275. The sensing of fingers 283 may be associated with the contact patch made by palm 281 on touchpad 224 (e.g., on left region 242 as illustrated in FIG. 4), and as a result, either the entire left region 242 would not be active for any type of touchpad operation or the particular contact patch made by the palm 281 would be rejected, allowing for palm 281 to rest on touchpad 224. Because second sensor 276 does not detect any breaks along its portion of the planar region, portions of touchpad 224 associated with second sensor 276 are responsive to touchpad commands or operations (e.g., middle region 244 and right region 246).



FIG. 9 illustrates an alternative embodiment of a sensor mechanism for sensor 240. Multiple optical emitter-detector pairs (e.g., pairs 277, 278) are disposed along the sensor strip area to detect the presence or absence of a user's hand in the sensed plane (i.e., a planar region in space extending upwards from the general line of sensor 240). The results produced by the emitter-detectors pairs are similar to that produced by the IR sensors (e.g., first and second sensors 275, 276) described above with respect to FIG. 8. The fingers 283 of left hand 280 breaks the planar region examined by the emitter-detector pairs 277, 278 near one side of sensor 240. The sensing of fingers 283 may be associated with the contact patch made by palm 281 on touchpad 224 (e.g., on left region 242 as illustrated in FIG. 4), and as a result, either the entire left region 242 would not be active for any type of touchpad operation or the particular contact patch made by the palm 281 would be rejected, allowing for palm 281 to rest on touchpad 224. The emitter-detector pairs 277, 278 do not detect any breaks along the planar region near the other end of fingers 283. Accordingly, portions of touchpad 224 associated with the undetected sensor regions would be responsive to touchpad commands or operations (e.g., middle region 244 and right region 246).


The infrared sensors of first sensor 275 and second sensor 276, as well as optical emitter-detector pairs 277, 278 are just two of many possible sensing mechanism that may be used for detecting a hand location. In alternative embodiments, sensor 240 may be a capacitive sensor or visible light/shadow sensor. It may be appreciated that sensor 240 does not necessarily have to be utilized with an enlarged or wide touchpad, as illustrated, for detecting a hand location. The IR sensors and optical emitter-detector sensors described herein may be associated with touchpad of any dimension (e.g., a touchpad having dimensions comparable to the dimensions of center region 244).


Referring again to FIG. 3, inside base assembly 220, there may be all the essential and well known electronic circuitry for the operation of portable computer 200, such as a central processing unit (CPU), memory, hard disk drive, floppy disk drive, flash memory drive, input/output circuitry, and power supply. Such electronic circuitry for a portable computer is well known in the art; for example, a portable computer is the Macintosh PowerBook from Apple Computer, Inc. of Cupertino, California.


Keyboard 222 and touchpad 224 occupy almost all of top surface 232 of base assembly 220. In one embodiment, display assembly 210 has a width 211 and length 213 that is substantially similar to a width 217 and length 219 of base assembly 220 so that when display assembly 210 is closed over base assembly 220, the edges of the two assemblies are flush with each other. In one particular embodiment, portable computer 200 may have a display screen size of about 12 inches (about 305 millimeters (mm), the diagonal distance from one corner to the opposite corner of the display screen). Display assembly width 211 and base assembly width 217 may be about 277 mm and display assembly length 213 and base assembly length 219 may be about 219 mm. Keyboard 222 may be substantially centered along a width of base assembly 220, having a width 227 of about 274 mm and a length 228 of about 108 mm.


In one embodiment, keyboard 222 may be a full-size keyboard (i.e., a keyboard layout having dimensions similar to those of conventional desktop computer keyboards) having a conventional “QWERTY” layout, which also includes a large, elongated space bar key in the bottom row of the keyboard. The specific type of the keyboard (e.g., a “QWERTY” keyboard) that is used is not critical to the present invention.


Touchpad 224 has an elongated width that is substantially similar to a width of keyboard 222. Further, the width of the touchpad may be substantially similar to the width of base assembly 220. For example, the touchpad in certain embodiments may have a width which is about 70 to about 80% of the width of the base assembly. More generally, in other embodiments, the touchpad may have a width which is about 50% to about 95% of the width of the base assembly. Further, a substantial portion (e.g., more than 50% and typically more than 60%) of the palm rest area may include one or more touchpads. The width 223 of touchpad extends along width 227 of keyboard 222 so as to provide a palm rest area during typing activity. In one embodiment, touchpad 224 has a width 223 of about 274 mm and a length 225 of about 45 mm. While touchpad 224 is shown as being one contiguous touchpad, in alternative embodiments, several separate touchpads may be disposed in the left, right, and central palm rest areas, and these several separate touchpads may occupy a substantial portion (e.g., about 60% to about 70%) of the palm rest areas.


In an alternative embodiment, portable computer 200 may have a display screen size of about 17 inches (about 432 mm, the diagonal distance from one corner to the opposite corner of the display screen). Display assembly width 211 and base assembly width 217 may be about 392 mm and display assembly length 213 and base assembly length 219 may be about 259 ram Keyboard 222 may be a full-sized keyboard that is substantially centered along a width of base assembly 220. Keyboard 222 may have a width 227 of about 274 mm and a length 228 of about 108 mm. Touchpad 224 disposed on base assembly 220 for a 17-inch display screen may have an elongated width that is substantially similar to or exceeds a width of keyboard 222. The width of a base assembly for a 17-inch display screen may be greater compared to that of a base assembly for a 12-inch display screen. Although the dimensions of keyboard 222 may not be substantially different for the two display semen sizes, greater surface area would be provided in the base assembly for the 17-inch display screen. Accordingly, the palm rest areas formed by touchpad 224 may be larger for the 17-inch display screen base assembly. In one embodiment, touchpad 224 has a width 223 between about 274 mm to about 330 mm and a length 225 between about 45 mm to about 55 mm.


The dimensions for keyboard 222, and in particular, for touchpad 224 are examples only and it should be noted that a larger range of dimensions may be utilized, depending, for example, on the size of display screen 212 and the surface area available on the base assembly. In one embodiment, touchpad 224 may have a width 223 between about 100 mm to about 400 mm and a length 225 between about 45 mm to about 200 mm.



FIG. 10 illustrates a logic diagram of one embodiment of a portable computer system 300 (e.g., for portable computer 200) that supports a wide touchpad and/or hand sensor. Note that while FIG. 10 illustrates various components of a computer system, it is not intended to represent any particular architecture or manner of interconnecting the components as such details are not germane to the present invention. In one embodiment, the corresponding hardware components for the components described may be disposed on motherboard 301 as shown. The computer system of FIG. 10 may, for example, be an Apple Macintosh portable computer.


The portable computer system 300 includes a main logic board or motherboard 301 with at least one central processing unit (CPU) or processor 302, and one or more volatile memory units 304 such as random access memory (RAM) and read only memory (ROM), coupled to motherboard 301, as well as a graphics processor 308. More than one processor 302 may be part of system 300 (e.g., a dual processor system, or a dual core processor system). Processor 302 may be, for example, a G4 or G5 microprocessor from Motorola, Inc., or IBM, and is coupled to cache memory 306.


A memory controller 303 allows for the interface of memory unit 304 and graphics processor 308 with CPU 302. Graphics processor 308 is also coupled to a display device (e.g., display screen 212), which may be a high resolution device. Memory controller 303 also defines the speed at which data can flow between CPU 302, memory unit 304, and graphics processor 308 through bus 305. Bus 305 may also be referred to as front side bus (FSB), processor bus, memory bus or system bus. An input/out (I/O) controller 320 manages the interface of other components coupled to motherboard 301 such as storage device 324 (non-volatile), and local 110 322. Types of 110 devices include mice, modems, network interfaces, printers, scanners, video cameras, and other devices that are well known in the art.


In one embodiment, aspects of the recognition of user's hand location by sensor 240, and either accepting or rejecting a contact patch on touchpad 224 may be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as memory 304 (which may include ROM, RAM, cache 306, or a remote storage device). In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the present invention. Thus, the techniques are not limited to any specific combination of hardware circuitry and software or to any particular source for the instructions executed by the data processing system. In addition, throughout this description, various functions and operations are described as being performed by or caused by software code to simplify description. However, those skilled in the art will recognize what is meant by such expressions is that the functions result from execution of the code by a processor, such as the CPU 302.


A machine readable medium can be used to store software and data which when executed by a data processing system causes the system to perform various methods of the present invention. This executable software and data may be stored in various places including for example memory 304, cache 306, or storage device 324, as illustrated in FIG. 7. Portions of this software and/or data may be stored in any one of these storage devices.


Thus, a machine readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.). For example, a machine readable medium includes recordable/non-recordable media (e.g., read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; etc.), as well as electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), etc.


In at least one embodiment of the present invention, a sensor is disposed on the base assembly of a portable computer to detect a hand location. If the hand location extends from a contact patch on the touchpad to the keyboard, that particular contact patch may be recognized by the computer system as an unintentional or accidental contact, and therefore not registered as a touchpad command. FIG. 11 illustrates a flowchart of one embodiment of an operation 400 for rejecting or accepting a contact patch on a touchpad in association with a hand location. The operation may be performed for each contact patch detected on the touchpad. In one embodiment, a capacitive touchpad (e.g., touchpad 224) disposed on a top surface (e.g., surface 232) of a base assembly (e.g., 220) senses a contact patch on the touchpad. Any contact sensed by the touchpad may undergo a post processor algorithm in order interpret the contact properly. In one embodiment, the post processor is defined herein to be the software or firmware that converts the information coming from the touchpad sensor into a format that can be interpreted by the portable computer (e.g., processor 302). The post processor has as inputs, the touchpad outputs, which may include any type of physical contact made with the touchpad. The post processor then uses the post processor algorithm” to analyze each set of inputs (location, width, number of contacts, presence of contact, and hand location) to determine whether the contact patch should be accepted or rejected.


The starting point 402 of operation 400 may be when the portable computer is in a power “ON” state, with the display screen visible (e.g., displaying an image or data) and the various input devices (e.g., keyboard 222, sensor 240, and touchpad 224) in active and responsive states. When a contact patch is sensed on the touchpad, a location, trajectory, and size of the contact patch are determined, block 404. Trajectory refers to the path of the contact patch (e.g., movement of a finger on the touchpad during a dragging operation). The contact patch may be for example, the palm region of hand during a typing activity (e.g., palm 281 of FIG. 7) or during a pointing activity (e.g., right hand 282 of FIG. 5). Next, a hand location is made using a sensor (e.g., sensor 240) disposed on the base assembly of the portable computer, block 406. In one embodiment, the sensor may include one or more IR sensors (e.g., sensors 275, 276) disposed along a sensor strip between the keyboard and the touchpad. In an alternative embodiment, the sensors may be pairs of optical emitter-detectors (e.g., pairs 277, 278) disposed along a sensor strip between the keyboard and the touchpad.


Once a hand location is determined, a probability of intentional contact is estimated using the measured quantities of the contact patch location, trajectory, size of the contact patch, in addition to the hand location detected by the sensor, block 406. As discussed above, the touchpad may be divided into multiple sensing regions, for example, a left sensor region 242, center sensor region 244, and right sensor region 246 or there may be separate touchpads, one for each of these regions which are separated by small areas which are not touchpads. For example, the size of a contact patch made by palm 281 resting on left sensor region 242 would be larger compared to a contact patch made by a finger moving during a pointing or dragging cursor operation (e.g., finger of right hand 282 over right sensor region 246 illustrated in FIG. 5). In one embodiment, a contact patch having a relatively small size and a trajectory with a certain distance along the surface of the touchpad, coupled with no detection by the sensor would be initially estimated with a high probability of intentional contact. This may correspond to, for example, a pointing or dragging cursor operation. In contrast, a contact patch of a large size, and with no or minimal trajectory, coupled with detection by the sensor, would be initially estimated with a very low probability of intentional contact. This may correspond to a palm resting on the touchpad surface.


The estimated probabilities are repeatedly calculated to establish a narrow or strict accept/reject criteria for the contact patch, block 410, and the contact patch is also measured repeatedly over a period of time, block 412. These calculations are done repeatedly to provide the system with the most recent of sampling data. In one particular embodiment, the measurements may be repeated in the range of about 120 Hz to about 3 Hz. Lastly, the contact patch is accepted or rejected based on the criteria established from the measured contact patch/sensor calculations, block, 414. Once an accept/reject decision has been made, the operation ends, block 416.


The accept/reject operation 400 may further be described with respect to the scenarios in FIGS. 4-5. FIG. 4 illustrates a conventional typing position with the palms of both hands resting on touchpad 224 and fingers extending over keyboard 222. The contact patches made on left sensor region 242 and right sensor region 246 would be rejected. The relatively large sizes of the contact patches made by the palms in connection with the detection of hand location would be interpreted as unintentional or accidental contact. In this position, touchpad 224 operates only as a palm rest. FIG. 5 illustrates a dual mode position in which the left hand 280 is in a typing position and right hand 282 is in a touchpad position. The contact patch from left hand 280 (e.g., the palm) would be rejected because the location of left hand 280 would be detected by sensor 240. Accordingly, either the entire left sensor region 242, which is associated with the location of left hand 280 and the contact patch, or the particular contact patch made by left hand 280 on left sensor region 242 would be rendered inactive for touchpad commands, and operate only as a palm rest. The contact patch made by the finger of right hand 282 would be accepted as an intentional contact. The sensor would not detect any hand presence associated with right sensor region 246. As described above, the calculations performed by operation 400 include measuring the size and trajectory of the contact patch made by right hand 282. A comparison with the contact patch from left hand 280 may also be performed to establish the accept/reject criteria.



FIG. 12 illustrates an alternative embodiment of a hand detecting sensor that may be disposed on a portable computer. Portable computer 500 is illustrated in an open position with display assembly 510 rotated open with respect to base assembly 520. Base assembly 520 includes a wide touchpad 524 disposed below keyboard 522. An imaging sensor 545 is disposed on bezel 514 that frames display screen 512. Imaging sensor 545 detects an area of base assembly 520 that includes keyboard 222 and touchpad 524. When activated, imaging sensor 545 may detect a particular hand location and establish accept/reject criteria as described above (e.g., operation 400). In an alternative embodiment, imaging sensor 545 may also provide video-conferencing functionality when not operating as an imaging sensor.


In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.

Claims
  • 1. A first electronic device, comprising: a first input device configured to detect a presence of a first object; anda processor configured to receive data from the first input device;wherein: the processor is further configured to cause the first electronic device to switch operational states from a first operational state to a second operational state when a second object is detected at a first location by a second input device, different from the first input device;the second input device is configured to detect a presence of the second object, and a location of the second object, regardless of a presence or an absence of the first object at the first input device;the processor is further configured to cause the first electronic device to: while the first electronic device is in the first operational state: respond to inputs on a first portion of the first input device and inputs on a second portion of the first input device; andwhile the first electronic device is in the second operational state: respond to inputs on the first portion of the first input device and not respond to inputs on the second portion of the first input device; andthe first input device is disposed on a first assembly and the second input device is disposed on a second assembly, different from the first assembly.
  • 2. The first electronic device of claim 1, wherein the first input device comprises a plurality of touch sensors configured to detect a touching of the first object.
  • 3. The first electronic device of claim 1, wherein the processor is further configurable to switch operational states of the first electronic device when the second object is detected over a predetermined location in space by the second input device.
  • 4. The first electronic device of claim 1, wherein said switching of operational states comprises switching a function of the first electronic device from an active state to an inactive state.
  • 5. The first electronic device of claim 1, wherein the first input device is in a different location as compared to the second input device.
  • 6. The first electronic device of claim 1, wherein the second input device comprises a sensor configured to detect the second object.
  • 7. The first electronic device of claim 1, wherein the processor is further configured to: cause the first electronic device to switch from the first operational state to a third operation state when the second object is detected at a second location by the second input device, different from the first location, andwhile the first electronic device is in the third operational state: respond to inputs on the second portion of the first input device and not respond to inputs on the first portion of the first input device.
  • 8. The first electronic device of claim 1, wherein movement associated with the second input device causes a distance between the first input device and the second input device to change.
  • 9. A method performed by a first electronic device having a first input device configured to detect a presence of a first object, comprising: receiving one or more sense signals indicating detection of a second object by a second input device, different from the first input device, wherein the second input device is configured to detect a presence of the second object and a location of the second object;switching operational states of the first electronic device from a first operational state to a second operational state when the one or more sense signals indicating detection of the second object at a first location are received, regardless of a presence or an absence of the first object at the first input device;while in the first operational state: responding to inputs on a first portion of the first input device and inputs on a second portion of the first input device; andwhile in the second operational state: responding to inputs on the first portion of the first input device and not responding to inputs on the second portion of the first input device; andwherein: the first input device is disposed on a first assembly and the second input device is disposed on a second assembly, different from the first assembly.
  • 10. The method of claim 9, further comprising detecting a touching of the first object at the first input device.
  • 11. The method of claim 9, further comprising switching operational states of the first electronic device when the second object is detected over a predetermined location in space by the second input device.
  • 12. The method of claim 9, wherein said switching operational states comprises switching a function of the first electronic device from an active state to an inactive state.
  • 13. The method of claim 9, wherein the first input device is in a different location as compared to the second input device.
  • 14. The method of claim 9, further comprising detecting a hovering of the second object over a predetermined location in space.
  • 15. The method of claim 9, further comprising: switching operational states of the first electronic device from the first operational state to a third operational state when the one or more sense signals indicating detection of the second object at a second location, different than the first location, are received; andwhile in the third operational state: responding to inputs on the second portion of the first input device and not respond to inputs on the first portion of the first input device.
  • 16. The method of claim 9, wherein movement associated with the second input device causes a distance between the first input device and the second input device to change.
  • 17. A non-transitory computer-readable storage medium storing program code, which when executed by a first electronic device having a first input device configured to detect a presence of a first object, causes the first electronic device to perform a method, the method comprising: receiving one or more sense signals indicating detection of a second object by a second input device, different from the first input device, wherein the second input device is configured to detect a presence of the second object and a location of the second object;switching operational states of the first electronic device from a first operational state to a second operational state when the one or more sense signals indicating detection of the second object at a first location are received, regardless of a presence or an absence of the first object at the first input device;while in the first operational state: responding to inputs on a first portion of the first input device and inputs on a second portion of the first input device; andwhile in the second operational state: responding to inputs on the first portion of the first input device and not responding to inputs on the second portion of the first input device; andwherein: the first input device is disposed on a first assembly and the second input device is disposed on a second assembly, different from the first assembly.
  • 18. The non-transitory computer-readable storage medium of claim 17, wherein said switching operational states comprises switching a function of the first electronic device from an active to an inactive state.
  • 19. The non-transitory computer-readable storage medium of claim 17, the method further comprising: switching operational states of the first electronic device from the first operational state to a third operational state when the one or more sense signals indicating detection of the second object at a second location, different than the first location, are received; andwhile in the third operational state: responding to inputs on the second portion of the first input device and not respond to inputs on the first portion of the first input device.
  • 20. The non-transitory computer-readable storage medium of claim 17, wherein movement associated with the second input device causes a distance between the first input device and the second input device to change.
  • 21. The non-transitory computer-readable storage medium of claim 17, wherein the first input device comprises a plurality of touch sensors configured to detect a touching of the first object.
  • 22. The non-transitory computer-readable storage medium of claim 17, the method further comprising: switching operational states of the first electronic device when the second object is detected over a predetermined location in space by the second input device.
  • 23. The non-transitory computer-readable storage medium of claim 17, wherein the first input device is in a different location as compared to the second input device.
  • 24. The non-transitory computer-readable storage medium of claim 17, wherein the second input device comprises a sensor configured to detect the second object.
CROSS REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/354,931, filed on Nov. 17, 2016 and published on Mar. 9, 2017 as U.S. Patent Publication No. 2017-0068346, which is a continuation of U.S. patent application Ser. No. 13/351,096, filed on Jan. 16, 2012 and issued on Dec. 6, 2016 as U.S. Pat. No. 9,513,673, which is a continuation of U.S. patent application Ser. No. 11/731,118, filed on Mar. 30, 2007 and issued on Jan. 17, 2012 as U.S. Pat. No. 8,098,233, which is a continuation of U.S. patent application Ser. No. 10/927,575, filed on Aug. 25, 2004, and issued on Nov. 16, 2010 as U.S. Pat. No. 7,834,855, the contents of which are incorporated herein by reference in their entirety for all purposes.

US Referenced Citations (323)
Number Name Date Kind
4346376 Mallos Aug 1982 A
4477797 Nakagiri Oct 1984 A
4658690 Aitken et al. Apr 1987 A
4731058 Doan Mar 1988 A
4797514 Talmage, Jr. et al. Jan 1989 A
4992779 Sugino Feb 1991 A
5053758 Cornett et al. Oct 1991 A
5070467 Todome Dec 1991 A
5119079 Hube et al. Jun 1992 A
5347295 Agulnick et al. Sep 1994 A
5426450 Drumm Jun 1995 A
5434757 Kashiwagi Jul 1995 A
5481278 Shigematsu et al. Jan 1996 A
5483261 Yasutake Jan 1996 A
5488204 Mead et al. Jan 1996 A
5495077 Miller et al. Feb 1996 A
5528267 Ise Jun 1996 A
5541372 Baller et al. Jul 1996 A
5563632 Roberts Oct 1996 A
5591945 Kent Jan 1997 A
5757361 Hirshik May 1998 A
5764218 Della Bona et al. Jun 1998 A
5767457 Gerpheide et al. Jun 1998 A
5821922 Sellers Oct 1998 A
5825352 Bisset et al. Oct 1998 A
5835079 Shieh Nov 1998 A
5844506 Binstead Dec 1998 A
5856822 Du et al. Jan 1999 A
5864334 Sellers Jan 1999 A
5880411 Gillespie et al. Mar 1999 A
5943052 Allen et al. Aug 1999 A
5956291 Nehemiah et al. Sep 1999 A
5963671 Comerford et al. Oct 1999 A
5996080 Silva et al. Nov 1999 A
6002389 Kasser Dec 1999 A
6073036 Heikkinen et al. Jun 2000 A
6073120 Shiota et al. Jun 2000 A
6105419 Michels et al. Aug 2000 A
6118435 Fujita et al. Sep 2000 A
6154210 Anderson Nov 2000 A
6188391 Seely et al. Feb 2001 B1
6204839 Mato, Jr. Mar 2001 B1
6216988 Hsu et al. Apr 2001 B1
6243080 Molne Jun 2001 B1
6246395 Goyins et al. Jun 2001 B1
6266050 Oh et al. Jul 2001 B1
6308144 Bronfeld et al. Oct 2001 B1
6310610 Beaton et al. Oct 2001 B1
6313853 Lamontagne et al. Nov 2001 B1
6323846 Westerman et al. Nov 2001 B1
6336614 Kwitek Jan 2002 B1
6337678 Fish Jan 2002 B1
6369803 Brisebois et al. Apr 2002 B2
6380931 Gillespie et al. Apr 2002 B1
6414674 Kamper et al. Jul 2002 B1
6424338 Anderson Jul 2002 B1
6452514 Philipp Sep 2002 B1
6459424 Resman Oct 2002 B1
6480188 Horsley Nov 2002 B1
6492979 Kent et al. Dec 2002 B1
6501462 Gamer Dec 2002 B1
6504530 Wilson et al. Jan 2003 B1
6560612 Yamada May 2003 B1
6573844 Venolia et al. Jun 2003 B1
6597347 Yasutake Jul 2003 B1
6610936 Gillespie et al. Aug 2003 B2
6611253 Cohen Aug 2003 B1
6654001 Su Nov 2003 B1
6661920 Skinner Dec 2003 B1
6680677 Tiphane Jan 2004 B1
6690387 Zimmerman et al. Feb 2004 B2
6747636 Martin Jun 2004 B2
6756971 Ramey et al. Jun 2004 B1
6765557 Segal et al. Jul 2004 B1
6819312 Fish Nov 2004 B2
6903730 Mathews et al. Jun 2005 B2
6920619 Milekic Jul 2005 B1
6943705 Bolender et al. Sep 2005 B1
6943779 Satoh Sep 2005 B2
6958749 Matsushita et al. Oct 2005 B1
6961912 Aoki et al. Nov 2005 B2
6982695 Canova et al. Jan 2006 B1
7015894 Morohoshi Mar 2006 B2
7038659 Rajkowski May 2006 B2
7046230 Zadesky et al. May 2006 B2
7058902 Iwema et al. Jun 2006 B2
7088347 Iisaka et al. Aug 2006 B2
7103852 Kairls Sep 2006 B2
7148882 Kamrath et al. Dec 2006 B2
7176902 Peterson et al. Feb 2007 B2
7184064 Zimmerman et al. Feb 2007 B2
7199788 Ise et al. Apr 2007 B2
7277087 Hill et al. Oct 2007 B2
7289102 Hinckley et al. Oct 2007 B2
7289111 Asbill Oct 2007 B2
7298364 Matsuda Nov 2007 B2
7319454 Thacker et al. Jan 2008 B2
7345670 Armstrong Mar 2008 B2
7406666 Davis et al. Jul 2008 B2
7408538 Hinckley et al. Aug 2008 B2
7428142 Ligtenberg et al. Sep 2008 B1
7499040 Zadesky et al. Mar 2009 B2
7561146 Hotelling Jul 2009 B1
7564448 Yi Jul 2009 B2
7609178 Son et al. Oct 2009 B2
7623892 Hawkins Nov 2009 B2
7633076 Huppi et al. Dec 2009 B2
7639233 Marks Dec 2009 B2
7653883 Hotelling et al. Jan 2010 B2
7658675 Hotta Feb 2010 B2
7663607 Hotelling et al. Feb 2010 B2
7746325 Roberts Jun 2010 B2
7834855 Hotelling Nov 2010 B2
7843427 Ording et al. Nov 2010 B2
7852199 Desai et al. Dec 2010 B2
7855718 Westerman Dec 2010 B2
7876310 Westerman et al. Jan 2011 B2
7884804 Kong Feb 2011 B2
7911455 Nishikawa Mar 2011 B2
7934156 Forstall et al. Apr 2011 B2
7944215 Howard et al. May 2011 B2
7956849 Anzures et al. Jun 2011 B2
7986307 Zotov et al. Jul 2011 B2
8006002 Kalayjian et al. Aug 2011 B2
8072439 Hillis et al. Dec 2011 B2
8098233 Hotelling Jan 2012 B2
8174508 Sinclair et al. May 2012 B2
8232973 Kocienda et al. Jul 2012 B2
8253698 Chen et al. Aug 2012 B2
8284165 Koshiyama et al. Oct 2012 B2
8294047 Westerman et al. Oct 2012 B2
8321809 Eom Nov 2012 B2
8381135 Hotelling et al. Feb 2013 B2
8411060 Scholler et al. Apr 2013 B1
8445793 Westerman et al. May 2013 B2
8446375 Yasumi May 2013 B2
8479122 Hotelling et al. Jul 2013 B2
8654095 Cho et al. Feb 2014 B1
8698750 Malabuyo Apr 2014 B2
8701049 Kim Apr 2014 B2
8749507 DaCosta et al. Jun 2014 B2
8847903 Stokes et al. Sep 2014 B2
8896561 Engel Nov 2014 B1
8952899 Hotelling Feb 2015 B2
8970501 Hotelling et al. Mar 2015 B2
8970533 Westerman et al. Mar 2015 B2
9041663 Westerman et al. May 2015 B2
9116583 De Los Reyes Aug 2015 B1
9189142 Kim et al. Nov 2015 B2
9250734 Hotelling et al. Feb 2016 B2
9285913 Kang et al. Mar 2016 B1
9285988 Kenney et al. Mar 2016 B2
9367158 Hotelling et al. Jun 2016 B2
9423995 Arneson Aug 2016 B2
9513673 Hotelling Dec 2016 B2
9632608 Westerman et al. Apr 2017 B2
9830036 Hotelling et al. Nov 2017 B2
9891732 Westerman Feb 2018 B2
10026108 Jackson et al. Jul 2018 B2
20010015718 Hinckley et al. Aug 2001 A1
20020015024 Westerman et al. Feb 2002 A1
20020080123 Kennedy et al. Jun 2002 A1
20020140633 Rafii et al. Oct 2002 A1
20020158838 Smith et al. Oct 2002 A1
20030001899 Partanen et al. Jan 2003 A1
20030016253 Aoki et al. Jan 2003 A1
20030076363 Murphy Apr 2003 A1
20030095095 Pihlaja May 2003 A1
20030122787 Zimmerman et al. Jul 2003 A1
20030137497 Kojo Jul 2003 A1
20030160808 Foote et al. Aug 2003 A1
20030179201 Thacker Sep 2003 A1
20030206162 Roberts Nov 2003 A1
20030216890 Gross et al. Nov 2003 A1
20040004603 Gerstner et al. Jan 2004 A1
20040012572 Sowden et al. Jan 2004 A1
20040036680 Davis et al. Feb 2004 A1
20040046791 Davis et al. Mar 2004 A1
20040056845 Harkcom et al. Mar 2004 A1
20040066379 Lse et al. Apr 2004 A1
20040104894 Tsukada et al. Jun 2004 A1
20040108994 Kato Jun 2004 A1
20040119744 Chan Jun 2004 A1
20040145601 Brielmann et al. Jul 2004 A1
20040150668 Myers et al. Aug 2004 A1
20040150669 Sabiers et al. Aug 2004 A1
20040178994 Kairls Sep 2004 A1
20040207605 Mackey et al. Oct 2004 A1
20040217944 Kong Nov 2004 A1
20040227736 Kamrath et al. Nov 2004 A1
20040233624 Aisenberg Nov 2004 A1
20040245438 Payne et al. Dec 2004 A1
20050012723 Pallakoff Jan 2005 A1
20050015731 Mak et al. Jan 2005 A1
20050024341 Gillespie et al. Feb 2005 A1
20050052425 Zadesky et al. Mar 2005 A1
20050078093 Peterson et al. Apr 2005 A1
20050104867 Westerman et al. May 2005 A1
20050134578 Chambers et al. Jun 2005 A1
20050146512 Hill et al. Jul 2005 A1
20050162406 Ono et al. Jul 2005 A1
20050184696 Anastas et al. Aug 2005 A1
20050185364 Bell et al. Aug 2005 A1
20050223308 Gunn et al. Oct 2005 A1
20050243053 Liess et al. Nov 2005 A1
20050248534 Kehlstadt Nov 2005 A1
20050275567 DePue et al. Dec 2005 A1
20060001655 Tanabe Jan 2006 A1
20060012580 Perski et al. Jan 2006 A1
20060022956 Lengeling et al. Feb 2006 A1
20060026521 Hotelling et al. Feb 2006 A1
20060033701 Wilson Feb 2006 A1
20060038796 Hinckley et al. Feb 2006 A1
20060044259 Hotelling et al. Mar 2006 A1
20060050059 Satoh et al. Mar 2006 A1
20060052885 Kong Mar 2006 A1
20060066588 Lyon et al. Mar 2006 A1
20060071915 Rehm Apr 2006 A1
20060097991 Hotelling et al. May 2006 A1
20060109252 Kolmykov-Zotov et al. May 2006 A1
20060161870 Hotelling et al. Jul 2006 A1
20060181517 Zadesky et al. Aug 2006 A1
20060197753 Hotelling Sep 2006 A1
20060228149 Harley Oct 2006 A1
20060232567 Westerman et al. Oct 2006 A1
20060238517 King et al. Oct 2006 A1
20060238522 Westerman et al. Oct 2006 A1
20060256090 Huppi Nov 2006 A1
20060279548 Geaghan Dec 2006 A1
20060284836 Philipp Dec 2006 A1
20070002192 Nishino et al. Jan 2007 A1
20070015976 Miesel et al. Jan 2007 A1
20070046643 Hillis et al. Mar 2007 A1
20070052693 Watari Mar 2007 A1
20070075965 Huppi et al. Apr 2007 A1
20070119698 Day May 2007 A1
20070125633 Boillot Jun 2007 A1
20070126715 Funamoto Jun 2007 A1
20070146334 Inokawa Jun 2007 A1
20070150842 Chaudhri et al. Jun 2007 A1
20070152976 Townsend et al. Jul 2007 A1
20070152983 McKillop et al. Jul 2007 A1
20070182722 Hotelling et al. Aug 2007 A1
20070247429 Westerman Oct 2007 A1
20070247435 Benko et al. Oct 2007 A1
20070262968 Kazuhito et al. Nov 2007 A1
20070268275 Westerman et al. Nov 2007 A1
20070273665 Park et al. Nov 2007 A1
20080001924 De Los Reyes et al. Jan 2008 A1
20080012835 Rimon et al. Jan 2008 A1
20080012838 Rimon Jan 2008 A1
20080036743 Westerman et al. Feb 2008 A1
20080040692 Sunday et al. Feb 2008 A1
20080062144 Shahoian et al. Mar 2008 A1
20080082920 Eom Apr 2008 A1
20080121442 Boer et al. May 2008 A1
20080122798 Koshiyama et al. May 2008 A1
20080136788 Nishikawa et al. Jun 2008 A1
20080136792 Peng et al. Jun 2008 A1
20080140868 Kalayjian et al. Jun 2008 A1
20080158145 Westerman Jul 2008 A1
20080158172 Hotelling et al. Jul 2008 A1
20080158181 Hamblin et al. Jul 2008 A1
20080158185 Westerman Jul 2008 A1
20080165141 Christie Jul 2008 A1
20080192026 Mackey et al. Aug 2008 A1
20080196945 Konstas Aug 2008 A1
20080202824 Philipp et al. Aug 2008 A1
20080211779 Pryor Sep 2008 A1
20080231603 Parkinson et al. Sep 2008 A1
20080291225 Arneson Nov 2008 A1
20080297487 Hotelling et al. Dec 2008 A1
20080309632 Westerman et al. Dec 2008 A1
20090005165 Arezina et al. Jan 2009 A1
20090015564 Ye et al. Jan 2009 A1
20090085881 Kearn Apr 2009 A1
20090095540 Zachut et al. Apr 2009 A1
20090101417 Suzuki et al. Apr 2009 A1
20090141046 Rathnam et al. Jun 2009 A1
20090160785 Chen et al. Jun 2009 A1
20090160802 Yasumi Jun 2009 A1
20090167692 Tan et al. Jul 2009 A1
20090174667 Kocienda et al. Jul 2009 A1
20090174679 Westerman Jul 2009 A1
20090237372 Kim et al. Sep 2009 A1
20090244092 Hotelling Oct 2009 A1
20090256817 Perlin et al. Oct 2009 A1
20090284495 Geaghan et al. Nov 2009 A1
20090322351 McLeod Dec 2009 A1
20090327977 Bachfischer et al. Dec 2009 A1
20100039380 Lanier Feb 2010 A1
20100073302 Ritzau et al. Mar 2010 A1
20100099394 Hainzl Apr 2010 A1
20100139990 Westerman et al. Jun 2010 A1
20100141580 Oh Jun 2010 A1
20100141603 Hotelling Jun 2010 A1
20100200309 Yilmaz et al. Aug 2010 A1
20100201615 Tupman et al. Aug 2010 A1
20100261526 Anderson et al. Oct 2010 A1
20100318930 Townsend et al. Dec 2010 A1
20110037735 Land et al. Feb 2011 A1
20110088086 Swink et al. Apr 2011 A1
20110163996 Wassvik et al. Jul 2011 A1
20110258542 Kenney et al. Oct 2011 A1
20120019468 Westerman et al. Jan 2012 A1
20120023459 Westerman et al. Jan 2012 A1
20130222220 Tobita Aug 2013 A1
20130229376 Westerman et al. Sep 2013 A1
20140109017 Benko et al. Apr 2014 A1
20140111486 Zay et al. Apr 2014 A1
20140293165 Rekimoto Oct 2014 A1
20140300579 Rekimoto Oct 2014 A1
20150097780 Hotelling et al. Apr 2015 A1
20150153865 Westerman et al. Jun 2015 A1
20150193039 Hotelling et al. Jul 2015 A1
20150253872 Reyes Sep 2015 A1
20150253891 Westerman Sep 2015 A1
20150293633 Ray et al. Oct 2015 A1
20160282998 Hotelling et al. Sep 2016 A1
20170220165 Westerman et al. Aug 2017 A1
20180095560 Hotelling Apr 2018 A1
20180150152 Westerman May 2018 A1
20200371688 Westerman Nov 2020 A1
Foreign Referenced Citations (57)
Number Date Country
1818840 Aug 2006 CN
1 610 210 Dec 2005 EP
1 659 481 May 2006 EP
1 691 263 Aug 2006 EP
2 344 894 Jun 2000 GB
2 402 105 Dec 2004 GB
61-075981 Apr 1986 JP
05-257594 Oct 1993 JP
06-149466 May 1994 JP
06-289969 Oct 1994 JP
07-073278 Mar 1995 JP
09-044293 Feb 1997 JP
10-003349 Jan 1998 JP
10-289061 Oct 1998 JP
10-293644 Nov 1998 JP
11-194883 Jul 1999 JP
11-327788 Nov 1999 JP
2000-039964 Feb 2000 JP
2000-47824 Feb 2000 JP
2000-163031 Jun 2000 JP
2000-163211 Jun 2000 JP
2000-172441 Jun 2000 JP
2000-194507 Jul 2000 JP
2001-265519 Sep 2001 JP
2001-290585 Oct 2001 JP
2002-287889 Oct 2002 JP
2002-287903 Oct 2002 JP
2002-342033 Nov 2002 JP
2003-173237 Jun 2003 JP
2003-530772 Oct 2003 JP
2005-082086 Mar 2005 JP
2005-82806 Mar 2005 JP
2006-34754 Feb 2006 JP
2006-512626 Apr 2006 JP
2007-512619 May 2007 JP
2007-242035 Sep 2007 JP
2007-304757 Nov 2007 JP
2008-140182 Jun 2008 JP
2008-234212 Oct 2008 JP
2004-0103125 Dec 2004 KR
WO-9211623 Jul 1992 WO
WO-9843202 Oct 1998 WO
WO-2004025449 Mar 2004 WO
WO-2004025449 Mar 2004 WO
WO-2006026183 Mar 2006 WO
WO-2006026183 Mar 2006 WO
WO-2006-133018 Dec 2006 WO
WO-2006-133018 Dec 2006 WO
WO-2007076226 Jul 2007 WO
WO-2007089766 Aug 2007 WO
WO-2007089766 Aug 2007 WO
WO-2008085418 Jul 2008 WO
WO-2008085418 Jul 2008 WO
WO-2008094791 Aug 2008 WO
WO-2008094791 Aug 2008 WO
WO-2009088672 Jul 2009 WO
WO-2009088672 Jul 2009 WO
Non-Patent Literature Citations (144)
Entry
Anonymous. (Apr. 13, 2004). Proximity Sensor Demo Kit, User Guide, Version 0.62—Preliminary, Integration Associates, Inc., 14 pages.
Apple Computer, Inc., “Block Diagram and Buses” Apple Developer Connection, Aug. 3, 2004 downloaded from the Internet from http://developer.apple.com/documentation/Hardware/Developer_Notes/Macintosh_CPUs-G . . . (4 pages).
Apple Computer, Inc., “PowerBook G4” Technology Overview, Apr. 2004 (29 pages).
Chinese Search Report dated Jan. 19, 2019, for CN Application No. 201310489261.x, with English translation, four pages.
Communication for EP Patent Application No. 05788888.5-2224, dated Sep. 4, 2017, 2 pages.
Communication for EP Patent Application No. 05788888.5-2224, dated Sep. 1, 2008, 3 pages.
European Search Report dated Dec. 10, 2009, for EP Application No. 08022346.4, filed Dec. 23, 2008, ten pages.
European Search Report dated Apr. 24, 2012, for EP Application No. 12160763.4, filed Dec. 23, 2008, nine pages.
European Search Report dated Sep. 1, 2014, for EP Application No. 14157275.0, filed Dec. 21, 2007, nine pages.
European Search Report dated Nov. 2, 2015, for EP Application No. 15164429.1, four pages.
Final Office Action dated Feb. 5, 2008, for U.S. Appl. No. 11/731,118, filed Mar. 30, 2017, nine pages.
Final Office Action dated Feb. 20, 2008, for U.S. Appl. No. 10/927,577, filed Aug. 25, 2004, 11 pages.
Final Office Action dated Mar. 26, 2008, for U.S. Appl. No. 10/927,575, filed Aug. 25, 2004, 25 pages.
Final Office Action dated Mar. 4, 2009, for U.S. Appl. No. 11/731,118, filed Mar. 30, 2007, eight pages.
Final Office Action dated Mar. 5, 2009, for U.S. Appl. No. 10/927,575, filed Aug. 25, 2004, 16 pages.
Final Office Action dated Jan. 25, 2010, for U.S. Appl. No. 11/731,118, filed Mar. 30, 2007, nine pages.
Final Office Action dated Mar. 2, 2010, for U.S. Appl. No. 10/927,575, filed Aug. 25, 2004, 16 pages.
Final Office Action dated Sep. 16, 2010, for U.S. Appl. No. 12/479,741, filed Aug. 25, 2004, 11 pages.
Final Office Action dated Jun. 7, 2011, for U.S. Appl. No. 11/649,998, filed Jan. 3, 2007, eight pages.
Final Office Action dated Feb. 24, 2012, for U.S. Appl. No. 13/250,955, filed Sep. 30, 2011, 29 pages.
Final Office Action dated Mar. 22, 2012, for U.S. Appl. No. 13/251,013, filed Sep. 30, 2011, 18 pages.
Final Office Action dated Apr. 12, 2012, for U.S. Appl. No. 12/242,772, filed Sep. 30, 2008, 24 pages.
Final Office Action dated Jul. 27, 2012, for U.S. Appl. No. 12/479,741, filed Jun. 5, 2009, 14 pages.
Final Office Action dated Sep. 13, 2012, for U.S. Appl. No. 12/172,998, filed Jul. 14, 2008, 23 pages.
Final Office Action dated Oct. 12, 2012, for U.S. Appl. No. 13/351,096, filed Jan. 16, 2012, 17 pages.
Final Office Action dated Feb. 14, 2013, for U.S. Appl. No. 12/242,772, filed Sep. 30, 2008, 32 pages.
Final Office Action dated Nov. 22, 2013, for U.S. Appl. No. 12/172,998, filed Jul. 14, 2008, 22 pages.
Final Office Action dated Dec. 23, 2013, for U.S. Appl. No. 11/649,998, filed Jan. 3, 2007, ten pages.
Final Office Action dated Feb. 13, 2014, for U.S. Appl. No. 12/479,741, filed Jun. 5, 2009, 15 pages.
Final Office Action dated Mar. 27, 2014, for U.S. Appl. No. 13/250,955, filed Sep. 30, 2011, 28 pages.
Final Office Action dated Jul. 24, 2014, for U.S. Appl. No. 13/868,787, filed Apr. 23, 2013, 10 pages.
Final Office Action dated Nov. 10, 2014, for U.S. Appl. No. 12/172,998, filed Jul. 14, 2008, 24 pages.
Final Office Action dated May 20, 2016, for U.S. Appl. No. 14/619,958, filed Feb. 11, 2015, 30 pages.
Final Office Action dated Oct. 24, 2016, for U.S. Appl. No. 14/711,626, filed May 13, 2015, 14 pages.
Final Office Action dated Feb. 23, 2017, for U.S. Appl. No. 15/179,909, filed Jun. 10, 2016, nine pages.
GB Combined Examination and Search Report dated Nov. 26, 2010, for GB Application No. 1018237.6, filed Dec. 18, 2008, six pages.
GB Search Report dated Feb. 17, 2009, for GB Application No. 0823047.6, filed Dec. 18, 2008, two pages.
International Search Report dated Jul. 8, 2008, for PCT Application No. PCT/US2007/026182, filed Dec. 21, 2007, three pages.
International Search Report dated Dec. 30, 2009, for PCT/US2008/087041, filed Dec. 16, 2008, six pages.
Lee, S.K. et al. (Apr. 1985). “A Multi-Touch Three Dimensional Touch-Sensitive Tablet,” Proceesings of CHI: ACM Conference on Human Factors in Computing Systems, pp. 21-25.
Non-Final Office Action dated Aug. 22, 2007, for U.S. Appl. No. 10/927,575, filed Aug. 25, 2004, 21 pages.
Non-Final Office Action dated Aug. 22, 2007, for U.S. Appl. No. 11/731,118, filed Mar. 30, 2007, seven pages.
Non-Final Office Action dated Sep. 10, 2007, for U.S. Appl. No. 10/927,577, filed Aug. 25, 2004, 10 pages.
Non-Final Office Action dated Jul. 24, 2008, for U.S. Appl. No. 11/731,118, filed Mar. 30, 2007, 14 pages.
Non-Final Office Action dated Jul. 31, 2008, for U.S. Appl. No. 10/927,577, filed Aug. 25, 2004, 11 pages.
Non-Final Office Action dated Sep. 17, 2008, for U.S. Appl. No. 10/927,575, filed Aug. 25, 2004, 14 pages.
Non-Final Office Action dated Aug. 3, 2009, for U.S. Appl. No. 11/731,118, filed Mar. 30, 2007, 10 pages.
Non-Final Office Action dated Sep. 1, 2009, for U.S. Appl. No. 10/927,575, filed Aug. 25, 2004, 17 pages.
Non-Final Office Action dated Apr. 1, 2010, for U.S. Appl. No. 12/479,741, filed Aug. 25, 2004, 12 pages.
Non-Final Office Action dated Jun. 24, 2010, for U.S. Appl. No. 11/649,998, filed Jan. 3, 2007, six pages.
Non-Final Office Action dated Dec. 13, 2010, for U.S. Appl. No. 11/649,998, filed Jan. 3, 2007, eight pages.
Non-Final Office Action dated Oct. 12, 2011, for U.S. Appl. No. 12/242,772, filed Sep. 30, 2008, 19 pages.
Non-Final Office Action dated Nov. 9, 2011, for U.S. Appl. No. 13/250,955, filed Sep. 30, 2011, 32 pages.
Non-Final Office Action dated Nov. 17, 2011, for U.S. Appl. No. 13/251,013, filed Sep. 30, 2011, 13 pages.
Non-Final Office Action dated Jan. 4, 2012, for U.S. Appl. No. 12/479,741, filed Aug. 25, 2004, 17 pages.
Non-Final Office Action dated Feb. 6, 2012, for U.S. Appl. No. 12/691,702, filed Jan. 21, 2010, 13 pages.
Non-Final Office Action dated Feb. 24, 2012, for U.S. Appl. No. 12/242,794, filed Dec. 8, 2008, seven pages.
Non-Final Office Action dated Feb. 29, 2012, for U.S. Appl. No. 13/351,096, filed Jan. 16, 2012, 27 pages.
Non-Final Office Action dated Mar. 13, 2012, for U.S. Appl. No. 12/172,998, filed Jul. 14, 2008, 17 pages.
Non-Final Office Action dated Sep. 12, 2012, for U.S. Appl. No. 13/251,013, filed Sep. 30, 2011, 22 pages.
Non-Final Office Action dated Sep. 20, 2012, for U.S. Appl. No. 11/649,998, filed Jan. 3, 2007, seven pages.
Non-Final Office Action dated Oct. 11, 2012, for U.S. Appl. No. 12/242,772, filed Sep. 30, 2008, 19 pages.
Non-Final Office Action dated May 22, 2013, for U.S. Appl. No. 11/649,998, filed Jan. 3, 2007, eight pages.
Non-Final Office Action dated Jul. 15, 2013, for U.S. Appl. No. 12/172,998, filed Jul. 14, 2008, 21 pages.
Non-Final Office Action dated Jul. 22, 2013, for U.S. Appl. No. 13/351,096, filed Jan. 16, 2012, 11 pages.
Non-Final Office Action dated Sep. 25, 2013, for U.S. Appl. No. 13/868,787, filed Apr. 23, 2013, 20 pages.
Non-Final Office Action dated Nov. 14, 2013, for U.S. Appl. No. 13/250,955, filed Sep. 30, 2011, 27 pages.
Non-Final Office Action dated Feb. 21, 2014, for U.S. Appl. No. 13/868,787, filed Apr. 23, 2013, 20 pages.
Non-Final Office Action dated May 1, 2014, for U.S. Appl. No. 12/172,998, filed Jul. 14, 2008, 23 pages.
Non-Final Office Action dated Feb. 5, 2015, for U.S. Appl. No. 12/172,998, filed Jul. 14, 2008, 25 pages.
Non-Final Office Action dated Jun. 8, 2015, for U.S. Appl. No. 14/666,146, filed Mar. 23, 2015 nine pages.
Non-Final Office Action dated Jul. 2, 2015, for U.S. Appl. No. 14/570,915, filed Dec. 15, 2014, ten pages.
Non-Final Office Action dated Nov. 5, 2015, for U.S. Appl. No. 14/619,958, filed Feb. 11, 2015, 20 pages.
Non-Final Office Action dated Apr. 14, 2016, for U.S. Appl. No. 14/711,626, filed May 13, 2015, 13 pages.
Non-Final Office Action dated Aug. 24, 2016, for U.S. Appl. No. 15/179,909, filed Jun. 10, 2016, 11 pages.
Non-Final Office Action dated Apr. 19, 2017, for U.S. Appl. No. 14/711,626, filed May 13, 2015, 16 pages.
Notice of Allowance dated Mar. 6, 2009, for U.S. Appl. No. 10/927,577, filed Aug. 25, 2004, seven pages.
Notice of Allowance dated Jul. 12, 2010, for U.S. Appl. No. 10/927,575, filed Aug. 25, 2004, four pages.
Notice of Allowance dated Sep. 14, 2011, for U.S. Appl. No. 11/731,118, filed Mar. 30, 2007, seven pages.
Notice of Allowance dated Jun. 26, 2012, for U.S. Appl. No. 12/242,794, filed Dec. 8, 2008, 10 pages.
Notice of Allowance dated Jan. 24, 2013, for U.S. Appl. No. 13/251,013, filed Sep. 30, 2011, nine pages.
Notice of Allowance dated Oct. 1, 2014, for U.S. Appl. No. 12/479,741, filed Jun. 5, 2009, five pages.
Notice of Allowance dated Oct. 17, 2014, for U.S. Appl. No. 13/868,787, filed Apr. 23, 2013, 8 pages.
Notice of Allowance dated Nov. 5, 2014, for U.S. Appl. No. 11/649,998, filed Jan. 3, 2007, five pages.
Notice of Allowance dated Jan. 23, 2015, for U.S. Appl. No. 13/250,955, filed Sep. 30, 2011, 11 pages.
Notice of Allowance dated Mar. 6, 2015, for U.S. Appl. No. 13/250,955, filed Sep. 30, 2011, 8 pages.
Notice of Allowance dated Sep. 25, 2015, for U.S. Appl. No. 14/666,146, filed Mar. 23, 2015, five pages.
Notice of Allowance dated Feb. 19, 2016, for U.S. Appl. No. 14/570,915, filed Dec. 15, 2014, five pages.
Notice of Allowance dated Jul. 25, 2016, for U.S. Appl. No. 13/351,096, filed Jan. 16, 2012, seven pages.
Notice of Allowance dated Dec. 30, 2016, for U.S. Appl. No. 14/619,958, filed Feb. 11, 2015, eleven pages.
Notice of Allowance dated Jul. 18, 2017, for U.S. Appl. No. 15/179,909, filed Jun. 10, 2016, nine pages.
Notice of Allowance dated Oct. 10, 2017, for U.S. Appl. No. 14/711,626, filed May 13, 2015, eight pages.
Notice of Allowance (Corrected) dated Oct. 30, 2017, for U.S. Appl. No. 15/179,909, filed Jun. 10, 2016, two pages.
Office Action for Chinese Patent Application No. 200580027691.3, dated Jun. 20, 2008, 4 pages.
Office Action for Chinese Patent Application No. 200580027691.3, dated Mar. 27, 2009, 4 pages.
Office Action for Chinese Patent Application No. 200580027691.3, dated Sep. 4, 2009, 4 pages.
Office Action for Japanese Patent Application No. 2007-529978, dated Jul. 27, 2010, 2 pages.
Office Action for Japanese Patent Application No. 2007-529978, dated Apr. 5, 2011, 2 pages.
Office Action for Japanese Patent Application No. 2007-529978, dated Nov. 1, 2011, 9 pages.
Oral Proceedings for EP Patent Application No. 05788888.5-2224, mailed Nov. 16, 2009, 11 pages.
Oral Proceedings Summons for EP Patent Application No. 05788888.5-2224, mailed Mar. 18, 2009, 11 pages.
Partial European Search Report dated Sep. 18, 2009, for EP Application No. 08022346.4, filed Dec. 23, 2008, six pages.
PCT International Preliminary Report and Written Opinion for PCT International Appl. No. PCT/US2005/029467, dated Mar. 8, 2007, 7 pages.
PCT International Search Report and Written Opinion for PCT International Appl. No. US2005/029467, dated Apr. 10, 2006, 15 pages.
PCT Invitation to Pay Additional Fees for PCT Appl. No. US2005/029467, dated Dec. 20, 2005, 5 pages.
Rubine, D.H. (Dec. 1991). “The Automatic Recognition of Gesture,” CMU-CS-91-202, Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, 285 pages.
Rubine, D.G. (May 1992). “Combining Gesture and Direct Manipulation,” CHI '92, pp. 659-660.
TouchPad Advanced Features, Synpatics, “Enriching the Interaction Between Humans and Intelligent Devices,” Downloaded Aug. 16, 2004 (2 pages) http://www.synaptics.com/products/touchpad_features.cfm.
Trackpad, Apple Developer Connection (last updated Apr. 19, 2004, printed Aug. 19, 2004) (3 pages) http://developer.apple.com/documentation/Hardware/Developer_notes/Macintosh_CPUs-. . . .
Westerman, W. (Spring 1999). “Hand Tracking, Finger Identification, and Chordic Manipulation on a Multi-Touch Surface,” A Dissertation Submitted to the Faculty of the University of Delaware in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Electrical Engineering, 364 pages.
Non-Final Office Action dated Mar. 1, 2018, for U.S. Appl. No. 15/354,931, filed Nov. 17, 2016, 25 pages.
Non-Final Office Action dated Apr. 19, 2018, for U.S. Appl. No. 15/821,135, filed Nov. 22, 2017, twelve pages.
Non-Final Office Action dated May 9, 2018, for U.S. Appl. No. 15/489,646, filed Apr. 17, 2017, 29 pages.
Advisory Action received for U.S. Appl. No. 12/242,772, dated May 21, 2013, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 11/649,998, dated Dec. 1, 2014, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 14/570,915, dated Mar. 10, 2016, 2 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 12/242,772, dated Oct. 22, 2013, 7 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 13/351,096, dated Feb. 11, 2014, 10 pages.
Final Office Action received for U.S. Appl. No. 15/354,931, dated Nov. 26, 2018, 27 pages.
Final Office Action received for U.S. Appl. No. 15/489,646, dated Jan. 11, 2019, 15 pages.
Final Office Action received for U.S. Appl. No. 15/821,135, dated Jan. 17, 2019, 9 pages.
Final Office Action received for U.S. Appl. No. 15/880,362, dated Nov. 19, 2019, 17 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2008/087041, completed on Aug. 26, 2010, 8 pages.
Kahney, L., “Pocket PCs Masquerade as IPods”, Available online at: <http://www.wired.com/gadgets/mac/news/2004/03/62543>, Mar. 8, 2004, 2 pages.
Non-Final Office Action received for U.S. Appl. No. 13/351,096, dated Feb. 29, 2012, 28 pages.
Non-Final Office Action received for U.S. Appl. No. 15/821,135, dated Jul. 8, 2019, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 15/880,362, dated Jul. 31, 2019, 17 pages.
Notice of Allowance received for U.S. Appl. No. 13/351,096, dated Jul. 25, 2016, 7 pages.
Notice of Allowance received for U.S. Appl. No. 15/489,646, dated Jun. 17, 2019, 10 pages.
Office Action received for European Patent Application No. 15164429.1, dated Apr. 17, 2019, 3 pages.
Office Action received for European Patent Application No. 15164429.1, dated Dec. 22, 2015, 5 pages.
Office Acton received for European Patent Application No. 15164429.1, dated Mar. 7, 2018, 5 pages.
Patent Board Decision received for U.S. Appl. No. 12/242,772, dated Jan. 29, 2016, 7 pages.
Patent Board Decision received for U.S. Appl. No. 13/351,096, dated May 9, 2016, 7 pages.
The Gadgeteer, “Apple iPod (30GB)”, Available online at: <http://thegadgeteer.com/review/apple_ipod_30gb_review>, Jun. 6, 2003, 19 pages.
Written Opinion received for PCT Patent Application No. PCT/US2008/087041, dated Dec. 30, 2009, 9 pages.
Applicant Initiated Interview Summary received for U.S. Appl. No. 12/479,741, dated Dec. 17, 2012, 3 pages.
Applicant Initiated Interview Summary received for U.S. Appl. No. 14/619,958, dated Oct. 31, 2016, 4 pages.
Applicant Initiated Interview Summary received for U.S. Appl. No. 15/489,646, dated Aug. 29, 2018, 4 pages.
Notice of Allowance received for U.S. Appl. No. 15/880,362, dated Apr. 14, 2020, 13 pages.
Restriction Requirement received for U.S. Appl. No. 12/172,998, dated Jan. 17, 2012, 6 pages.
Restriction Requirement received for U.S. Appl. No. 12/242,794, dated Dec. 23, 2011, 6 pages.
Restriction Requirement received for U.S. Appl. No. 12/242,794, dated Oct. 14, 2011, 6 pages.
Restriction Requirement received for U.S. Appl. No. 12/479,741, dated Dec. 16, 2009, 5 pages.
Related Publications (1)
Number Date Country
20180067571 A1 Mar 2018 US
Continuations (4)
Number Date Country
Parent 15354931 Nov 2016 US
Child 15805954 US
Parent 13351096 Jan 2012 US
Child 15354931 US
Parent 11731118 Mar 2007 US
Child 13351096 US
Parent 10927575 Aug 2004 US
Child 11731118 US