Tablet computing devices may include alternative input devices, such as a stylus. Storing of a stylus, however, may create a couple of design challenges. There are two conventional solutions to this problem. In a first example, an internal slot is used to store and retain the stylus through friction or through a push-push type mechanism.
This may create a problem where extra space and parts are required inside the device. This may also cause an increase in the complexity of the device, overall size of the device which may be undesirable for mobile configurations, and may therefore hinder the user's experience with the device.
In another example a lanyard and a pen cap are used. This conventional solution may also create problems. The lanyard, for instance, may operate somewhat as an uncontrolled appendage and therefore get caught on other objects, pen caps tend to let the pen fall out due to limitations of a retention force that may be used, and so on.
Peripheral retention device techniques are described. In one or more implementations, a peripheral retention device includes a computing device securing portion and a peripheral securing portion. The computing device securing portion is configured to removably engage a computing device such that the computing device securing portion is securable to and removable from a first side of a housing the computing device using one or more hands of a user. The peripheral securing portion is connected to the computing device securing portion and configured to removably engage a peripheral device via a second side of the housing that opposes the first side of the housing such that the peripheral device is securable to and removable from the peripheral securing portion using one or more hands of a user.
In one or more implementations, a computing device includes a display device, a housing, and one or more modules. The housing has a form factor configured to be held by one or more hands of a user and includes a kickstand that is movable to support different viewing positions of the display device as secured to the housing. The kickstand is configured to removably engage a peripheral retention device such that the peripheral retention device is securable to and removable from the kickstand using one or more hands of a user, the peripheral device is securable to and removable from the peripheral retention device using the one or more hands of a user. The one or more modules are implemented at least partially in hardware and configured to perform one or more operations responsive to inputs received from the peripheral device.
In one or more implementations, a system includes a stylus and a computing device including a housing having a hand-held configuration. The housing includes a kickstand that is movable to support different viewing positions of a display device as secured to the housing. The kickstand is configured to removably engage a peripheral retention device such that the peripheral retention device is securable to and removable from the kickstand using one or more hands of a user and the stylus is securable to and removable from the peripheral retention device using the one or more hands of a user.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items. Entities represented in the figures may be indicative of one or more entities and thus reference may be made interchangeably to single or plural forms of the entities in the discussion.
Overview
Computing devices may employ a wide range of peripheral devices to support different types of user interaction with the device. This may include input devices that are configured to be used in addition to the computing device, an example of which is a stylus. However, conventional techniques that were utilized to store peripheral devices were often cumbersome and hindered a user's interaction with both the peripheral device and the computing device.
Peripheral retention device techniques are described. In one or more implementations, a peripheral retention device is configured to be secured to a computing device, such as within a cavity of a housing, using a computing device securing portion. The peripheral retention device includes a peripheral securing portion which may be configured as a loop that extends through the housing such that the computing device securing portion and the peripheral securing portion as disposed on opposing sides of the housing. In this way, the peripheral retention device has a sufficient securing force such that a user may grasp a peripheral (e.g., a stylus) and “pick up” the computing device without the computing device being otherwise supported.
Additionally, the loop of the peripheral securing portion may be flexible such that the computing device may still “lay flat” on a surface even when the peripheral retention device is secured to the computing device. The peripheral retention device may be attached to a variety of different locations of a housing of the computing device, such as a kickstand or elsewhere as further described in the following sections.
In the following discussion, an example environment is first described that may employ the techniques described herein. Example mechanisms are also described which may be performed in the example environment as well as other environments. Consequently, use of the example mechanisms is not limited to the example environment and the example environment is not limited to use of the example mechanisms.
Example Environment
The computing device 102 may be configured in a variety of ways. For example, a computing device may be configured as a computer that is capable of communicating over a network, such as a desktop computer, a mobile station, an entertainment appliance, a set-top box communicatively coupled to a display device, a wireless phone, a game console, and so forth. Thus, the computing device 102 may range from full resource devices with substantial memory and processor resources (e.g., personal computers, game consoles) to a low-resource device with limited memory and/or processing resources (e.g., traditional set-top boxes, hand-held game consoles).
The computing device 102 is further illustrated as including an operating system 118. The operating system 118 is configured to abstract underlying functionality of the computing device 102 to applications 120 that are executable on the computing device 102. For example, the operating system 118 may abstract the computing components 104 of the computing device 102 such that the applications 120 may be written without knowing “how” this underlying functionality is implemented. The application 120, for instance, may provide data to the operating system 118 to be rendered and displayed by the display device 114 without understanding how this rendering will be performed, may receive inputs detected using touchscreen functionality of the display device 114, and so on. The operating system 118 may also represent a variety of other functionality, such as to manage a file system and user interface that is navigable by a user of the computing device 102.
The computing device 102 may support a variety of different interactions. For example, the computing device 102 may include one or more hardware devices that are manipulable by a user to interact with the device, which may include peripheral devices such as a keyboard, cursor control device (e.g., mouse), a stylus 122 and so on.
In the illustrated example, first and second hands 124, 126 of a user are shown. The first hand 124 of the user is shown as holding a housing 116 of the computing device 102. The second hand 126 of the user is illustrated as providing one or more inputs using the stylus 122 that are detected using touchscreen functionality of the display device 114 to perform an operation, such as to launch an application. Thus, recognition of the inputs may be leveraged to interact with a user interface output by the computing device 102, such as to interact with a game, an application, browse the internet, change one or more settings of the computing device 102, and so forth. Although a stylus 122 is shown, a variety of other peripheral devices are also contemplated, such as a mouse or other cursor control device, output device, external power supply, and so on.
Peripheral devices such as the illustrated stylus 122 may be lost in some instances by a user because the device is not physically attached to the computing device 102, especially in handheld (i.e., mobile) configurations of the computing device 102. However, conventional techniques that were utilized to secure the stylus to the computing device 102 could consume inordinate amounts of room within a housing 116 (e.g., by internal slot is used to store and retain the stylus through friction or through a push-push type mechanism), interfere with a user's interaction with a device (e.g., a lanyard), and so forth. Accordingly, the peripheral retention device 110 may be configured to secure the stylus 122 or other peripheral device to the housing 116 in a manner that does not interfere with a user's interaction with the computing device 102. An example of one such configuration is described as follows and shown in a corresponding figure.
While the kickstand 202 is illustrated in the closed position 200 as being visible from a side view of the computing device 102, this is not intended to be limiting. For instance, as illustrated in some of the accompanying figures, in some implementations the kickstand 202 is positioned within a cutout portion of the rear surface 204 that includes a border that surrounds the kickstand 202 when the kickstand 202 is in a closed position.
Disposed on a front surface is a display device 114, which is representative of functionality to provide visual output for the computing device 102 as previously described. Disposed on the rear surface 204 is the kickstand 202 that enables various operating positions for the computing device 102, such as relative to an adjacent surface. Generally, the kickstand 202 is formed via a planar portion of material, such as instances and/or combinations of plastic, metal, various alloys, carbon fiber, and so forth.
As further detailed herein, the kickstand 202 is adjustably attached to the rear surface 204 such that the kickstand 202 may be moved to different positions relative to the rear surface 204. In at least some implementations, this enables the kickstand 202 to be closed to support handheld usage of the computing device 102 as shown in
In at least some implementations, the kickstand 202 includes multiple preset open positions that enable different reclining angles, e.g., different angles of the front surface of the display device 114 relative to the surface. The kickstand 202, for instance, is attached to the computing device 102 via a hinge mechanism 206 that enables movement of the kickstand 202 relative to the rear surface 204. The hinge mechanism 206 may thus include a closed position that enables the kickstand 202 to be placed in a closed position 200. The hinge mechanism 206 may further include one or more preset open positions that enable the kickstand 202 to be placed in one or more open positions to support different operating positions of the computing device 102, an example of which is described as follows and shown in a corresponding figure.
The kickstand 202 includes a first side edge 404, a second side edge 406, a bottom edge 408, and a top edge 410. As illustrated, the peripheral portion 402 surrounds the first side edge 404, the second side edge 406, and the bottom edge 408. The top edge 410 represents a region where the kickstand 202 connects to the computing device 102.
In this example, however, a part of the housing 116 (e.g., the kickstand 202 in this instance) has secured thereto a peripheral retention device 110. Further, the peripheral retention device 110 is also illustrated as securing a peripheral, in this instance a stylus 122. Thus, the stylus 122 may be secured to the computing device 102 through use of the peripheral retention device 110.
The peripheral retention device 110 may be configured in a variety of ways. In the illustrated example, the peripheral retention device 110 includes a peripheral securing portion 602 that is configured to secure a peripheral, such as the stylus 122. The peripheral securing portion 602 may also be configured in a variety of ways. In the illustrated example, the peripheral securing portion 602 assumes a complementary shape of the peripheral being secured. This may be performed through use of a flexible material, such as a fabric, rubber, or elastic material. Other examples are also contemplated including examples in which the peripheral securing portion 602 is not flexible, is molded to conform to an outer surface of a peripheral device to be retained, and so on.
The peripheral securing portion 602 may also be configured to provide a biasing force to secure the peripheral. For example, when formed as an elastic loop, the elasticity may bias the peripheral toward the housing 114 (e.g., kickstand) and thereby retain the peripheral against the housing 114. Other examples are also contemplated, such as through use of a spring and so on. Thus, the peripheral retention device 110 may assume a variety of different configurations, an example of which is described as follows and shown in a corresponding figure.
The computing device securing portion 802 is configured to removably engage a computing device 102 as shown in
As shown in the example 900 of
Returning again to
This length 808 of material is then attached to a raised part 810 (e.g., “foot”) of the computing device securing portion 802, thereby forming a layered structure in which the secured part 806 is nested within a recess of the computing device securing portion 802. In this way, an overall thickness of the peripheral retention device 802 may be reduced, thereby limiting interference of the device with normal usage of a user. Further, the raised part 810 supports the loop of the peripheral device portion 602 in a direction perpendicular to the computing device securing portion 802 which provide strong mechanical retention. Further, this may be configured such that only the fabric of the loop of the peripheral device portion 602 is visible to a user as shown and described in relation to
For example, the computing device securing portion 802 may include a raised part 810 that is configured to be secured to the length 808 of the peripheral device portion 702 as previously described. The computing device securing portion 802 also includes a recessed surface 1008 in relation to the raised part 810 that forms the cavity between the computing device securing portion 802 and the peripheral device portion 702 as previously described in relation to
The computing device securing portion 802 also includes indentions 1010, 1012 on opposing sides of the computing device securing portion 802 are configured to engage complementary shapes of the housing 116 of the computing device. This may be utilized to help support the high retention force previously described, further discussion of which may be found in the following as relates to installation and removal of the peripheral retention device 110 to and from the housing 116 of the computing device 102.
To install the peripheral retention device 110, a loop of the peripheral device portion 602 may be pulled 1104 from a first side 1106 of the kickstand 202 through the cavity 1102 to a second side 1108 of the kickstand 202. This causes the peripheral device portion 602 to compress 1110 (e.g., opposing sides of the loop move toward each other as illustrated by the phantom arrows) to fit through the cavity 1102. This motion may continue to position 1112 edges of the computing device securing portion 802 of the peripheral retention device 110 to engage edges of the cavity 1102 in the kickstand 202, further discussion of which may be found in the following and shown in a corresponding figure.
The computing device securing portion 802, for instance, may flex and “click” to bias contact of edges of the portion and the cavity as a result of the force provided by the computing device securing portion 802. This process as described in
As previously described in relation to
For example, a user may grasp the peripheral securing portion 602 and/or a peripheral secured by that portion with one or more hands and pull away from the kickstand. This may result in a force that mimics the force used to pull 1104 the peripheral securing portion through the cavity 1102. However, mechanical engagement of the edges of the indention 1010 to edges of the complementary shape 1204 of the cavity 1102 may be configured to resist this movement, which in the illustrated instance is configured to provide a securing force as generally perpendicular to the pull 1104. Other examples are also contemplated which may be used in addition to or separate from the previous examples, such as to support magnetic attachment, use of an adhesive, and so on.
Thus, as installed in this example the computing device securing portion 802 is not visible via the second side 1108 of the kickstand 202. Further, as previously described the peripheral device portion 602 may be configured to be flexible and thus minimize intrusion of the peripheral retention device 110 on a user's interaction with the computing device 102 when not in use, e.g., when placed on a surface. A variety of other examples of peripheral retention device configurations are also contemplated, discussion of which may be found in the following and shown in the corresponding figures.
Example System and Device
The example computing device 1602 as illustrated includes a processing system 1604, one or more computer-readable media 1606, and one or more I/O interface 1608 that are communicatively coupled, one to another. Although not shown, the computing device 1602 may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.
The processing system 1604 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 1604 is illustrated as including hardware element 1610 that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 1610 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.
The computer-readable storage media 1606 is illustrated as including memory/storage 1612. The memory/storage 1612 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage component 1612 may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage component 1612 may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media 1606 may be configured in a variety of other ways as further described below.
Input/output interface(s) 1608 are representative of functionality to allow a user to enter commands and information to computing device 1602, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non-visible wavelengths such as infrared frequencies to recognize movement as gestures that do not involve touch), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile-response device, and so forth. Thus, the computing device 1602 may be configured in a variety of ways to support user interaction.
The computing device 1602 is further illustrated as being physically coupled to a peripheral device 1614 that is physically removable from the computing device 1602, e.g., using magnetism. In this way, a variety of different input devices may be coupled to the computing device 1602 having a wide variety of configurations to support a wide variety of functionality.
Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms “module,” “functionality,” and “component” as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.
An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device 1602. By way of example, and not limitation, computer-readable media may include “computer-readable storage media” and “computer-readable signal media.”
“Computer-readable storage media” may refer to media and/or devices that enable persistent and/or non-transitory storage of information in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media refers to non-signal bearing media. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.
“Computer-readable signal media” may refer to a signal-bearing medium that is configured to transmit instructions to the hardware of the computing device 1602, such as via a network. Signal media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Signal media also include any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.
As previously described, hardware elements 1610 and computer-readable media 1606 are representative of modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein, such as to perform one or more instructions. Hardware may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware. In this context, hardware may operate as a processing device that performs program tasks defined by instructions and/or logic embodied by the hardware as well as a hardware utilized to store instructions for execution, e.g., the computer-readable storage media described previously.
Combinations of the foregoing may also be employed to implement various techniques described herein. Accordingly, software, hardware, or executable modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements 1610. The computing device 1602 may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of a module that is executable by the computing device 1602 as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements 1610 of the processing system 1604. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 1602 and/or processing systems 1604) to implement techniques, modules, and examples described herein.
Although the example implementations have been described in language specific to structural features and/or methodological acts, it is to be understood that the implementations defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed features.
Number | Name | Date | Kind |
---|---|---|---|
5576981 | Parker et al. | Nov 1996 | A |
5719898 | Davidovici et al. | Feb 1998 | A |
5973677 | Gibbons | Oct 1999 | A |
6266685 | Danielson et al. | Jul 2001 | B1 |
6337924 | Smith | Jan 2002 | B1 |
6338655 | Masse et al. | Jan 2002 | B1 |
6442764 | Badillo et al. | Sep 2002 | B1 |
6468090 | Belopolsky et al. | Oct 2002 | B2 |
6691176 | Narin et al. | Feb 2004 | B1 |
6918066 | Dutta et al. | Jul 2005 | B2 |
7055146 | Durr et al. | May 2006 | B1 |
7151795 | Goldburg | Dec 2006 | B1 |
7437193 | Parramon et al. | Oct 2008 | B2 |
7535874 | Ozluturk et al. | May 2009 | B2 |
7623121 | Dodge | Nov 2009 | B2 |
7626358 | Lam et al. | Dec 2009 | B2 |
7639876 | Clary et al. | Dec 2009 | B2 |
7653893 | Neumann et al. | Jan 2010 | B2 |
7681208 | Pantuso et al. | Mar 2010 | B1 |
7853646 | Black et al. | Dec 2010 | B2 |
7905753 | Siev et al. | Mar 2011 | B2 |
7921430 | Johnson et al. | Apr 2011 | B2 |
7953295 | Vincent et al. | May 2011 | B2 |
8090225 | Lapstun et al. | Jan 2012 | B2 |
8141059 | Ding et al. | Mar 2012 | B2 |
8175613 | Patil et al. | May 2012 | B2 |
8363036 | Liang | Jan 2013 | B2 |
8370629 | Ngo et al. | Feb 2013 | B1 |
8401054 | Myers et al. | Mar 2013 | B2 |
8432939 | Bhattad et al. | Apr 2013 | B2 |
8490084 | Alford et al. | Jul 2013 | B1 |
8509563 | Robinson et al. | Aug 2013 | B2 |
8537851 | Gossett et al. | Sep 2013 | B1 |
8606293 | Kim et al. | Dec 2013 | B2 |
8634386 | Jagger et al. | Jan 2014 | B2 |
8634849 | Jovicic et al. | Jan 2014 | B2 |
8639266 | Zelinka | Jan 2014 | B2 |
8655944 | Silbey et al. | Feb 2014 | B2 |
8700060 | Huang | Apr 2014 | B2 |
8794987 | Classen et al. | Aug 2014 | B2 |
9397723 | Hassan et al. | Jul 2016 | B2 |
9424048 | Jakoboski et al. | Aug 2016 | B2 |
20010009545 | Schilling | Jul 2001 | A1 |
20010033218 | Murata et al. | Oct 2001 | A1 |
20020015437 | Li et al. | Feb 2002 | A1 |
20020036253 | Lake | Mar 2002 | A1 |
20020126445 | Minaguchi et al. | Sep 2002 | A1 |
20020186710 | Alvesalo et al. | Dec 2002 | A1 |
20020187799 | Haartsen | Dec 2002 | A1 |
20030061283 | Dutta et al. | Mar 2003 | A1 |
20030072467 | Brundage et al. | Apr 2003 | A1 |
20030088716 | Sanders | May 2003 | A1 |
20030110296 | Kirsch et al. | Jun 2003 | A1 |
20030126311 | Kushnirskiy et al. | Jul 2003 | A1 |
20030132916 | Kramer | Jul 2003 | A1 |
20030179731 | Noguchi et al. | Sep 2003 | A1 |
20040027387 | Nason et al. | Feb 2004 | A1 |
20040031030 | Kidder et al. | Feb 2004 | A1 |
20040100457 | Mandle | May 2004 | A1 |
20040120290 | Makhijani et al. | Jun 2004 | A1 |
20050094604 | Ozluturk et al. | May 2005 | A1 |
20050157459 | Yin et al. | Jul 2005 | A1 |
20050240949 | Liu et al. | Oct 2005 | A1 |
20050281321 | Bergstrom et al. | Dec 2005 | A1 |
20060012567 | Sicklinger | Jan 2006 | A1 |
20060081714 | King et al. | Apr 2006 | A1 |
20060089171 | Yoo et al. | Apr 2006 | A1 |
20060189353 | Fujishima | Aug 2006 | A1 |
20060197755 | Bawany | Sep 2006 | A1 |
20060238510 | Panotopoulos et al. | Oct 2006 | A1 |
20060270351 | Lastinger et al. | Nov 2006 | A1 |
20070022390 | Hillis et al. | Jan 2007 | A1 |
20070051766 | Spencer | Mar 2007 | A1 |
20070147226 | Khandekar et al. | Jun 2007 | A1 |
20070174846 | Johnson et al. | Jul 2007 | A1 |
20070180441 | Ding et al. | Aug 2007 | A1 |
20070247338 | Marchetto | Oct 2007 | A1 |
20070283048 | Theimer et al. | Dec 2007 | A1 |
20070297323 | Seki | Dec 2007 | A1 |
20080024502 | Nagahara et al. | Jan 2008 | A1 |
20080077855 | Lev et al. | Mar 2008 | A1 |
20080077941 | Holmes et al. | Mar 2008 | A1 |
20080104233 | Smith et al. | May 2008 | A1 |
20080104580 | Wilkinson | May 2008 | A1 |
20080165754 | Hu | Jul 2008 | A1 |
20080180411 | Solomon et al. | Jul 2008 | A1 |
20080215796 | Lam et al. | Sep 2008 | A1 |
20080232061 | Wang et al. | Sep 2008 | A1 |
20080309636 | Feng et al. | Dec 2008 | A1 |
20090007001 | Morin et al. | Jan 2009 | A1 |
20090102794 | Lapstun et al. | Apr 2009 | A1 |
20090187879 | Ao et al. | Jul 2009 | A1 |
20090201850 | Davis et al. | Aug 2009 | A1 |
20090217241 | Motoyama et al. | Aug 2009 | A1 |
20090241020 | Hsiao | Sep 2009 | A1 |
20090250366 | Esfahani | Oct 2009 | A1 |
20100001963 | Doray et al. | Jan 2010 | A1 |
20100021022 | Pittel et al. | Jan 2010 | A1 |
20100055928 | Randall | Mar 2010 | A1 |
20100075517 | Ni et al. | Mar 2010 | A1 |
20100146488 | Chen et al. | Jun 2010 | A1 |
20100188338 | Longe | Jul 2010 | A1 |
20100231556 | Mines et al. | Sep 2010 | A1 |
20100245221 | Khan | Sep 2010 | A1 |
20110066973 | Plom et al. | Mar 2011 | A1 |
20110083126 | Bhakta et al. | Apr 2011 | A1 |
20110093773 | Yee | Apr 2011 | A1 |
20110164813 | Enomoto | Jul 2011 | A1 |
20110183678 | Kerpez et al. | Jul 2011 | A1 |
20110225490 | Meunier | Sep 2011 | A1 |
20110234502 | Yun et al. | Sep 2011 | A1 |
20110248941 | Abdo et al. | Oct 2011 | A1 |
20120071189 | Mody | Mar 2012 | A1 |
20120084345 | Silbey | Apr 2012 | A1 |
20120087078 | Medica et al. | Apr 2012 | A1 |
20120106082 | Wu et al. | May 2012 | A1 |
20120108180 | Shibuya | May 2012 | A1 |
20120170966 | Novak, Jr. | Jul 2012 | A1 |
20120173226 | McEvoy et al. | Jul 2012 | A1 |
20120174224 | Thomas et al. | Jul 2012 | A1 |
20120180002 | Campbell et al. | Jul 2012 | A1 |
20120189203 | Lin et al. | Jul 2012 | A1 |
20120192155 | Silbey et al. | Jul 2012 | A1 |
20120249300 | Avital et al. | Oct 2012 | A1 |
20120263118 | Love | Oct 2012 | A1 |
20120270537 | Weng et al. | Oct 2012 | A1 |
20130050922 | Lee et al. | Feb 2013 | A1 |
20130076617 | Csaszar et al. | Mar 2013 | A1 |
20130093388 | Partovi | Apr 2013 | A1 |
20130106723 | Bakken et al. | May 2013 | A1 |
20130179798 | Korupolu et al. | Jul 2013 | A1 |
20130191715 | Raskovic et al. | Jul 2013 | A1 |
20130229386 | Bathiche | Sep 2013 | A1 |
20130242762 | Bennett et al. | Sep 2013 | A1 |
20130279098 | Cho | Oct 2013 | A1 |
20130288516 | Chang | Oct 2013 | A1 |
20130301200 | Leung | Nov 2013 | A1 |
20130322423 | Park et al. | Dec 2013 | A1 |
20130335330 | Lane | Dec 2013 | A1 |
20130335902 | Campbell | Dec 2013 | A1 |
20130335903 | Raken | Dec 2013 | A1 |
20130342465 | Bathiche | Dec 2013 | A1 |
20130346636 | Bathiche | Dec 2013 | A1 |
20140028635 | Krah | Jan 2014 | A1 |
20140029183 | Ashcraft et al. | Jan 2014 | A1 |
20140036430 | Wroblewski et al. | Feb 2014 | A1 |
20140061406 | Chevalier | Mar 2014 | A1 |
20140080501 | Lee et al. | Mar 2014 | A1 |
20140094165 | Karlsson et al. | Apr 2014 | A1 |
20140098485 | Vahid | Apr 2014 | A1 |
20140104279 | Albrecht | Apr 2014 | A1 |
20140117928 | Liao | May 2014 | A1 |
20140128091 | Engström | May 2014 | A1 |
20140173402 | Bastide et al. | Jun 2014 | A1 |
20140173517 | Chaudhri | Jun 2014 | A1 |
20140187288 | Correll, Jr. | Jul 2014 | A1 |
20140328194 | Sen et al. | Nov 2014 | A1 |
20140341056 | Carbajal | Nov 2014 | A1 |
20150085683 | Sadek et al. | Mar 2015 | A1 |
20150277500 | Turowski et al. | Oct 2015 | A1 |
20150310043 | Adelman | Oct 2015 | A1 |
20160042070 | Rossi et al. | Feb 2016 | A1 |
20160050529 | Hassan et al. | Feb 2016 | A1 |
20160055374 | Zhang et al. | Feb 2016 | A1 |
20160055659 | Wilson et al. | Feb 2016 | A1 |
20160056916 | Hassan et al. | Feb 2016 | A1 |
20160065265 | Hassan et al. | Mar 2016 | A1 |
20160073267 | Hassan et al. | Mar 2016 | A1 |
20160077843 | Jakoboski et al. | Mar 2016 | A1 |
Number | Date | Country |
---|---|---|
687757 | Feb 1997 | CH |
1825278 | Aug 2006 | CN |
101388057 | Mar 2009 | CN |
101650659 | Feb 2010 | CN |
101685487 | Mar 2010 | CN |
101799855 | Aug 2010 | CN |
102855232 | Jan 2013 | CN |
202011103087 | Aug 2011 | DE |
0611498 | Aug 1994 | EP |
2102632 | Feb 1983 | GB |
2178570 | Feb 1987 | GB |
20030000579 | Jan 2003 | KR |
1038411 | May 2012 | NL |
M482205 | Jul 2014 | TW |
WO-0158098 | Aug 2001 | WO |
WO-02069533 | Sep 2002 | WO |
WO-2009139789 | Nov 2009 | WO |
WO 2010011983 | Jan 2010 | WO |
WO-2010048746 | May 2010 | WO |
WO-2012171729 | Dec 2012 | WO |
WO-2013010323 | Jan 2013 | WO |
Entry |
---|
“ABBYY FineReader”, Available at: http://www.softexia.com/office-tools/abbyy-finereader/, Jul. 11, 2013, 10 pages. |
“Chronoscan”, Available at: http://wwvv.chronoscan.org/index.php?lang=en, Jan. 26, 2013, 3 pages. |
“Final Office Action”, U.S. Appl. No. 12/897,947, Dec. 19, 2012, 8 pages. |
“Final Office Action”, U.S. Appl. No. 13/010,552, Sep. 26, 2013, 22 pages. |
“Final Office Action”, U.S. Appl. No. 13/010,552, Oct. 23, 2014, 22 pages. |
“Foreign Office Action”, CN Application No. 201210018531.4, Feb. 28, 2015, 12 pages. |
“Foreign Office Action”, CN Application No. 201210018531.4, Jun. 4, 2014, 16 pages. |
“How and Why Would Anyone Validate Their Code”, Retrieved from: <http://designreviver.com/articles/how-and-why-would-anyone-validate-their-code/> on Nov. 11, 2010, Aug. 25, 2010, 9 pages. |
“HP Code Advisor Version C.02.15 User's Guide”, Hewlett-Packard Development Company L.P., Available at <http://docs.hp.com/en/14242/Cadvise—UG.pdf>, Jan. 2010, pp. 1-72. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/022349, Jun. 25, 2015, 9 Pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2012/021004, Jul. 30, 2012, 9 pages. |
“Introducing OmniPage Cloud Service”, Available at: http://www.nuance.com/for-business/by-product/omnipage/omnipage-cloud-services/index.htm, Sep. 4, 2012, 3 pages. |
“Non-Final Office Action”, U.S. Appl. No. 12/897,947, Jun. 7, 2012, 7 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/010,552, May 8, 2015, 27 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/010,552, Jul. 8, 2014, 22 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/010,552, Aug. 12, 2013, 20 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/468,699, May 15, 2015, 6 pages. |
“Notice of Allowance”, U.S. Appl. No. 12/897,947, Oct. 8, 2013, 8 pages. |
“OmniPage Standard 18”, Available at: http://ocr-software-review.toptenreviews.com/omnipage-standard-review.html, Oct. 27, 2010, 3 pages. |
“Pearl scan solutions”, Available at: http://www.pearl-scan.co.uk/document-conversion/OCR-conversion.php, Aug. 21, 2008, 2 pages. |
“Restriction Requirement”, U.S. Appl. No. 12/897,947, May 11, 2012, 7 pages. |
“ScanSnap ix500 Scanning into Excel”, Retrieved on: Feb. 20, 2014, Available at: http://www.youtube.com/watch?v=PvpH4NAzUjM, 2 pages. |
“Scansnap”, Available at: http://scanners.fcpa.fujitsu.com/scansnapit/scansnap-ix500.php, Jan. 11, 2013, 4 pages. |
“Understanding the Compatibility View List”, Retrieved From: <http://msdn.microsoft.com/en-us/library/dd567845(v=vs.85).aspx> Jun. 11, 2014, Mar. 2011, 5 Pages. |
“Visual Basic 6.0 Code Advisor”, Retrieved from: <http://msdn.microsoft.com/en-us/vbasic/ms789135.aspx> on Nov. 11, 2010, 2006, 2 pages. |
“Web Site Maintenance Tools, Software”, Retrieved from: <http://websitetips.com/tools/> on Nov. 11, 2010, Nov. 11, 2010, 10 pages. |
Bohge,“The Use of Guard Bands to Mitigate Multiple Access Interference in the OFDMA Uplink”, In Proceedings of 13th International OFDM-Workshop, Aug. 2008, 5 Pages. |
Chapman,“Review of Cross-Browser Testing Tools”, Retrieved From: <http://www.smashingmagazine.com/2011/08/07/a-dozen-cross-browser-testing-tools/> Jun. 9, 2014, Aug. 7, 2011, 13 pages. |
Choudhary,“Crosscheck: Combining Crawling and Differencing to Better Detect Cross-browser Incompatibilities in Web Applications”, In Proceedings: IEEE Fifth International Conference on Software Testing, Verification and Validation, Apr. 17, 2012, 10 Pages. |
Choudhary,“Detecting Cross-browser Issues in Web Applications”, In Proceedings: The 33rd International Conference on Software Engineering, May 21, 2011, 3 Pages. |
Kang,“An Opportunistic Indoors Positioning Scheme Based on Estimated Positions”, In Proceedings: IEEE Symposium on Computers and Communications, Jul. 5, 2009, 7 Pages. |
Kim,“Chrome Extensions for Web Development”, Retrieved from: <http://googlecode.blogspot.com/2010/05/chrome-extensions-for-web-development.html> on Nov. 11, 2010, May 27, 2010, 4 pages. |
Kristianto,“Cross Browser Compatibility Check Tools”, Retrieved from: <http://wwvv.ivankristianto.com/web-development/designs/cross-browser-compatibility-check-tools/1202/> on Nov. 11, 2010, Jan. 26, 2010, 14 pages. |
Mesbah,“Automated Cross-Browser Compatibility Testing”, In Proceedings: the 33rd International Conference on Software Engineering, May 21, 2011, 10 Pages. |
Ross,“IE9 Compat Inspector”, Retrieved From: <http://blogs.msdn.com/b/ie/archive/2011/04/27/ie9-compat-inspector.aspx> Jun. 11, 2014, Apr. 27, 2011, 7 Pages. |
Yucek, “A Survey of Spectrum Sensing Algorithms for Cognitive Radio Applications”, In Proceedings: IEEE Communications Surveys & Tutorials, vol. 11 No. 1, Jan. 1, 2009, 15 pages. |
“Cholesteric Liquid Crystal”, Retrieved from: <http://en.wikipedia.org/wiki/Cholesteric—liquid—crystal> on Aug. 6, 2012, Jun. 10, 2012, 2 pages. |
“Final Office Action”, U.S. Appl. No. 13/603,918, Mar. 21, 2014, 14 pages. |
“i-Interactor electronic pen”, Retrieved from: <http://www.alibaba.com/product-gs/331004878/i—Interactor—electronic—pen.html> on Jun. 19, 2012, 2012, 5 pages. |
“International Search Report and Written Opinion”, U.S. Appl. No. PCT/US2013/044871, Aug. 14, 2013, 12 pages. |
“International Search Report and Written Opinion”, U.S. Appl. No. PCT/US2013/044873, Nov. 22, 2013, 9 pages. |
“International Search Report and Written Opinion”, U.S. Appl. No. PCT/US2013/045049, Sep. 16, 2013, 9 pages. |
“MPC Fly Music Production Controller”, AKAI Professional, Retrieved from: <http://www.akaiprompc.com/mpc-fly> on Jul. 9, 2012, 4 pages. |
“neXus Charging Cradle”, Retrieved from <http://www.gen-xtech.com/neXus.php> on Jul. 28, 2014, Apr. 17, 2012, 2 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/603,918, Dec. 19, 2013, 12 pages. |
“Rechargeable Stylus Pen”, Retrieved from <http://www.e-pens.com/uk/rechargeable-stylus-pen.html> on Jul. 28, 2014, Jul. 5, 2013, 1 pages. |
“Reflex LCD Writing Tablets”, retrieved from <http://www.kentdisplays.com/products/lcdwritingtablets.html> on Jun. 27, 2012, 3 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/603,918, filed Nov. 27, 2013, 8 pages. |
“Smart Board™ Interactive Display Frame Pencil Pack”, Available at <http://downloads01.smarttech.com/media/sitecore/en/support/product/sbfpd/400series(interactivedisplayframes)/guides/smartboardinteractivedisplayframepencilpackv12mar09.pdf>, 2009, 2 pages. |
“Write & Learn Spellboard Advanced”, Available at <http://somemanuals.com/Vtech,Write%2526Learn--Spellboard--Adv--71000,Jidfhe.pdf>, 2006, 22 pages. |
Bathiche, et al., “Input Device with Interchangeable Surface”, U.S. Appl. No. 13/974,749, Aug. 23, 2013, 51 pages. |
Lane, et al., “Media Processing Input Device”, U.S. Appl. No. 13/655,065, Oct. 18, 2012, 43 pages. |
Qin, et al., “pPen: Enabling Authenticated Pen and Touch Interaction on Tabletop Surfaces”, In Proceedings of ITS 2010, Available at <http://www.dfki.de/its2010/papers/pdf/po172.pdf>,Nov. 2010, pp. 283-284. |
Sumimoto, “Touch & Write: Surface Computing With Touch and Pen Input”, Retrieved from: <http://www.gottabemobile.com/2009/08/07/touch-write-surface-computing-with-touch-and-pen-input/> on Jun. 19, 2012, Aug. 7, 2009, 4 pages. |
Van “Lenovo Thinkpad Tablet 2 Review”, Retrieved from: <http://www.digitaltrends.com/tablet-reviews/lenovo-thinkpad-tablet-2-review/> Jan. 29, 2014, Feb. 12, 2013, 7 Pages. |
“Final Office Action”, U.S. Appl. No. 13/010,552, Oct. 9, 2015, 30 pages. |
“FOLDOC: Free On-Line Dictionary of Computing, definition for “Exception””, Retrieved from the Internet: http://web.archive.org/web/20100615211114/http://foldoc.org/exception, 1 page. |
“Foreign Office Action”, CN Application No. 201210018531.4, Sep. 6, 2015, 13 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/045985, Oct. 30, 2015, 10 Pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/044402, Nov. 9, 2015, 10 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/045780, Oct. 22, 2015, 11 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/042551, Oct. 6, 2015, 13 Pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/044944, Nov. 11, 2015, 13 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/045468, Oct. 29, 2015, 9 Pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/229,507, Nov. 10, 2015, 11 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/468,699, Oct. 16, 2015, 8 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/477,014, Sep. 29, 2015, 18 pages. |
Gao, “View: Visual Information Extraction Widget for Improving Chart Images Accessibility”, Sep. 30, 2012, 4 pages. |
Mishchenko, “Chart image understanding and numerical data extraction”, Sixth International Conference on Digital Information Management (ICDIM), Sep. 26, 2011, 20 pages. |
Savva, “ReVision: Automated Classification, Analysis and Redesign of Chart Images”, Oct. 16, 2011, 10 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/048218, Dec. 2, 2015, 11 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/045778, Dec. 15, 2015, 15 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/462,820, Dec. 21, 2015, 33 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/465,307, Jan. 29, 2016, 8 pages. |
Embley,“Table-Processing Paradigms: A Research Survey”, International Journal of Document Analysis and Recognition, vol. 8, No. 2-3, May 9, 2006, pp. 66-86. |
Sadek,“Method and Apparatus for Performing Carrier Sense Adaptive Transmission in Unlicensed Spectrum”, U.S. Appl. No. 61/981,608, filed Apr. 18, 2014, 41 pages. |
“Final Office Action”, U.S. Appl. No. 14/229,507, Apr. 26, 2016, 15 pages. |
“Foreign Notice of Allowance”, CN Application No. 201210018531.4, Feb. 4, 2016, 7 pages. |
“International Search Report and Written Opinion”, Application No. PCT/US2015/049270, Feb. 23, 2016, 14 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/468,699, Mar. 11, 2016, 8 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/486,381, Apr. 13, 2016, 7 pages. |
“Restriction Requirement”, U.S. Appl. No. 14/486,381, Mar. 7, 2016, 6 pages. |
“Second Written Opinion”, Application No. PCT/US2015/044402, Apr. 6, 2016, 4 pages. |
“Corrected Notice of Allowance”, U.S. Appl. No. 14/486,381, Jul. 20, 2016, 4 pages. |
“Corrected Notice of Allowance”, U.S. Appl. No. 14/486,381, May 24, 2016, 6 pages. |
“Final Office Action”, U.S. Appl. No. 14/462,280, May 20, 2016, 34 pages. |
“Final Office Action”, U.S. Appl. No. 14/477,014, Jun. 8, 2016, 20 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/049270, Jul. 6, 2016, 5 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/044402, Jul. 8, 2016, 7 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2015/044944, Jul. 21, 2016, 8 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/229,507, Jul. 29, 2016, 24 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/465,307, Jun. 6, 2016, 7 pages. |
“Second Written Opinion”, Application No. PCT/US2015/045985, Aug. 1, 2016, 7 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/468,699, May 9, 2016, 4 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/468,699, Jun. 20, 2016, 4 pages. |
Non-Final Office Action, U.S. Appl. No. 14/456,561, Sep. 26, 2016, 22 pages. |
Non-Final Office Action, U.S. Appl. No. 14/462,820, Aug. 25, 2016, 27 pages. |
Notice of Allowance, U.S. Appl. No. 14/465,307, Aug. 12, 2016, 8 pages. |
Second Written Opinion, Application No. PCT/US2015/045780, Jul. 12, 2016, 4 pages. |
Second Written Opinion, Application No. PCT/US2015/048218, Aug. 9, 2016, 6 pages. |
Number | Date | Country | |
---|---|---|---|
20160034001 A1 | Feb 2016 | US |