Patent Application
20200033995
Humans interact with devices in various ways. Keyboards, mice, and trackpads, for example, have been used for years to facilitate user interaction with computers and are still relevant input mechanisms for providing accurate input control with excellent tactile feedback. One downside of these input mechanisms, however, is limited customizability. Apart from adding additional keys and allowing for custom key bindings, keyboards are still restrained by the requirement to function correctly across a wide range of applications. Touchscreens, on the other hand, allow near limitless customizability since touchscreens can be customized through software to display any soft button or other graphical user interface (“GUI”) element, and do not rely on hardware keys and buttons to be mapped to particular functions of a given application. For these reasons, touchscreens have come to dominate user input for many devices, including smartphones, tablets, and even personal computers. Existing touchscreen interfaces, however, are relatively small, have a fixed size, and typically cannot be shared by multiple concurrent users. As such, each touchscreen user must have his/her own interface which limits collaboration and isolates each user to some extent. Moreover, all interactions are scaled to fit on the same-sized interface which can make some interactions convoluted.
Concepts and technologies are disclosed herein for a surface interface. According to one aspect of the concepts and technologies disclosed herein, a system can include a plurality of surface transducers, a user transducer, and a user device. The plurality of surface transducers are in contact with a surface that is to be used as an input interface for a user. The user transducer is in contact with the user. The user device can include a processor and memory. The memory can store instructions that, when executed by the processor, cause the processor to perform operations. In particular, the processor can analyze a received portion of a signal to determine a relative location of a part of a body of the user on the surface, and can perform a function responsive to the relative location of the part of the body of the user on the surface.
In some embodiments, the signal includes a user-originated signal that is sent by the user transducer through the body of the user towards the surface. The received portion can be received from a surface transducer of the plurality of surface transducers. In some embodiments, the processor can analyze a second received portion of the signal to determine the relative location of the part of the body of the user on the surface. The second received portion of the signal can be received from a second surface transducer of the plurality of surface transducers.
In some embodiments, the signal includes a surface-originated signal that is sent by a surface transducer of the plurality of surface transducers towards the body of the user. The received portion, in these embodiments, includes a portion of the surface-originated signal that is received by the user transducer. Additional portions of the surface-originated signal can be received from other surface transducers of the plurality of surface transducers.
According to another aspect of the concepts and technologies disclosed herein, a user transducer can send a signal towards a surface that is to be used as an input interface for a user device associated with a user. The surface can include a plurality of surface transducers in contact therewith. Each surface transducer of the plurality of surface transducers can communicate a received portion of the signal to the user device. The user device can analyze the received portion of the signal from each surface transducer of the plurality of surface transducers to determine a relative location of contact on the surface. The user device can perform a function responsive to the relative location of contact on the surface.
In some embodiments, the user transducer is in contact with the user. The signal, in these embodiments, can traverse at least a part of a body of the user. In some other embodiments, the signal also can traverse a stylus that is in contact with the surface. The relative location of contact on the surface, in these embodiments, can include the relative location of contact by the stylus on the surface.
In some embodiments, the user transducer is in contact with a stylus. In these embodiments, the signal can traverse the stylus. The relative location of contact on the surface, in these embodiments, can include the relative location of contact by the stylus on the surface.
In some embodiments, the relative location of contact on the surface includes the relative location of contact by at least a part of the user's body at a single contact point on the surface. In other embodiments, the relative location of contact on the surface includes the relative location of contact by at least two parts of the user's body at two distinct contact points.
According to another aspect of concepts and technologies disclosed herein, each surface transducer of a plurality of surface transducers in contact with a surface can send a signal through the surface and a body of a user towards a user transducer that is in contact with the user. The user transducer can communicate a plurality of the received portions of the signal to a user device associated with the user. Each received portion of the plurality of received portions can correspond to a surface transducer of the plurality of surface transducers. The user device can analyze the plurality of received portions of the signal to determine a relative location of a part of the body of the user on the surface. The user device can perform a function responsive to the relative location. In some embodiments, the user transducer is in contact with the user through a stylus.
In some embodiments, the plurality of surface transducers are arranged in a centralized surface transducer configuration of a single transducer device. Alternatively, the plurality of surface transducers can be arranged in a distributed surface transducer configuration.
It should be appreciated that the above-described subject matter may be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable storage medium. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.
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 that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
The following detailed description is directed to a surface interface. More particularly, by using bone conduction technology, any surface can be turned into an input device. Additionally, the size of the interface area can be expanded and the interface can be shared by multiple concurrent users. The concepts and technologies described herein can support not only traditional touch gestures (e.g., swipe and tap), but also multi-touch gestures (e.g., two-handed pinch and stretch) as well as the use of input tools (e.g., a stylus and a dial).
According to one aspect of the concepts and technologies disclosed herein, bone conduction signals can be passed between surface transducers in, on, or attached to a surface and at least one user transducer in, on, or attached to a user. The bone conduction signals can be used to interpret movement and gestures performed by the user with one or more body parts (e.g., one or more fingers) in contact with the surface as input to a user device. The bone conduction signals can originate from the user transducer(s) (i.e., user-originated signal) or from the surface transducer(s) (i.e., surface-originated signal). The arrangement of the surface transducers can provide additional implementations as will be described herein. In some embodiments disclosed herein, a visualization of an input device (e.g., a keyboard) or other display can be projected onto the surface to create a fully-functional interface. Alternatively, the surface being used might be a display that, when combined with the concepts and technologies disclosed herein, becomes a fully-functional interface.
While the subject matter described herein may be presented, at times, in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, computer-executable instructions, and/or other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system, including hand-held devices, mobile devices, wireless devices, multiprocessor systems, distributed computing systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, routers, switches, other computing devices described herein, and the like.
In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments or examples. Referring now to the drawings, in which like numerals represent like elements throughout the several figures, example aspects of a surface interface will be presented.
Referring now to
The user's 102 body has a plurality of bones 108 (“bones 108”) through which one or more signals can propagate, a process referred to herein as “bone conduction.” It should be understood that a portion of a given bone conduction signal may propagate through other parts of the user's 102 body, such as fat, organ tissue, blood vessels, skin, and/or other tissue in addition to one or more of the bones 108.
The surface 104 can be any surface the user 102 can touch. The surface 104 might be, for example, at least a portion of a floor, a ceiling, a wall, a piece of furniture, a piece of art or other decoration, a portion of a user device 110 (e.g., a case, a screen/display, a keyboard, and/or a physical button), another device, a body of another user, an animal, clothing, footwear, handwear, headwear, jewelry, accessory, a vehicle, an object, or a food. The surface 104 can include a single surface or multiple surfaces. The surface 104 can be made from one or more materials. In some embodiments, the surface 104 is made from a composite material.
The user transducer 106 can transmit one or more bone conduction signals, such as one or more user-originated signals 112, through at least a portion of the user's 102 body towards the surface 104. The user transducer 106, additionally or alternatively, can receive one or more bone conduction signals or one or more portions thereof from one or more of a plurality of surface transducers 114. In the illustrated example, the plurality of surface transducers 114 includes a first surface transducer 114A, a second surface transducer 114B, and a third surface transducer 114C in, on, or attached to the surface 104. The surface transducers 114 can transmit one or more bone conduction signals, such as one or more surface-originated signals 116, to the user's 102 body to be received, at least in part, by the user transducer 106. The user transducer(s) 106 and the surface transducers 114, in some embodiments, are piezoelectric transducers, such as contact microphones or other electro-acoustic transducers.
The user device 110 can be a smartphone, feature phone, personal digital assistant (“PDA”), tablet device, laptop computer, desktop computer, server computer, video game system, handheld video game system, media player, set-top box, vehicle computing system, smart watch, television, consumer electronic device, personal tracker or safety device, dumbbell or other fitness equipment, other computing device, a combination thereof, or the like. It should be understood that the functionality of the user device 110 can be provided by a single device, by two or more similar devices, and/or by two or more dissimilar devices.
The illustrated user device 110 includes an operating system 118, one or more applications 120, a device-side transducer communications component 122, a signal analysis module 124, and a surface input interface 126. The operating system 118 is a program for controlling the operation of the user device 110. In some embodiments, the operating system 118 includes the signal analysis module 124, which is described in greater detail below. The operating system 118 can be executed by one or more processor(s) (best shown in
The user device 110 can utilize one or more processor(s) (best shown in
The device-side transducer communications component 122 can be or can include one or more transceivers configured to communicate with the user transducer(s) 106 and the surface transducers 114. In some embodiments, the device-side transducer communications component 122 can communicate with the user transducer(s) 106 and the surface transducers 114 using various communications technologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared, infrared data association (“IRDA”), near-field communications (“NFC”), ZIGBEE, Z-WAVE, other proprietary or non-proprietary RF technologies, combinations thereof, and the like. In some embodiments, the device-side transducer communications component 122 includes one or more transceivers that operate in accordance with one or more wireless telecommunications technologies such as, for example, Global System for Mobile communication (“GSM”), Code Division Multiple Access (“CDMA”), CDMAONE, CDMA2000, Long-Term Evolution (“LTE”), and various other 2G, 2.5G, 3G, 4G, 5G, and greater generation technology standards. Moreover, the device-side transducer communications component 122 may facilitate communications over various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, Time Division Multiple Access (“TDMA”), Frequency Division Multiple Access (“FDMA”), Wideband CDMA (“W-CDMA”), Orthogonal Frequency-Division multiplexing (“OFDM”), Space-Division Multiple Access (“SDMA”), and the like.
The user transducer(s) 106 and the surface transducers 114 can communicate characteristics of one or more bone conduction signals, such as the user-originated signal(s) 112 and/or the surface-originated signal(s) 116, to the signal analysis module 124. The signal analysis module 124 can analyze characteristics of the bone conduction signal(s) or one or more portions thereof to determine the relative location of the user's 102 contact with the surface 104 and the direction of movement (if any). In other embodiments, the user transducer(s) 106 and/or the surface transducers 114 include one or more processing components capable of performing, at least in part, the signal analysis and can report the results to the user device 110.
The body of the user 102 modifies bone conduction signals in unique ways. This enables the surface transducers 114 to distinguish between multiple users (not shown). The surface transducers 114 also can use characteristics of the received signal(s) to further distinguish between concurrent users. Moreover, differences between successive signals can be analyzed to enhance the accuracy of location and direction interpretations. Users also can be assigned unique waveforms allowing the surface transducers 114 to easily differentiate between multiple users. Similar functionality alternatively or additionally can be provided by the signal analysis module 124.
The surface input interface 126 can include software, firmware, hardware, or some combination thereof to support the surface 104, via the surface transducers 114 and the user transducer(s) 106, as an input device for the user device 110. The surface input interface 126 can provide a graphical user interface (“GUI”) on a display (best shown in
The surface transducers 114 can be arranged differently to meet the needs of various use cases. One approach is to contain all transducers in a single device, as shown in
Turning now to
Another possible arrangement of the surface transducers 114 is to distribute the surface transducers 114 across the surface 104. This arrangement improves accuracy for larger surfaces. This arrangement also enables the expansion of an input interface by adding one or more additional surface transducers 114 to the surface 104. The centralized arrangement and the distributed arrangement can be combined to reduce the total number of devices, increase the size of the interface, and/or to improve accuracy.
Turning now to
Turning now to
Turning now to
Turning now to
Turning now to
Turning now to
Turning now to
Turning now to
Turning now to
Turning now to
Turning now to
It also should be understood that the methods disclosed herein can be ended at any time and need not be performed in their respective entireties. Some or all operations of the methods, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer storage media, as defined herein. The term “computer-readable instructions,” and variants thereof, as used herein, is used expansively to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations including the user device 110, the user transducer(s) 106, the surface transducer(s) 114, single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, other devices and systems disclosed herein, combinations thereof, and the like.
Thus, it should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These states, operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. As used herein, the phrase “cause a processor to perform operations” and variants thereof refers to causing a processor of a computing system or device, such as the user device 110, the user transducer(s) 106, the surface transducer(s) 114, another device disclosed herein, or another system disclosed herein, to perform one or more operations and/or causing the processor to direct other components of the computing system or device to perform one or more of the operations.
For purposes of illustrating and describing some of the concepts of the present disclosure, the methods disclosed herein are described as being performed, at least in part, by the such as the user device 110, the user transducer(s) 106, and/or the surface transducer(s) 114, another via execution of one or more software modules and/or software applications. It should be understood that additional and/or alternative devices and/or systems can provide the functionality described herein via execution of one or more modules, applications, and/or other software. Thus, the illustrated embodiments are illustrative, and should not be viewed as being limiting in any way.
The method 400 begins and proceeds to operation 402, where the user transducer 106 sends the user-originated signal 112 through the body of the user 102 towards the surface 104 that is to be used as an input interface for the user device 110 associated with the user 102. From operation 402, the method 400 proceeds to operation 404, where each surface transducer 114 of the surface 104 communicates at least a received portion of the user-originated signal 112 to the user device 110.
From operation 404, the method 400 proceeds to operation 406, where the user device 110 analyzes the received portion(s) of the user-originated signal 112 from each surface transducer 114 to determine a relative location of a part of the body of the user 102 on the surface 104. From operation 406, the method 400 proceeds to operation 408, where the user device 110 performs one or more functions responsive to the relative location determined at operation 406. From operation 408, the method 400 proceeds to operation 410, where the method 400 ends.
Turning now to
From operation 504, the method 500 proceeds to operation 506, where the user device 110 analyzes the received portions of the surface-originated signals 116 from each surface transducer 114 to determine a relative location of a part of the body of the user 102 on the surface 104. From operation 506, the method 500 proceeds to operation 508, where the user device 110 performs one or more functions responsive to the relative location determined at operation 506. From operation 508, the method 500 proceeds to operation 510, where the method 500 ends.
Turning now to
As illustrated in
The UI application can interface with the operating system 608 to facilitate user interaction with functionality and/or data stored at the mobile device 600 and/or stored elsewhere. In some embodiments, the operating system 608 can include a member of the SYMBIAN OS family of operating systems from SYMBIAN LIMITED, a member of the WINDOWS MOBILE OS and/or WINDOWS PHONE OS families of operating systems from MICROSOFT CORPORATION, a member of the PALM WEBOS family of operating systems from HEWLETT PACKARD CORPORATION, a member of the BLACKBERRY OS family of operating systems from RESEARCH IN MOTION LIMITED, a member of the IOS family of operating systems from APPLE INC., a member of the ANDROID OS family of operating systems from GOOGLE INC., and/or other operating systems. These operating systems are merely illustrative of some contemplated operating systems that may be used in accordance with various embodiments of the concepts and technologies described herein and therefore should not be construed as being limiting in any way.
The UI application can be executed by the processor 604 to aid a user in entering content, viewing account information, answering/initiating calls, entering/deleting data, entering and setting user IDs and passwords for device access, configuring settings, manipulating address book content and/or settings, multimode interaction, interacting with other applications 610, and otherwise facilitating user interaction with the operating system 608, the applications 610, and/or other types or instances of data 612 that can be stored at the mobile device 600. The data 612 can include user preferences, user settings, and/or other data. The applications 610 can include, for example, presence applications, visual voice mail applications, messaging applications, text-to-speech and speech-to-text applications, add-ons, plug-ins, email applications, music applications, video applications, camera applications, location-based service applications, power conservation applications, game applications, productivity applications, entertainment applications, enterprise applications, combinations thereof, and the like. The applications 610, the data 612, and/or portions thereof can be stored in the memory 606 and/or in a firmware 614, and can be executed by the processor 604. The firmware 614 also can store code for execution during device power up and power down operations. It can be appreciated that the firmware 614 can be stored in a volatile or non-volatile data storage device including, but not limited to, the memory 606 and/or a portion thereof.
The mobile device 600 also can include an input/output (“I/O”) interface 616. The I/O interface 616 can be configured to support the input/output of data such as location information, user information, organization information, presence status information, user IDs, passwords, and application initiation (start-up) requests. In some embodiments, the I/O interface 616 can include a hardwire connection such as USB port, a mini-USB port, a micro-USB port, an audio jack, a PS2 port, an IEEE 1344 (“FIREWIRE”) port, a serial port, a parallel port, an Ethernet (RJ45rj 11) port, an RJ11 port, a proprietary port, combinations thereof, or the like. In some embodiments, the mobile device 600 can be configured to synchronize with another device to transfer content to and/or from the mobile device 600. In some embodiments, the mobile device 600 can be configured to receive updates to one or more of the applications 610 via the I/O interface 616, though this is not necessarily the case. In some embodiments, the I/O interface 616 accepts I/O devices such as keyboards, keypads, mice, interface tethers, printers, plotters, external storage, touch/multi-touch screens, touch pads, trackballs, joysticks, microphones, remote control devices, displays, projectors, medical equipment (e.g., stethoscopes, heart monitors, and other health metric monitors), modems, routers, external power sources, docking stations, combinations thereof, and the like. It should be appreciated that the I/O interface 616 may be used for communications between the mobile device 600 and a network device or local device.
The mobile device 600 also can include a communications component 618. The communications component 618 can be configured to interface with the processor 604 to facilitate wired and/or wireless communications with one or more networks. In some embodiments, other networks include networks that utilize non-cellular wireless technologies such as WI-FI or WIMAX. In some embodiments, the communications component 618 includes a multimode communications subsystem for facilitating communications via the cellular network and one or more other networks.
The communications component 618, in some embodiments, includes one or more transceivers. The one or more transceivers, if included, can be configured to communicate over the same and/or different wireless technology standards with respect to one another. For example, in some embodiments one or more of the transceivers of the communications component 618 may be configured to communicate using Global System for Mobile communication (“GSM”), Code Division Multiple Access (“CDMA”), CDMAONE, CDMA2000, Long-Term Evolution (“LTE”), and various other 2G, 2.5G, 3G, 4G, and greater generation technology standards. Moreover, the communications component 618 may facilitate communications over various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, Time Division Multiple Access (“TDMA”), Frequency Division Multiple Access (“FDMA”), Wideband CDMA (“W-CDMA”), Orthogonal Frequency-Division multiplexing (“OFDM”), Space-Division Multiple Access (“SDMA”), and the like.
In addition, the communications component 618 may facilitate data communications using Generic Packet Radio Service (“GPRS”), Enhanced Date Rates for GSM Evolution (“EDGE”), the High-Speed Packet Access (“HSPA”) protocol family, including High-Speed Downlink Packet Access (“HSDPA”), Enhanced Uplink (“EUL”) or otherwise termed Highs-Speed Uplink Packet Access (“HSUPA”), HSPA+, and various other current and future wireless data access standards. In the illustrated embodiment, the communications component 618 can include a first transceiver (“TxRx”) 620A that can operate in a first communications mode (e.g., GSM). The communications component 618 also can include an Nth transceiver (“TxRx”) 620N that can operate in a second communications mode relative to the first transceiver 620A (e.g., UMTS). While two transceivers 620A-620N (hereinafter collectively and/or generically referred to as “transceivers 620”) are shown in
The communications component 618 also can include an alternative transceiver (“Alt TxRx”) 622 for supporting other types and/or standards of communications. According to various contemplated embodiments, the alternative transceiver 622 can communicate using various communications technologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared, IRDA, NFC, other RF technologies, combinations thereof, and the like.
In some embodiments, the communications component 618 also can facilitate reception from terrestrial radio networks, digital satellite radio networks, internet-based radio service networks, combinations thereof, and the like. The communications component 618 can process data from a network such as the Internet, an intranet, a broadband network, a WI-FI hotspot, an Internet service provider (“ISP”), a digital subscriber line (“DSL”) provider, a broadband provider, combinations thereof, or the like.
The mobile device 600 also can include one or more sensors 624. The sensors 624 can include temperature sensors, light sensors, air quality sensors, movement sensors, orientation sensors, noise sensors, proximity sensors, or the like. As such, it should be understood that the sensors 624 can include, but are not limited to, accelerometers, magnetometers, gyroscopes, infrared sensors, noise sensors, microphones, combinations thereof, or the like. Additionally, audio capabilities for the mobile device 600 may be provided by an audio I/O component 626. The audio I/O component 626 of the mobile device 600 can include one or more speakers for the output of audio signals, one or more microphones for the collection and/or input of audio signals, and/or other audio input and/or output devices.
The illustrated mobile device 600 also can include a subscriber identity module (“SIM”) system 628. The SIM system 628 can include a universal SIM (“USIM”), a universal integrated circuit card (“UICC”) and/or other identity devices. The SIM system 628 can include and/or can be connected to or inserted into an interface such as a slot interface 630. In some embodiments, the slot interface 630 can be configured to accept insertion of other identity cards or modules for accessing various types of networks. Additionally, or alternatively, the slot interface 630 can be configured to accept multiple subscriber identity cards. Because other devices and/or modules for identifying users and/or the mobile device 600 are contemplated, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.
The mobile device 600 also can include an image capture and processing system 632 (“image system”). The image system 632 can be configured to capture or otherwise obtain photos, videos, and/or other visual information. As such, the image system 632 can include cameras, lenses, charge-coupled devices (“CCDs”), combinations thereof, or the like. The mobile device 600 may also include a video system 634. The video system 634 can be configured to capture, process, record, modify, and/or store video content. Photos and videos obtained using the image system 632 and the video system 634, respectively, may be added as message content to an MMS message, email message, and sent to another mobile device. The video and/or photo content also can be shared with other devices via various types of data transfers via wired and/or wireless communication devices as described herein.
The mobile device 600 also can include one or more location components 636. The location components 636 can be configured to send and/or receive signals to determine a geographic location of the mobile device 600. According to various embodiments, the location components 636 can send and/or receive signals from global positioning system (“GPS”) devices, assisted-GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellular network triangulation data, combinations thereof, and the like. The location component 636 also can be configured to communicate with the communications component 618 to retrieve triangulation data for determining a location of the mobile device 600. In some embodiments, the location component 636 can interface with cellular network nodes, telephone lines, satellites, location transmitters and/or beacons, wireless network transmitters and receivers, combinations thereof, and the like. In some embodiments, the location component 636 can include and/or can communicate with one or more of the sensors 624 such as a compass, an accelerometer, and/or a gyroscope to determine the orientation of the mobile device 600. Using the location component 636, the mobile device 600 can generate and/or receive data to identify its geographic location, or to transmit data used by other devices to determine the location of the mobile device 600. The location component 636 may include multiple components for determining the location and/or orientation of the mobile device 600.
The illustrated mobile device 600 also can include a power source 638. The power source 638 can include one or more batteries, power supplies, power cells, and/or other power subsystems including alternating current (“AC”) and/or direct current (“DC”) power devices. The power source 638 also can interface with an external power system or charging equipment via a power I/O component 640. Because the mobile device 600 can include additional and/or alternative components, the above embodiment should be understood as being illustrative of one possible operating environment for various embodiments of the concepts and technologies described herein. The described embodiment of the mobile device 600 is illustrative, and should not be construed as being limiting in any way.
The computer system 700 includes a processing unit 702, a memory 704, one or more user interface devices 706, one or more input/output (“I/O”) devices 708, and one or more network devices 710, each of which is operatively connected to a system bus 712. The bus 712 enables bi-directional communication between the processing unit 702, the memory 704, the user interface devices 706, the I/O devices 708, and the network devices 710.
The processing unit 702 may be a standard central processor that performs arithmetic and logical operations, a more specific purpose programmable logic controller (“PLC”), a programmable gate array, a system-on-a-chip, or other type of processor known to those skilled in the art and suitable for controlling the operation of the server computer. Processing units are generally known, and therefore are not described in further detail herein.
The memory 704 communicates with the processing unit 702 via the system bus 712. In some embodiments, the memory 704 is operatively connected to a memory controller (not shown) that enables communication with the processing unit 702 via the system bus 712. The memory 704 includes an operating system 714 (e.g., the operating system 118) and one or more program modules 716. The operating system 714 can include, but is not limited to, members of the WINDOWS, WINDOWS CE, and/or WINDOWS MOBILE families of operating systems from MICROSOFT CORPORATION, the LINUX family of operating systems, the SYMBIAN family of operating systems from SYMBIAN LIMITED, the BREW family of operating systems from QUALCOMM CORPORATION, the MAC OS, and/or iOS families of operating systems from APPLE CORPORATION, the FREEBSD family of operating systems, the SOLARIS family of operating systems from ORACLE CORPORATION, other operating systems, and the like.
The program modules 716 may include various software and/or program modules to perform the various operations described herein. The program modules 716 can include, for example, the signal analysis module 124, the device-side transducer communications component 122, and/or the application 120. The program modules 716 and/or other programs can be embodied in computer-readable media containing instructions that, when executed by the processing unit 702, perform one or more of the operations described herein. According to embodiments, the program modules 716 may be embodied in hardware, software, firmware, or any combination thereof. The memory 704 can also store other data, if desired.
By way of example, and not limitation, computer-readable media may include any available computer storage media or communication media that can be accessed by the computer system 700. Communication media includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media.
The term “modulated data signal” means a signal that has one or more of its characteristics changed or set in a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.
Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, Erasable Programmable ROM (“EPROM”), Electrically Erasable Programmable ROM (“EEPROM”), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer system 700. In the claims, the phrase “computer storage medium” and variations thereof does not include waves or signals per se and/or communication media.
The user interface devices 706 may include one or more devices with which a user accesses the computer system 700. The user interface devices 706 may include, but are not limited to, computers, servers, personal digital assistants, cellular phones, or any suitable computing devices. The I/O devices 708 enable a user to interface with the program modules 716. In one embodiment, the I/O devices 708 are operatively connected to an I/O controller (not shown) that enables communication with the processing unit 702 via the system bus 712. The I/O devices 708 may include one or more input devices, such as, but not limited to, a keyboard, a mouse, or an electronic stylus. Further, the I/O devices 708 may include one or more output devices, such as, but not limited to, a display screen or a printer.
The network devices 710 enable the computer system 700 to communicate with other networks or remote systems via a network 718. Examples of the network devices 710 include, but are not limited to, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface, a bridge, a router, or a network card. The network 718 may include a wireless network such as, but not limited to, a Wireless Local Area Network (“WLAN”), a Wireless Wide Area Network (“WWAN”), a Wireless Personal Area Network (“WPAN”) such as provided via BLUETOOTH technology, a Wireless Metropolitan Area Network (“WMAN”) such as a WiMAX network or metropolitan cellular network. Alternatively, the network 718 may be a wired network such as, but not limited to, a Wide Area Network (“WAN”), a wired LAN such as provided via Ethernet, a wired Personal Area Network (“PAN”), or a wired Metropolitan Area Network (“MAN”).
Turning now to
A mobile communications device 808, such as, for example, a cellular telephone, a user equipment, a mobile terminal, a PDA, a laptop computer, a handheld computer, the user device 110, and combinations thereof, can be operatively connected to the cellular network 802. The cellular network 802 can be configured as a 2G GSM network and can provide data communications via GPRS and/or EDGE. Additionally, or alternatively, the cellular network 802 can be configured as a 3G UMTS network and can provide data communications via the HSPA protocol family, for example, HSDPA, EUL (also referred to as HSUPA), and HSPA+. The cellular network 802 also is compatible with 4G mobile communications standards such as LTE, or the like, as well as evolved and future mobile standards.
The packet data network 804 includes various devices, for example, servers, computers, databases, and other devices in communication with another, as is generally known. The packet data network 804 devices are accessible via one or more network links. The servers often store various files that are provided to a requesting device such as, for example, a computer, a terminal, a smartphone, or the like. Typically, the requesting device includes software (a “browser”) for executing a web page in a format readable by the browser or other software. Other files and/or data may be accessible via “links” in the retrieved files, as is generally known. In some embodiments, the packet data network 804 includes or is in communication with the Internet. The circuit switched network 806 includes various hardware and software for providing circuit switched communications. The circuit switched network 806 may include, or may be, what is often referred to as a plain old telephone system (“POTS”). The functionality of a circuit switched network 806 or other circuit-switched network are generally known and will not be described herein in detail.
The illustrated cellular network 802 is shown in communication with the packet data network 804 and a circuit switched network 806, though it should be appreciated that this is not necessarily the case. One or more Internet-capable devices 810, for example, the user device 110, a PC, a laptop, a portable device, or another suitable device, can communicate with one or more cellular networks 802, and devices connected thereto, through the packet data network 804. It also should be appreciated that the Internet-capable device 810 can communicate with the packet data network 804 through the circuit switched network 806, the cellular network 802, and/or via other networks (not illustrated).
As illustrated, a communications device 812, for example, a telephone, facsimile machine, modem, computer, the user device 110, or the like, can be in communication with the circuit switched network 806, and therethrough to the packet data network 804 and/or the cellular network 802. It should be appreciated that the communications device 812 can be an Internet-capable device, and can be substantially similar to the Internet-capable device 810. In the specification, the network 800 is used to refer broadly to any combination of the networks 802, 804, 806. It should be appreciated that substantially all of the functionality described with reference to the network 502 can be performed by the cellular network 802, the packet data network 804, and/or the circuit switched network 806, alone or in combination with other networks, network elements, and the like.
Based on the foregoing, it should be appreciated that concepts and technologies directed to a surface interface have been disclosed herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological and transformative acts, specific computing machinery, and computer-readable media, it is to be understood that the concepts and technologies disclosed herein are not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the concepts and technologies disclosed herein.
The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the embodiments of the concepts and technologies disclosed herein.
The concepts and technologies disclosed herein can be enhanced, expanded, and/or diversified, at least in part, by the concepts and technologies disclosed in U.S. patent application Ser. No. 14/083,094 filed Nov. 18, 2013 and assigned to the Assignee of this application, which is hereby incorporated by reference in its entirety. For example, the concept of determining a pressure applied to a surface taught in the aforementioned patent application can be used to enable further functionality for the surface interface disclosed herein. In particular, the surface interface, in addition to detecting one or more contact points, the surface interface can detect a pressure applied at one or more contact points. In cases where the contact points are registered as writing input, the addition of pressure data can be used to modify the thickness of the writing (e.g., higher pressure corresponds to thicker line).
