Patent Application
20160379776
Embodiments described herein generally relate to a keyboard for an electronic device.
End users have more electronic device choices than ever before. A number of prominent technological trends are currently afoot (e.g., more computing devices, thinner lighter devices, etc.), and these trends are changing the electronic device landscape. One of the technological trends is a growing demand for extremely light and thin keyboards to reduce the bulk and weight of electronic devices. Virtual keyboards (or typing on glass) are often ergonomically uncomfortable and typically do not provide an enjoyable user experience. Keyboards for convertible laptops and peripheral keyboards are often thick and cumbersome for carrying from place to place. As conventional key heights are lowered to provide thinner keyboards, the key travel becomes an issue and thin keyboards often fail to offer an acceptable user experience. Currently, keyboard designs often stifle the user's flexibility, along with hindering the overall consumer experience of the associated electronic device. Hence, there is a challenge in providing a thin lightweight keyboard that can provide a traditional keyboard typing experience.
Embodiments are illustrated by way of example and not by way of limitation in the FIGURES of the accompanying drawings, in which like references indicate similar elements and in which:
The FIGURES of the drawings are not necessarily drawn to scale, as their dimensions can be varied considerably without departing from the scope of the present disclosure.
The following detailed description sets forth example embodiments of apparatuses, methods, and systems relating to detachable unit configurations for an electronic device. Features such as structure(s), function(s), and/or characteristic(s), for example, are described with reference to one embodiment as a matter of convenience; various embodiments may be implemented with any suitable one or more of the described features.
Turning to
Turning to
In general terms, electronic device 100 can include a means for receiving a signal from a key indicating that the key has been activated and a means for sending a lateral haptic feedback to the key in response to the received signal. The system may also include a means for generating acoustic feedback in response to the received signal and a means for generating visual feedback in response to the received signal. In an example, the haptic, acoustic, and visual feedback can be adjusted using a user interface. In another example, the keys can be configured as a shallow depression in a surface of electronic device 100.
For purposes of illustrating certain example features of electronic devices 100, the following foundational information may be viewed as a basis from which the present disclosure may be properly explained. The push to reduce thickness in clamshell notebooks requires individually addressing chassis wall thicknesses, the thickness of display panels, battery, motherboard component height, and I/O. One of the least negotiable components is the keyboard whose, “z” dimensions are driven by optimal key travel and associated mechanical parts, typically resulting in a keyboard thickness of around 3.5 mm. There is a growing demand for extremely light and thin keyboards to reduce the bulk and weight of delivering a good touch typing experience. However, traditionally, thin keyboard configurations fail to offer an acceptable user experience. Virtual keyboards that require typing on glass (or some other material) are often ergonomically uncomfortable. Furthermore, peripheral keyboards (e.g., Bluetooth keyboards) are often thick and cumbersome for carrying from place to place. Currently, keyboard designs often stifle a user's flexibility, along with hindering the overall consumer experience of the associated electronic device. In addition, current thin keyboard configurations typically do not have individual key haptic effects for a physical keyboard. One current solution is to use a scissor mechanism along with a collapsible rubber dome. The key drawback of this approach is z-height limitations of the collapsible rubber dome which cannot allow for zero (or very low) key travel.
An electronic device that includes a keyboard design with haptic effects, as outlined in
In operation, the spacing between keys 112 can enable a touch-typer to distinguish between the keys using their fingers. Edge keys can be specially designed for thinner sides. An edge key configuration allows keys to hang over the edge of the keyboard to accommodate the thinner sides of the keyboard portion. Second housing 104 can include any suitable dimensions, sizes, and shapes: all of which are encompassed by the present disclosure.
Note that any number of connectors (e.g., Universal Serial Bus (USB) connectors (e.g., in compliance with the USB 3.0 Specification), Thunderbolt™ connectors, WiFi connectors, a non-standard connection point such as a docking connector, etc.) and a plurality of antennas can be provisioned in conjunction with electronic device 100. [Thunderbolt™ and the Thunderbolt logo are trademarks of Intel Corporation in the U.S. and/or other countries.] The antennas are reflective of electrical components that can convert electric currents into radio waves. In particular examples, the antennas can be associated with WiFi activities, wireless connections more generally, small cell deployments, Bluetooth, 802.11, etc.
In regards to the internal structure associated with electronic device 100, each of first housing 102 and second housing 104 can include memory elements for storing information to be used in the operations outlined herein. Each of first housing 102 and second housing 104 may keep information in any suitable memory element (e.g., random access memory (RAM), read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), application specific integrated circuit (ASIC), etc.), software, hardware, firmware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’ Moreover, the information being used, tracked, sent, or received in electronic device 100 could be provided in any database, register, queue, table, cache, control list, or other storage structure, all of which can be referenced at any suitable timeframe. Any such storage options may also be included within the broad term ‘memory element’ as used herein.
In certain example implementations, the functions outlined herein may be implemented by logic encoded in one or more tangible media (e.g., embedded logic provided in an ASIC, digital signal processor (DSP) instructions, software (potentially inclusive of object code and source code) to be executed by a processor, or other similar machine, etc.), which may be inclusive of non-transitory computer-readable media. In some of these instances, memory elements can store data used for the operations described herein. This includes the memory elements being able to store software, logic, code, or processor instructions that are executed to carry out the activities described herein.
In an example implementation, first housing 102 and second housing 104 may include software modules to achieve, or to foster, operations as outlined herein. These modules may be suitably combined in any appropriate manner, which may be based on particular configuration and/or provisioning needs. In example embodiments, such operations may be carried out by hardware, implemented externally to these elements, or included in some other network device to achieve the intended functionality. Furthermore, the modules can be implemented as software, hardware, firmware, or any suitable combination thereof. These elements may also include software (or reciprocating software) that can coordinate with other network elements in order to achieve the operations, as outlined herein.
Additionally, each of first housing 102 and second housing 104 may include a processor that can execute software or an algorithm to perform activities as discussed herein. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein. In one example, the processors could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array (FPGA), an EPROM, an EEPROM) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof. Any of the potential processing elements, modules, and machines described herein should be construed as being encompassed within the broad term ‘processor.’
Electronic device 100 can be an electronic element and includes, for example, desktop computers, laptop computers, mobile devices, personal digital assistants, smartphones, tablets, or other similar devices. Second housing 104 may be secondary hardware such as a peripheral that is in communication with first housing 102. The term “peripheral” as used herein, is generally defined as any auxiliary device such as a keyboard that connects to and works with an electrical device such as a computer in some way.
Turning to
Turning to
Turning to
Keys 112 and touch sensitive layer 124 can be interconnected and configured to response to haptic impulses from haptic actuator 122. For example, when a specific key 112 is touched by a user, haptic module 126 can sense the user's touch and provide lateral haptic feedback using haptic actuator 122. The lateral haptic feedback can be perceived by the user to simulate mechanical characteristics of a keyboard.
Turning to
When a specific key (e.g., key 112a) is touched by a user, haptic module 126 can sense the user's touch and provide lateral haptic feedback using haptic actuator 122. The lateral haptic feedback can be perceived by the user to simulate mechanical characteristics of a keyboard. In addition, haptic module 126 can send a signal to speaker 134a causing speaker 134a to provide acoustic feedback in response to the touching of the specific key. Also, haptic module 126 can send a signal to an illumination source corresponding to the key that was touched (e.g., illumination source 132a) to provide illuminated feedback in response to the touch of the specific key. The haptic response from haptic actuator 122 can be synced with acoustic and visual (i.e., illumination) feedback to allow for a typing experience that is improved over a touch-screen typing experience.
Turning to
Turning to
Turning to
Turning to
As illustrated in
Processors 970 and 980 may also each include integrated memory controller logic (MC) 972 and 982 to communicate with memory elements 932 and 934. Memory elements 932 and/or 934 may store various data used by processors 970 and 980. In alternative embodiments, memory controller logic 972 and 982 may be discrete logic separate from processors 970 and 980.
Processors 970 and 980 may be any type of processor, and may exchange data via a point-to-point (PtP) interface 950 using point-to-point interface circuits 978 and 988, respectively. Processors 970 and 980 may each exchange data with a control logic 990 via individual point-to-point interfaces 952 and 954 using point-to-point interface circuits 976, 986, 994, and 998. Control logic 990 may also exchange data with a high-performance graphics circuit 938 via a high-performance graphics interface 939, using an interface circuit 992, which could be a PtP interface circuit. In alternative embodiments, any or all of the PtP links illustrated in
Control logic 990 may be in communication with a bus 920 via an interface circuit 996. Bus 920 may have one or more devices that communicate over it, such as a bus bridge 918 and I/O devices 916. Via a bus 910, bus bridge 918 may be in communication with other devices such as a keyboard/mouse 912 (or other input devices such as a touch screen, trackball, etc.), communication devices 926 (such as modems, network interface devices, or other types of communication devices that may communicate through a computer network 960), audio I/O devices 914, and/or a data storage device 928. Data storage device 928 may store code 930, which may be executed by processors 970 and/or 980. In alternative embodiments, any portions of the bus architectures could be implemented with one or more PtP links.
The computer system depicted in
Turning to
In this example of
ARM ecosystem SOC 1000 may also include a subscriber identity module (SIM) I/F 1030, a boot read-only memory (ROM) 1035, a synchronous dynamic random access memory (SDRAM) controller 1040, a flash controller 1045, a serial peripheral interface (SPI) master 1050, a suitable power control 1055, a dynamic RAM (DRAM) 1060, and flash 1065. In addition, one or more embodiments include one or more communication capabilities, interfaces, and features such as instances of Bluetooth™ 1070, a 3G modem 1075, a global positioning system (GPS) 1080, and an 802.11 Wi-Fi 1085.
In operation, the example of
Processor core 1100 can also include execution logic 1114 having a set of execution units 1116-1 through 1116-N. Some embodiments may include a number of execution units dedicated to specific functions or sets of functions. Other embodiments may include only one execution unit or one execution unit that can perform a particular function. Execution logic 1114 performs the operations specified by code instructions.
After completion of execution of the operations specified by the code instructions, back-end logic 1118 can retire the instructions of code 1104. In one embodiment, processor core 1100 allows out of order execution but requires in order retirement of instructions. Retirement logic 1120 may take a variety of known forms (e.g., re-order buffers or the like). In this manner, processor core 1100 is transformed during execution of code 1104, at least in terms of the output generated by the decoder, hardware registers and tables utilized by register renaming logic 1110, and any registers (not shown) modified by execution logic 1114.
Although not illustrated in
Note that with the examples provided herein, interaction may be described in terms of two, three, or more network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that electronic device 100 and its teachings are readily scalable and can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of electronic device 100 as potentially applied to a myriad of other architectures.
It is also important to note that the operations in the diagrams illustrate only some of the possible correlating scenarios and patterns that may be executed by, or within, electronic device 100. Some of these operations may be deleted or removed where appropriate, or these operations may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by electronic device 100 in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure.
Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure.
Moreover, certain components may be combined, separated, eliminated, or added based on particular needs and implementations. Additionally, although electronic device 100 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements and operations may be replaced by any suitable architecture, protocols, and/or processes that achieve the intended functionality of electronic device 100. As used herein, the term “and/or” is to include an and or an or condition. For example, A, B, and/or C would include A, B, and C; A and B; A and C; B and C; A, B, or C; A or B; A or C; B or C; and any other variations thereof.
Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.
