Mobile computing devices have been developed to increase the functionality that is made available to users in a mobile setting. For example, a user may interact with a mobile phone, tablet computer, or other mobile computing device to check email, surf the web, compose texts, interact with applications, and so on. Some mobile computing devices may incorporate multiple antennas to support various wireless subsystems and communications. The multiple antennas may include for example one or more Wi-Fi, Bluetooth, global navigation satellite system (GNSS), near field communication (NFC) and/or cellular antennas.
Arranging antennas within a small form factor device, such as a tablet presents a significant challenge. This problem may be compounded as the number of antennas increases. To avoid interference between different antennas, traditional devices may separate antennas by utilizing multiple edges of the device for antenna placements. In order to provide acceptable antenna performance, though, the materials and other features (metal components/cases, connectors, buttons, speakers, etc.) that may be placed along the multiple edges may be limited in this approach, which is a substantial restriction on product design. Moreover, common hand positions used with tablets and other mobile devices may adversely affect antenna performance for antennas placed at or near these hand positions. Thus, traditional placements may be inadequate for some devices and antenna combinations.
Antenna placement techniques are described. In one or more embodiments, a computing device includes an antenna suite having multiple different kinds of antennas. An antenna zone for the antenna suite may be established along a particular edge of the computing device. Non-interfering materials (e.g., RF transparent material) may be used within the antenna zone and other materials (e.g., metal) may be employed for other regions of the device. The multiple different kinds of antennas in the antenna suite may then be disposed within the established antenna zone. The antennas may be placed to minimize interference between antennas and/or achieve performance objective for the suite of antennas. In one approach, a suite of five antennas may be placed along a top edge of a computing device in a landscape orientation.
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.
To avoid interference between different antennas, traditional devices may separate antennas by utilizing multiple edges of the device for antenna placements, which may tie-up these edges with RF keep outs and create substantial restrictions on product design. Accordingly, traditional placements may be inadequate for some devices and antenna combinations.
Antenna placement techniques are described. In one or more embodiments, a computing device includes an antenna suite having multiple different kinds of antennas. An antenna zone for the antenna suite may be established along a particular edge of the computing device. Non-interfering materials (e.g., RF transparent material) may be used within the antenna zone and other materials (e.g., metal) may be employed for other regions of the device. The multiple different kinds of antennas in the antenna suite may then be disposed within the established antenna zone. The antennas may be placed to minimize interference between antennas and/or achieve performance objectives for the suite of antennas. In one approach, a suite of five antennas may be placed along a top edge of a computing device in a landscape orientation.
In the following discussion, an example environment and devices are first described that may employ the techniques described herein. Example implementations and procedures are then described which may occur in the example environment and by the devices as well as in other environments and by other devices. Consequently, the example implementations and procedures are not limited to the example environment/devices and the example environment/devices are not limited to performance of the example implementations and procedures.
Example Operating Environment
The computing device 102, for instance, is illustrated as including an input/output module 108. The input/output module 108 is representative of functionality relating to processing of inputs and rendering outputs of the computing device 102. A variety of different inputs may be processed by the input/output module 108, such as inputs relating to functions that correspond to keys of the input device, keys of a virtual keyboard displayed by the display device 110 to identify gestures and cause operations to be performed that correspond to the gestures that may be recognized through the accessory device 104 and/or touchscreen functionality of the display device 110, and so forth. Thus, the input/output module 108 may support a variety of different input techniques by recognizing and leveraging a division between types of inputs including key presses, gestures, and so on.
In the illustrated example, the accessory device 104 is a device configured as a keyboard having a QWERTY arrangement of keys although other arrangements of keys are also contemplated. Further, other non-conventional configurations for an accessory device 104 are also contemplated, such as a game controller, configuration to mimic a musical instrument, a power adapter, an accessory to provide wireless functionality, and so forth. Thus, the accessory device 104 may assume a variety of different configurations to support a variety of different functionality. Different accessory devices may be connected to the computing device at different times.
As previously described, the accessory device 104 is physically and communicatively coupled to the computing device 102 in this example through use of a flexible hinge 106. The flexible hinge 106 represents one illustrative example of an interface that is suitable to connect and/or attach and accessory device to a host computing device 102. The flexible hinge 106 is flexible in that rotational movement supported by the hinge is achieved through flexing (e.g., bending) of the material forming the hinge as opposed to mechanical rotation as supported by a pin, although that embodiment is also contemplated. Further, this flexible rotation may be configured to support movement in one direction (e.g., vertically in the figure) yet restrict movement in other directions, such as lateral movement of the accessory device 104 in relation to the computing device 102. This may be used to support consistent alignment of the accessory device 104 in relation to the computing device 102, such as to align sensors used to change power states, application states, and so on.
The flexible hinge 106, for instance, may be formed using one or more layers of fabric and include conductors formed as flexible traces to communicatively couple the accessory device 104 to the computing device 102 and vice versa. This communication, for instance, may be used to communicate a result of a key press to the computing device 102, receive power from the computing device, perform authentication, provide supplemental power to the computing device 102, and so on. The flexible hinge 106 or other interface may be configured in a variety of ways to support multiple different accessory devices 104, further discussion of which may be found in relation to the following figure.
As further illustrated in
The computing device 102 further includes an antenna suite 114 that is representative of various antennas employed by the computing device to implement wireless functionality, subsystems, and communications. In accordance with techniques described herein, the antenna suite 114 may include multiple different kinds of antennas (e.g., radios) that are arranged together within one or more antennas zones established for the computing device. In general, the antenna suite 114 may be placed to minimize interference between antennas and/or achieve performance objectives for the suite of antennas as a whole. The placement of the antenna suite 114 may also minimize areas of the computing device 102 and/or accessory device 104 which have restrictions that limit the materials and componentry that may be placed with or near to the antenna suite 114. Areas with such restrictions may be referred to as radio frequency (RF) keep outs. A variety of different types of antennas, combinations of different types of antennas, and arrangements of antennas are contemplated as discussed in greater detail in relation to the following figures.
To further illustrate, consider
The computing device 102 may also implement selected device functionality through one or more microcontrollers 206. The microcontrollers 206 represent hardware devices/systems that are designed to perform a predefined set of designated tasks. The microcontrollers 206 may represent respective on-chip systems/circuits having self-contained resources such as processing components, I/O devices/peripherals, various types of memory (ROM, RAM, Flash, EEPROM), programmable logic, and so forth. Different microcontrollers may be configured to provide different embedded applications/functionality that are implemented at least partially in hardware and perform corresponding tasks. The microcontrollers 206 enable performance of some tasks outside of operation of a general purpose processing system and other applications/components of the computing device or accessory device. Generally, power consumption of the microcontrollers is low in comparison with operating a general purpose processing system for a device.
As further depicted, the computing device 102 may further include an antenna suite 114 as previously discussed. A variety of different types of antennas suitable for the antenna suite 114 are contemplated as represented in
For instance, the Wi-Fi 208 antennas may employ a two-by-two multiple input/multiple output configuration (e.g., 2×2 MIMO). The Wi-Fi 208 antennas may include at least a main and a MIMO antenna in some configurations. In addition, a Bluetooth 216 antenna may optionally be combined with the Wi-Fi 208 antennas. Further, modern cellular technologies such as Long Term Evolution (LTE), WiMax, and/or 4G may employ two or more cellular 212 antennas, such as a main cellular antenna and a MIMO cellular antenna to cover various frequencies, geographic areas, and so forth. 3G and other cellular antennas are also contemplated. The GNSS 210 antennas may be configured for use with various types of navigation standards, technologies, and systems including but not limited to GPS, GLONASS, Galileo, and/or BeiDou navigation systems, to name some examples.
Having discussed an example environment and devices, consider now some example details regarding antenna placement techniques in accordance with various implementations.
Antenna Placement Details
The following discussion presents some details regarding antenna placements and some illustrative examples. As detailed, an antenna suite having multiple different kinds of antennas may be arranged in one or more an antenna zones of the computing device. A variety of design considerations may be accounted for to determine where to place the antenna zones and antennas. Generally, antennas are placed to limit interference between antennas. Thus, antennas that may interfere with one another are isolated to the extent possible. For example, a pair of cellular antennas may be spaced apart to minimize interference. Likewise, a pair of Wi-Fi antennas (e.g., dual 2×2 MIMO antennas) may also be placed in a manner that keeps interference as low as possible given the various other design considerations that are also taken into account.
Further particular performance objectives associated with one or more antennas may be factors used to establish antenna zones and place antennas. Individual and collective performance objectives may be considered in determining where to place the antenna zone(s) and individual antennas. For example, performance priorities may be assigned to different types of antennas and placement may depend at least in part upon these priorities. Thus, for example, if priority is given to LTE/cellular performance then associated cellular 212 antennas may be placed first. On the other hand, if priority is given to Wi-Fi performance then associated Wi-Fi 208 antennas may be placed first. Additionally, performance objectives may dictate particular locations or placements for at least some antennas. By way of example, a GNSS 210 antenna generally is arranged to point skyward so as to obtain information from satellites and provide acceptable performance. Thus, suitable skyward facing real estate of the device may be considered and/or reserved for placement of a GNSS 210 antenna.
Another consideration is RF keep outs that are associated with antenna zones. The RF keep outs generally have non-interfering and/or RF transparent materials (e.g., polymers/plastics). This means that interfering material such as metal may be “kept out” of these areas. Even using interfering material in other areas may affect performance of the antenna suite 114 and therefore placement of interfering material is a factor that may be taken into account for antenna placement. In addition, the antenna placement consumes real estate of the device that may otherwise be used for connectors, interfaces, buttons, speakers, and/or other components. Thus, the amount of area and locations that are taken up by the antennas and that are available for other components may be another factor used to select antenna placements. Hand positions commonly used by users of the device may also be taken into account. In practice, trade-offs between the example considerations enumerated above as well as other considerations may be made to select a suitable arrangement that enables placement of a plurality of antennas and/or provides acceptable performance given the various different design considerations.
Given the foregoing context, consider now some illustrative example antenna placements in various implementations. For example,
The antenna suite 114 may be configured to provide multiple different types of antennas and corresponding communication and/or wireless functionality. For example, the antenna suite 114 may provide cellular functionality and at least one other type of antenna and functionality. Alternatively, an antenna suite 114 may be configured to provide Wi-Fi functionality and at least one other type of antenna and functionality. Comparable combinations including at least two or more different types of antennas are also contemplated. For instance, combinations may include different antennas to provide different types of wireless functionality including various combinations of Wi-Fi, cellular, NFC, Bluetooth, GNSS, and/or other types of antennas as described above and below.
In addition or alternatively, an antenna suite 114 may be configured to provide multiple (e.g., two or more) antennas of the same type alone or in combination with other types of antennas. For instance, an antenna suite 114 of two, three, or more cellular antennas may be implemented for some device designs. Likewise, an arrangement of two, three, or more Wi-Fi antennas may be employed. One example of such an arrangement is a dual two-by-two multiple input/multiple output (e.g., dual 2×2 MIMO) arrangement in which two Wi-Fi 208 antennas may be arranged within the example antenna zone 302 generally along the top edge of the device. In one particular placement, the two Wi-Fi 208 antennas may be spaced apart generally at opposite corners of the antenna zone away from the middle of antenna zone 302. These and other arrangements of multiple, same-type antennas may be implemented with or without including other types of antennas in the same antenna suite 114. Moreover, an antenna suite 114 may extend across one or multiple antenna zones as further discussed in relation to the following figures.
Notably, the suite of five antennas in this arrangement is placed along a single designated edge having the established antenna zone 302. This leaves the remaining edges available for other purposes and generally free of RF keep outs. Additionally, the designer is free to use metal and/or other material away from the top edge and antenna zone 302. Moreover, common hand positions along the short edges of the device are away from the antenna zone 302 and will have little or no impairment upon the antennas in the antenna suite 114.
Antennas provided within antennas zones 604, 602 of an accessory device 104 may be designed as an alternative or a supplement to wireless functionality of the computing device 102. By way of example, an accessory device may be configured to provide supplemental cellular and/or GNSS functionality to a computing device that already provides Wi-Fi and other wireless functionality. As another example, the accessory may be configured to provide NFC functionality to a device that does not have NFC functionality. Alternatively, an antenna suite 114 of an accessory device may be implemented as an accessory to provide wireless functionally to a device that does not already have such wireless functionality. In some implementations, multiple different antenna zones of a device and/or an accessory may be employed in combinations. Any of the example antenna zones 302, 602, 604, 606 described herein may be employed individually or in combinations of multiple zones to implement various arrangements of antenna suites 114 described above and below.
By way of example,
For example, the antenna zone 302 and antenna zone 604 may be configured to have a pair of identical antenna suites 114. Having duplicate antenna suites 114 may enable selective switching between the suites to enhance wireless performance as the computing device 102 and accessory device 104 are manipulated into different orientations relative to one another. For example, the antenna suite 114 in antenna zone 302 may be activated in a first orientation while the antenna suite 114 in antenna zone 604 is deactivated. Then, upon manipulation to a second orientation the antenna suite 114 in antenna zone 604 may become activated and the antenna suite 114 in antenna zone 302 may be deactivated. Comparable techniques may be used to selective switch between operation of different antenna zones that may be configured to have different types of antennas and/or different arrangements of antennas. This type of switching between multiple antenna suites/zones may occur for instance if the accessory device covers and/or in some way blocks or interferes with operation of the antenna zone 302 in the second orientation. Various different orientations are contemplated, examples of which are described in relation to
An angle range 1200 is illustrated, which corresponds to a closed position for the computing device 102. Thus, if the computing device 102 is positioned at an angle within the angle range 1200 relative to the accessory device 104, the computing device 102 can be determined to be in a closed position. A closed position can include an associated closed state where various functionalities/behaviors for the computing device 102 and accessory device 104 including antenna operations can be modified accordingly based on the closed state. This may include switching between different antenna zones, selectively turning antennas on/off, selecting various wireless functionality provided by one or more antenna suites 114, and so forth.
Further illustrated is an angle range 1202, which may correspond to a typing orientation for the computing device 102. Thus, if the computing device 102 is positioned at an angle within the angle range 1002 relative to the accessory device 104, the computing device 102 can be determined to be in a typing orientation. Within this orientation, the computing device 102 and/or the accessory device 104 can be placed in a typing power state where functionalities/behaviors for the computing device 102 and accessory device 104 including antenna operations can be customized accordingly based on the typing state.
Having discussed some example antenna placement details, consider an example procedure in accordance with one or more implementations.
Example Procedures
The following discussion describes antenna placement techniques that may be implemented utilizing the previously described systems and devices. Aspects of each of the procedures may be implemented in hardware, firmware, software, or a combination thereof. The procedures are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks.
Various arrangements of an antenna suite 114 may be placed within the established antenna zone(s) examples of which are described above and below. Antennas within the antenna zone may enable a variety of wireless functionality including but not limited to one or more of Wi-Fi, Cellular, NFC, Bluetooth, and/or GNSS functionality. In an implementation functionality may be provided for at least cellular communications, Wi-Fi communications, and global navigation. In addition or alternatively, functionality may be provided for different combinations of cellular communications, Wi-Fi communications, and global navigation. These combinations may include for example, a combination of cellular communications and at least one other type of wireless functionality, a combination of Wi-Fi communications and at least one other type of wireless functionality, and/or a combination of global navigation and at least one other type of wireless functionality. Other wireless functionality such as NFC and/or Bluetooth may be included in addition to or as alternatives to the enumerated examples.
Having considered the foregoing example procedures, consider now a discussion of example systems and devices that may be employed to implement aspects of techniques in one or more embodiments.
Example System and Device
The example computing device 1402 as illustrated includes a processing system 1404, one or more computer-readable media 1406, and one or more I/O interface 1408 that are communicatively coupled, one to another. Although not shown, the computing device 1402 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 1404 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 1404 is illustrated as including hardware element 1410 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 1410 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 media 1406 is illustrated as including memory/storage 1412. The memory/storage 1412 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage component 1412 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 1412 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 1406 may be configured in a variety of other ways as further described below.
Input/output interface(s) 1408 are representative of functionality to allow a user to enter commands and information to computing device 1402, 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 1402 may be configured in a variety of ways to support user interaction.
The computing device 1402 is further illustrated as being communicatively and physically coupled to an accessory device 1414 that is physically and communicatively removable from the computing device 1402. In this way, a variety of different accessory devices may be coupled to the computing device 1402 having a wide variety of configurations to support a wide variety of functionality. In this example, the accessory device 1414 includes one or more controls 1416, which may be configured as press-sensitive keys, mechanically switched keys, buttons, and so forth.
The accessory device 1414 is further illustrated as including one or more modules 1418 that may be configured to support a variety of functionality. The one or more modules 1418, for instance, may be configured to process analog and/or digital signals received from the controls 1416 to determine whether an input was intended, determine whether an input is indicative of resting pressure, support authentication of the accessory device 1414 for operation with the computing device 1402, and so on.
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 1402. 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 storage of information in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media does not include signal bearing media or signals per se. 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 1402, 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 1410 and computer-readable media 1406 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, microcontroller devices, 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 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 media and/or by one or more hardware elements 1410. The computing device 1402 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 1402 as software may be achieved at least partially in hardware, e.g., through use of computer-readable media and/or hardware elements 1410 of the processing system 1404. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 1402 and/or processing systems 1404) 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.
This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 61/714,713, filed Oct. 16, 2012, and titled “Antenna Placement”, the entire disclosure of which is incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4046975 | Seeger, Jr. | Sep 1977 | A |
4065649 | Carter et al. | Dec 1977 | A |
4243861 | Strandwitz | Jan 1981 | A |
4302648 | Sado et al. | Nov 1981 | A |
4317013 | Larson | Feb 1982 | A |
4365130 | Christensen | Dec 1982 | A |
4492829 | Rodrique | Jan 1985 | A |
4527021 | Morikawa et al. | Jul 1985 | A |
4559426 | Van Zeeland et al. | Dec 1985 | A |
4588187 | Dell | May 1986 | A |
4607147 | Ono et al. | Aug 1986 | A |
4651133 | Ganesan et al. | Mar 1987 | A |
5220521 | Kikinis | Jun 1993 | A |
5283559 | Kalendra et al. | Feb 1994 | A |
5331443 | Stanisci | Jul 1994 | A |
5548477 | Kumar et al. | Aug 1996 | A |
5558577 | Kato | Sep 1996 | A |
5618232 | Martin | Apr 1997 | A |
5681220 | Bertram et al. | Oct 1997 | A |
5745376 | Barker et al. | Apr 1998 | A |
5748114 | Koehn | May 1998 | A |
5781406 | Hunte | Jul 1998 | A |
5807175 | Davis et al. | Sep 1998 | A |
5818361 | Acevedo | Oct 1998 | A |
5828770 | Leis et al. | Oct 1998 | A |
5874697 | Selker et al. | Feb 1999 | A |
5926170 | Oba | Jul 1999 | A |
5971635 | Wise | Oct 1999 | A |
6002389 | Kasser | Dec 1999 | A |
6005209 | Burleson et al. | Dec 1999 | A |
6012714 | Worley et al. | Jan 2000 | A |
6040823 | Seffernick et al. | Mar 2000 | A |
6044717 | Biegelsen et al. | Apr 2000 | A |
6061644 | Leis | May 2000 | A |
6112797 | Colson et al. | Sep 2000 | A |
6178443 | Lin | Jan 2001 | B1 |
6254105 | Rinde et al. | Jul 2001 | B1 |
6279060 | Luke et al. | Aug 2001 | B1 |
6329617 | Burgess | Dec 2001 | B1 |
6344791 | Armstrong | Feb 2002 | B1 |
6380497 | Hashimoto et al. | Apr 2002 | B1 |
6437682 | Vance | Aug 2002 | B1 |
6506983 | Wilson et al. | Jan 2003 | B1 |
6511378 | Bhatt et al. | Jan 2003 | B1 |
6532147 | Christ, Jr. | Mar 2003 | B1 |
6543949 | Ritchey et al. | Apr 2003 | B1 |
6565439 | Shinohara et al. | May 2003 | B2 |
6600121 | Olodort et al. | Jul 2003 | B1 |
6603408 | Gaba | Aug 2003 | B1 |
6617536 | Kawaguchi | Sep 2003 | B2 |
6685369 | Lien | Feb 2004 | B2 |
6704864 | Philyaw | Mar 2004 | B1 |
6721019 | Kono et al. | Apr 2004 | B2 |
6725318 | Sherman et al. | Apr 2004 | B1 |
6774888 | Genduso | Aug 2004 | B1 |
6776546 | Kraus et al. | Aug 2004 | B2 |
6784869 | Clark et al. | Aug 2004 | B1 |
6813143 | Makela | Nov 2004 | B2 |
6819316 | Schulz et al. | Nov 2004 | B2 |
6856506 | Doherty et al. | Feb 2005 | B2 |
6861961 | Sandbach et al. | Mar 2005 | B2 |
6898315 | Guha | May 2005 | B2 |
6914197 | Doherty et al. | Jul 2005 | B2 |
6950950 | Sawyers et al. | Sep 2005 | B2 |
6970957 | Oshins et al. | Nov 2005 | B1 |
6976799 | Kim et al. | Dec 2005 | B2 |
7051149 | Wang et al. | May 2006 | B2 |
7083295 | Hanna | Aug 2006 | B1 |
7091436 | Serban | Aug 2006 | B2 |
7106222 | Ward et al. | Sep 2006 | B2 |
7123292 | Seeger et al. | Oct 2006 | B1 |
7194662 | Do et al. | Mar 2007 | B2 |
7213991 | Chapman et al. | May 2007 | B2 |
7277087 | Hill et al. | Oct 2007 | B2 |
7447934 | Dasari et al. | Nov 2008 | B2 |
7469386 | Bear et al. | Dec 2008 | B2 |
7499037 | Lube | Mar 2009 | B2 |
7502803 | Culter et al. | Mar 2009 | B2 |
7542052 | Solomon et al. | Jun 2009 | B2 |
7558594 | Wilson | Jul 2009 | B2 |
7559834 | York | Jul 2009 | B1 |
7620244 | Collier | Nov 2009 | B1 |
7636921 | Louie | Dec 2009 | B2 |
7639876 | Clary et al. | Dec 2009 | B2 |
7656392 | Bolender | Feb 2010 | B2 |
7733326 | Adiseshan | Jun 2010 | B1 |
7773076 | Pittel et al. | Aug 2010 | B2 |
7777972 | Chen et al. | Aug 2010 | B1 |
7782342 | Koh | Aug 2010 | B2 |
7813715 | McKillop et al. | Oct 2010 | B2 |
7884807 | Hovden et al. | Feb 2011 | B2 |
D636397 | Green | Apr 2011 | S |
7928964 | Kolmykov-Zotov et al. | Apr 2011 | B2 |
7945717 | Rivalsi | May 2011 | B2 |
7973771 | Geaghan | Jul 2011 | B2 |
7978281 | Vergith et al. | Jul 2011 | B2 |
8018386 | Qi et al. | Sep 2011 | B2 |
8026904 | Westerman | Sep 2011 | B2 |
8053688 | Conzola et al. | Nov 2011 | B2 |
8065624 | Morin et al. | Nov 2011 | B2 |
8069356 | Rathi et al. | Nov 2011 | B2 |
8077160 | Land et al. | Dec 2011 | B2 |
8130203 | Westerman | Mar 2012 | B2 |
8154524 | Wilson et al. | Apr 2012 | B2 |
D659139 | Gengler | May 2012 | S |
8169421 | Wright et al. | May 2012 | B2 |
8229509 | Paek et al. | Jul 2012 | B2 |
8229522 | Kim et al. | Jul 2012 | B2 |
20020134828 | Sandbach et al. | Sep 2002 | A1 |
20030197687 | Shetter | Oct 2003 | A1 |
20040258924 | Berger et al. | Dec 2004 | A1 |
20040268000 | Barker et al. | Dec 2004 | A1 |
20050030728 | Kawashima et al. | Feb 2005 | A1 |
20050057515 | Bathiche | Mar 2005 | A1 |
20050059489 | Kim | Mar 2005 | A1 |
20050146512 | Hill et al. | Jul 2005 | A1 |
20050264653 | Starkweather et al. | Dec 2005 | A1 |
20050264988 | Nicolosi | Dec 2005 | A1 |
20050285703 | Wheeler et al. | Dec 2005 | A1 |
20060049993 | Lin et al. | Mar 2006 | A1 |
20060085658 | Allen et al. | Apr 2006 | A1 |
20060125799 | Hillis et al. | Jun 2006 | A1 |
20060154725 | Glaser et al. | Jul 2006 | A1 |
20060156415 | Rubinstein et al. | Jul 2006 | A1 |
20060181514 | Newman | Aug 2006 | A1 |
20060195522 | Miyazaki | Aug 2006 | A1 |
20070062089 | Homer et al. | Mar 2007 | A1 |
20070072474 | Beasley et al. | Mar 2007 | A1 |
20070182663 | Biech | Aug 2007 | A1 |
20070200830 | Yamamoto | Aug 2007 | A1 |
20070234420 | Novotney et al. | Oct 2007 | A1 |
20070236408 | Yamaguchi et al. | Oct 2007 | A1 |
20070247432 | Oakley | Oct 2007 | A1 |
20070260892 | Paul et al. | Nov 2007 | A1 |
20070283179 | Burnett et al. | Dec 2007 | A1 |
20080005423 | Jacobs et al. | Jan 2008 | A1 |
20080104437 | Lee | May 2008 | A1 |
20080151478 | Chern | Jun 2008 | A1 |
20080158185 | Westerman | Jul 2008 | A1 |
20080167832 | Soss | Jul 2008 | A1 |
20080238884 | Harish | Oct 2008 | A1 |
20080253822 | Matias | Oct 2008 | A1 |
20080309636 | Feng et al. | Dec 2008 | A1 |
20080316002 | Brunet et al. | Dec 2008 | A1 |
20080320190 | Lydon et al. | Dec 2008 | A1 |
20090009476 | Daley, III | Jan 2009 | A1 |
20090073060 | Shimasaki et al. | Mar 2009 | A1 |
20090073957 | Newland et al. | Mar 2009 | A1 |
20090079639 | Hotta et al. | Mar 2009 | A1 |
20090127005 | Zachut et al. | May 2009 | A1 |
20090140985 | Liu | Jun 2009 | A1 |
20090163147 | Steigerwald et al. | Jun 2009 | A1 |
20090251008 | Sugaya | Oct 2009 | A1 |
20090262492 | Whitchurch et al. | Oct 2009 | A1 |
20090303137 | Kusaka et al. | Dec 2009 | A1 |
20090303204 | Nasiri et al. | Dec 2009 | A1 |
20090320244 | Lin | Dec 2009 | A1 |
20090321490 | Groene et al. | Dec 2009 | A1 |
20100001963 | Doray et al. | Jan 2010 | A1 |
20100026656 | Hotelling et al. | Feb 2010 | A1 |
20100038821 | Jenkins et al. | Feb 2010 | A1 |
20100045609 | Do et al. | Feb 2010 | A1 |
20100045633 | Gettemy | Feb 2010 | A1 |
20100051356 | Stern et al. | Mar 2010 | A1 |
20100051432 | Lin et al. | Mar 2010 | A1 |
20100053534 | Hsieh et al. | Mar 2010 | A1 |
20100077237 | Sawyers | Mar 2010 | A1 |
20100081377 | Chatterjee et al. | Apr 2010 | A1 |
20100085321 | Pundsack | Apr 2010 | A1 |
20100103112 | Yoo et al. | Apr 2010 | A1 |
20100149111 | Olien | Jun 2010 | A1 |
20100149134 | Westerman et al. | Jun 2010 | A1 |
20100156798 | Archer | Jun 2010 | A1 |
20100161522 | Tirpak et al. | Jun 2010 | A1 |
20100164857 | Liu et al. | Jul 2010 | A1 |
20100171891 | Kaji et al. | Jul 2010 | A1 |
20100174421 | Tsai et al. | Jul 2010 | A1 |
20100180063 | Ananny et al. | Jul 2010 | A1 |
20100188299 | Rinehart et al. | Jul 2010 | A1 |
20100206614 | Park et al. | Aug 2010 | A1 |
20100206644 | Yeh | Aug 2010 | A1 |
20100214257 | Wussler et al. | Aug 2010 | A1 |
20100222110 | Kim et al. | Sep 2010 | A1 |
20100231556 | Mines et al. | Sep 2010 | A1 |
20100238075 | Pourseyed | Sep 2010 | A1 |
20100250988 | Okuda et al. | Sep 2010 | A1 |
20100274932 | Kose | Oct 2010 | A1 |
20100279768 | Huang et al. | Nov 2010 | A1 |
20100289457 | Onnerud et al. | Nov 2010 | A1 |
20100295812 | Burns et al. | Nov 2010 | A1 |
20100302378 | Marks et al. | Dec 2010 | A1 |
20100304793 | Kim | Dec 2010 | A1 |
20100306538 | Thomas et al. | Dec 2010 | A1 |
20100308778 | Yamazaki et al. | Dec 2010 | A1 |
20100308844 | Day et al. | Dec 2010 | A1 |
20100315348 | Jellicoe et al. | Dec 2010 | A1 |
20100325155 | Skinner et al. | Dec 2010 | A1 |
20100331059 | Apgar et al. | Dec 2010 | A1 |
20110012873 | Prest et al. | Jan 2011 | A1 |
20110019123 | Prest et al. | Jan 2011 | A1 |
20110031287 | Le Gette et al. | Feb 2011 | A1 |
20110037721 | Cranfill et al. | Feb 2011 | A1 |
20110043990 | Mickey et al. | Feb 2011 | A1 |
20110060926 | Brooks et al. | Mar 2011 | A1 |
20110069148 | Jones et al. | Mar 2011 | A1 |
20110074688 | Hull et al. | Mar 2011 | A1 |
20110102326 | Casparian et al. | May 2011 | A1 |
20110102356 | Kemppinen et al. | May 2011 | A1 |
20110134032 | Chiu et al. | Jun 2011 | A1 |
20110157087 | Kanehira et al. | Jun 2011 | A1 |
20110163955 | Nasiri et al. | Jul 2011 | A1 |
20110164370 | Mcclure et al. | Jul 2011 | A1 |
20110167181 | Minoo et al. | Jul 2011 | A1 |
20110167287 | Walsh et al. | Jul 2011 | A1 |
20110167391 | Momeyer et al. | Jul 2011 | A1 |
20110167992 | Eventoff et al. | Jul 2011 | A1 |
20110179864 | Raasch et al. | Jul 2011 | A1 |
20110184646 | Wong et al. | Jul 2011 | A1 |
20110193787 | Morishige et al. | Aug 2011 | A1 |
20110205372 | Miramontes | Aug 2011 | A1 |
20110227913 | Hyndman | Sep 2011 | A1 |
20110242138 | Tribble | Oct 2011 | A1 |
20110248920 | Larsen | Oct 2011 | A1 |
20110261001 | Liu | Oct 2011 | A1 |
20110290686 | Huang | Dec 2011 | A1 |
20110297566 | Gallagher et al. | Dec 2011 | A1 |
20110304577 | Brown | Dec 2011 | A1 |
20110316807 | Corrion | Dec 2011 | A1 |
20120007821 | Zaliva | Jan 2012 | A1 |
20120011462 | Westerman et al. | Jan 2012 | A1 |
20120013519 | Hakansson et al. | Jan 2012 | A1 |
20120023459 | Westerman | Jan 2012 | A1 |
20120024682 | Huang et al. | Feb 2012 | A1 |
20120026048 | Vazquez et al. | Feb 2012 | A1 |
20120044179 | Hudson | Feb 2012 | A1 |
20120047368 | Chinn et al. | Feb 2012 | A1 |
20120050975 | Garelli et al. | Mar 2012 | A1 |
20120075249 | Hoch | Mar 2012 | A1 |
20120081316 | Sirpal et al. | Apr 2012 | A1 |
20120092279 | Martin | Apr 2012 | A1 |
20120094257 | Pillischer et al. | Apr 2012 | A1 |
20120099749 | Rubin et al. | Apr 2012 | A1 |
20120115553 | Mahe et al. | May 2012 | A1 |
20120117409 | Lee et al. | May 2012 | A1 |
20120127118 | Nolting et al. | May 2012 | A1 |
20120140396 | Zeliff et al. | Jun 2012 | A1 |
20120145525 | Ishikawa | Jun 2012 | A1 |
20120162693 | Ito | Jun 2012 | A1 |
20120182242 | Lindahl et al. | Jul 2012 | A1 |
20120194393 | Utterman et al. | Aug 2012 | A1 |
20120194448 | Rothkopf | Aug 2012 | A1 |
20120223866 | Ayala et al. | Sep 2012 | A1 |
20120224073 | Miyahara | Sep 2012 | A1 |
20120235635 | Sato | Sep 2012 | A1 |
20120246377 | Bhesania | Sep 2012 | A1 |
20120256959 | Ye et al. | Oct 2012 | A1 |
20120274811 | Bakin | Nov 2012 | A1 |
20120300275 | Vilardell et al. | Nov 2012 | A1 |
20130063873 | Wodrich et al. | Mar 2013 | A1 |
20130227836 | Whitt, III | Sep 2013 | A1 |
20130228435 | Whitt, III | Sep 2013 | A1 |
20130229356 | Marwah | Sep 2013 | A1 |
20130229366 | Dighde | Sep 2013 | A1 |
20130229759 | Whitt, III | Sep 2013 | A1 |
20130335902 | Campbell | Dec 2013 | A1 |
Number | Date | Country |
---|---|---|
2353978 | Aug 2011 | EP |
10326124 | Dec 1998 | JP |
Entry |
---|
Li, et al., “Characteristic Mode Based Tradeoff Analysis of Antenna-Chassis Interactions for Multiple Antenna Terminals,” In IEEE Transactions on Antennas and Propagation, Retrieved from <http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6060882>, (Feb. 2012), 13 pages. |
“Accessing Device Sensors”, retrieved from <https://developer.palm.com/content/api/dev-guide/pdk/accessing-device-sensors.html> on May 25, 2012, 4 pages. |
“ACPI Docking for Windows Operating Systems”, Retrieved from: <http://www.scritube.com/limba/engleza/software/ACPI-Docking-for-Windows-Opera331824193.php> on Jul. 6, 2012, 10 pages. |
“Cholesteric Liquid Crystal”, Retrieved from: <http://en.wikipedia.org/wiki/Cholesteric—liquid—crystal> on Aug. 6, 2012,(Jun. 10, 2012), 2 pages. |
“Cirago Slim Case®—Protective case with built-in kickstand for your iPhone5®”, Retrieved from <http://cirago.com/wordpress/wp-content/uploads/2012/ipc1500brochure1.pdf> on Jan. 29, 2013, (Jan. 2013),1 page. |
“DR2PA”, retrieved from <http://www.architainment.co.uk/wp-content/uploads/2012/08/DR2PA-AU-US-size-Data-Sheet-Rev-H—LOGO.pdf> on Sep. 17, 2012, 4 pages. |
“First One Handed Fabric Keyboard with Bluetooth Wireless Technology”, Retrieved from: <http://press.xtvworld.com/article3817.html> on May 8, 2012,(Jan. 6, 2005), 2 pages. |
“Force and Position Sensing Resistors: An Emerging Technology”, Interlink Electronics, Available at <http://staff.science.uva.nl/˜vlaander/docu/FSR/An—Exploring—Technology.pdf>, (Feb. 1990), pp. 1-6. |
“Frogpad Introduces Weareable Fabric Keyboard with Bluetooth Technology”, Retrieved from: <http://www.geekzone.co.nz/content.asp?contentid=3898> on May 7, 2012,(Jan. 7, 2005), 3 pages. |
“How to Use the iPad's Onscreen Keyboard”, Retrieved from <http://www.dummies.com/how-to/content/how-to-use-the-ipads-onscreen-keyboard.html> on Aug. 28, 2012, 3 pages. |
“i-Interactor electronic pen”, Retrieved from: <http://www.alibaba.com/product-gs/331004878/i—Interactor—electronic—pen.html> on Jun. 19, 2012, 5 pages. |
“Incipio LG G-Slate Premium Kickstand Case—Black Nylon”, Retrieved from: <http://www.amazon.com/Incipio-G-Slate-Premium-Kickstand-Case/dp/B004ZKP916> on May 8, 2012, 4 pages. |
“Membrane Keyboards & Membrane Keypads”, Retrieved from: <http://www.pannam.com/> on May 9, 2012,(Mar. 4, 2009), 2 pages. |
“Motion Sensors”, Android Developers, retrieved from <http://developer.android.com/guide/topics/sensors/sensors—motion.html> on May 25, 2012, 7 pages. |
“MPC Fly Music Production Controller”, AKAI Professional, Retrieved from: <htttp://www.akaiprompc.com/mpc-fly> on Jul. 9, 2012, 4 pages. |
“NI Releases New Maschine & Maschine Mikro”, Retrieved from <http://www.djbooth.net/index/dj-equipment/entry/ni-releases-new-maschine-mikro/> on Sep. 17, 2012 19 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/471,001, (Feb. 19, 2013),15 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/471,139, (Mar. 21, 2013),12 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/471,202, (Feb. 11, 2013),10 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/471,336, (Jan. 18, 2013),14 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,195, (Jan. 2, 2013),14 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,232, (Jan. 17, 2013),15 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,272, (Feb. 12, 2013),10 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,287, (Jan. 29, 2013),13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,304, (Mar. 22, 2013), 9 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,327, (Mar. 22, 2013), 6 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,871, (Mar. 18, 2013),14 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/651,976, (Feb. 22, 2013),16 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/653,321, (Feb. 1, 2013),13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/653,682, (Feb. 7, 2013),11 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/470,633, (Mar. 22, 2013), 7 pages. |
“On-Screen Keyboard for Windows 7, Vista, XP with Touchscreen”, Retrieved from <www.comfort-software.com/on-screen-keyboard.html> on Aug. 28, 2012, (Feb. 2, 2011), 3 pages. |
“Position Sensors”, Android Developers, retrieved from <http://developer.android.com/guide/topics/sensors/sensors—position.html> on May 25, 2012, 5 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/471,139, (Jan. 17, 2013), 7 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/651,304, (Jan. 18, 2013), 7 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/651,726, (Feb. 22, 2013), 6 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/651,871, (Feb. 7, 2013),6 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. |
“SolRxTM E-Series Multidirectional Phototherapy Expandable TM 2-Bulb Full Body Panel System”, Retrieved from: <http://www.solarcsystems.com/us—multidirectional—uv—light—therapy—1—intro.html> on Jul. 25, 2012,(2011), 4 pages. |
“The Microsoft Surface Tablets Comes With Impressive Design and Specs”, Retrieved from <http://microsofttabletreview.com/the-microsoft-surface-tablets-comes-with-impressive-design-and-specs> on Jan. 30, 2013, (Jun. 2012), 2 pages. |
“Tilt Shift Lenses: Perspective Control”, retrieved from http://www.cambridgeincolour.com/tutorials/tilt-shift-lenses1.htm, (Mar. 28, 2008), 11 Pages. |
“Virtualization Getting Started Guide”, Red Hat Enterprise Linux 6, Edition 0.2, retrieved from <http://docs.redhat.com/docs/en-US/Red—Hat—Enterprise—Linux/6/html-single/Virtualization—Getting—Started—Guide/index.html> on Jun. 13, 2012, 24 pages. |
“What is Active Alignment?”, http://www.kasalis.com/active—alignment.html, retrieved on Nov. 22, 2012, 2 Pages. |
Block, Steve et al., “DeviceOrientation Event Specification”, W3C, Editor's Draft, retrieved from <https://developer.palm.com/content/api/dev-guide/pdk/accessing-device-sensors.html> on May 25, 2012,(Jul. 12, 2011), 14 pages. |
Brown, Rich “Microsoft Shows Off Pressure-Sensitive Keyboard”, retrieved from <http://news.cnet.com/8301-17938—105-10304792-1.html> on May 7, 2012, (Aug. 6, 2009), 2 pages. |
Butler, Alex et al., “SideSight: Multi-“touch” Interaction around Small Devices”, In the proceedings of the 21st annual ACM symposium on User interface software and technology., retrieved from <http://research.microsoft.com/pubs/132534/sidesight—crv3.pdf> on May 29, 2012,(Oct. 19, 2008), 4 pages. |
Crider, Michael “Sony Slate Concept Tablet “Grows” a Kickstand”, Retrieved from: <http://androidcommunity.com/sony-slate-concept-tablet-grows-a-kickstand-20120116/> on May 4, 2012,(Jan. 16, 2012), 9 pages. |
Das, Apurba et al., “Study of Heat Transfer through Multilayer Clothing Assemblies: A Theoretical Prediction”, Retrieved from <http://www.autexrj.com/cms/zalaczone—pliki/5—013—11.pdf>, (Jun. 2011), 7 pages. |
Dietz, Paul H., et al., “A Practical Pressure Sensitive Computer Keyboard”, In Proceedings of UIST 2009,(Oct. 2009), 4 pages. |
Glatt, Jeff “Channel and Key Pressure (Aftertouch).”, Retrieved from: <http://home.roadrunner.com/˜jgglatt/tutr/touch.htm> on Jun. 11, 2012, 2 pages. |
Hanlon, Mike “ElekTex Smart Fabric Keyboard Goes Wireless”, Retrieved from: <http://www.gizmag.com/go/5048/> on May 7, 2012,(Jan. 15, 2006), 5 pages. |
Iwase, Eiji “Multistep Sequential Batch Assembly of Three-Dimensional Ferromagnetic Microstructures with Elastic Hinges”, Retrieved at <<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1549861>> Proceedings: Journal of Microelectromechanical Systems, (Dec. 2005), 7 pages. |
Kaur, Sukhmani “Vincent Liew's redesigned laptop satisfies ergonomic needs”, Retrieved from: <http://www.designbuzz.com/entry/vincent-liew-s-redesigned-laptop-satisfies-ergonomic-needs/> on Jul. 27, 2012,(Jun. 21, 2010), 4 pages. |
Khuntontong, Puttachat et al., “Fabrication of Molded Interconnection Devices by Ultrasonic Hot Embossing on Thin Polymer Films”, IEEE Transactions on Electronics Packaging Manufacturing, vol. 32, No. 3,(Jul. 2009), pp. 152-156. |
Linderholm, Owen “Logitech Shows Cloth Keyboard for PDAs”, Retrieved from: <http://www.pcworld.com/article/89084/logitech—shows—cloth—keyboard—for—pdas.html> on May 7, 2012,(Mar. 15, 2002), 5 pages. |
McLellan, Charles “Eleksen Wireless Fabric Keyboard: a first look”, Retrieved from: <http://www.zdnetasia.com/eleksen-wireless-fabric-keyboard-a-first-look-40278954.htm> on May 7, 2012,(Jul. 17, 2006), 9 pages. |
Piltch, Avram “ASUS Eee Pad Slider SL101 Review”, Retrieved from <http://www.laptopmag.com/review/tablets/asus-eee-pad-slider-sl101.aspx>, (Sep. 22, 2011), 5 pages. |
Post, E.R. et al., “E-Broidery: Design and Fabrication of Textile-Based Computing”, IBM Systems Journal, vol. 39, Issue 3 & 4,(Jul. 2000), pp. 840-860. |
Purcher, Jack “Apple is Paving the Way for a New 3D GUI for IOS Devices”, Retrieved from: <http://www.patentlyapple.com/patently-apple/2012/01/apple-is-paving-the-way-for-a-new-3d-gui-for-ios-devices.html> on Jun. 4, 2012,(Jan. 12, 2012),15 pages. |
Qin, Yongqiang 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, Mark “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. |
Takamatsu, Seiichi et al., “Flexible Fabric Keyboard with Conductive Polymer-Coated Fibers”, In Proceedings of Sensors 2011,(Oct. 28, 2011), 4 pages. |
Valliath, G T., “Design of Hologram for Brightness Enhancement in Color LCDs”, Retrieved from <http://www.loreti.it/Download/PDF/LCD/44—05.pdf> on Sep. 17, 2012, 5 pages. |
Williams, Jim “A Fourth Generation of LCD Backlight Technology”, Retrieved from <http://cds.linear.com/docs/Application%20Note/an65f.pdf>, (Nov. 1995), 124 pages. |
Zhang, et al., “Model-Based Developement of Dynamically Adaptive Software”, In Proceedings of ICSE 2006, Available at <http://www.irisa.fr/lande/lande/icse-proceedings/icse/p371.pdf>, (May 20, 2006), pp. 371-380. |
“PCT Search Report and Written Opinion”, Application No. PCT/US2013/028948, Jun. 21, 2013, 11 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/715,229, Aug. 13, 2013, 7 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/715,133, (Oct. 28, 2013), 6 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/715,133, (Dec. 3, 2013), 6 pages. |
Number | Date | Country | |
---|---|---|---|
61714713 | Oct 2012 | US |