WO2012109368A1 - Multimodal touchscreen interaction apparatuses, methods and systems - Google Patents
Multimodal touchscreen interaction apparatuses, methods and systems Download PDFInfo
- Publication number
- WO2012109368A1 WO2012109368A1 PCT/US2012/024350 US2012024350W WO2012109368A1 WO 2012109368 A1 WO2012109368 A1 WO 2012109368A1 US 2012024350 W US2012024350 W US 2012024350W WO 2012109368 A1 WO2012109368 A1 WO 2012109368A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- touch
- touchscreen
- processor
- mti
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/033—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
- G06F3/0354—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor with detection of 2D relative movements between the device, or an operating part thereof, and a plane or surface, e.g. 2D mice, trackballs, pens or pucks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/033—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
- G06F3/0354—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor with detection of 2D relative movements between the device, or an operating part thereof, and a plane or surface, e.g. 2D mice, trackballs, pens or pucks
- G06F3/03545—Pens or stylus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
Definitions
- the present innovations generally address apparatuses, methods, and systems for human-computer interaction, and more particularly, include MULTIMODAL TOUCHSCREEN INTERACTION APPARATUSES, METHODS AND SYSTEMS ("MTI"). BACKGROUND
- Electronic displays provide visual information for users.
- Some computer systems include mechanisms for the user to provide input in response to visual information provided by an electronic display.
- the computer system may include a touchscreen.
- a user may apply pressure on a portion of the touchscreen as a mechanism for providing input into the computer system.
- FIGURES lA-B show block diagrams illustrating example aspects of multimodal touchscreen interaction in some embodiments of the MTI; [ 0007] FIGURES 2A-D show block diagrams illustrating example aspects of multimodal touch sensing in some embodiments of the MTI; [ 0008 ] FIGURE 3 shows block diagrams illustrating example aspects of light- based touch input recognition in some embodiments of the MTI; [ 0009 ] FIGURES 4A-B show logic flow diagrams illustrating example aspects of multimodal touch processing in some embodiments of the MTI, e.g., a Multimodal Touch Processing ("MTP") component 400; [ 0010 ] FIGURE 5 shows a logic flow diagram illustrating example aspects of touch coordinate determination in some embodiments of the MTI, e.g., a Touch Coordinate Determination (“TCD”) component 500; [o o i i] FIGURE
- FIGURES lA-B show block diagrams illustrating example aspects of multimodal touchscreen interaction in some embodiments of the MTI.
- the MTI may provide a touchscreen 100.
- a user may touch a display provided by the MTI with a finger or hand or object such as a stylus.
- the touchscreen may be an electronic visual display that can detect the presence and location of a touch within the display area, and translate the detected touch into a processed interaction with content being displayed.
- the MTI may provide a mechanism whereby virtual overlays or surfaces may receive user input entering, interacting with or touching a given surface comprising or hosting a display.
- the touchscreen may comprise a frame outlined or supported with sensors designed to detect subtle physical and ambient changes in the touchscreen or its vicinity. The sensors may detect and track the contact of a variety of objects on a defined surface in space and time.
- the touchscreen surface may include, without limitation, an overlay on a digital display, e.g.
- the MTI may provide multi touch screens designed to simultaneously detect and interpret two or more distinct touch events on a single display, including those which can interpret various "gestures" made by two or more fingers.
- the MTI may implement multi-touch touchscreens using any of the various touch detection and tracking implementations discussed herein. Accordingly, the MTI may enable gesture interpretation capabilities, thus providing a rich and sophisticated array of user interactions with displayed content.
- the MTI may facilitate a single user to provide a single type of input (e.g., stylus input 101a, finger input 101b, etc.). In some embodiments, the MTI may facilitate a single user to provide multiple simultaneous input touches (e.g., multi-stylus input IOIC, hybrid stylus-finger input loid, multi-finger input loie, multi-hand, multi-finger input loif, multi-finger hybrid stylus-finger input loig, and/or like combinations).
- a single type of input e.g., stylus input 101a, finger input 101b, etc.
- the MTI may facilitate a single user to provide multiple simultaneous input touches (e.g., multi-stylus input IOIC, hybrid stylus-finger input loid, multi-finger input loie, multi-hand, multi-finger input loif, multi-finger hybrid stylus-finger input loig, and/or like combinations).
- the MTI may facilitate a number of users (e.g., useri iioa, user2 nob, user3 HOC) to simultaneously provide inputs such as those described above with reference to FIGURE lA into the touchscreen 100.
- each user may be interacting with a separate executable application (e.g., applicationi ma, application nib, applications me) displayed on the touchscreen provided by the MTI.
- the MTI may receive, distinguish, and uniquely identify each of the (possibly simultaneous) inputs from each of the (possibly simultaneously acting) users and associate the inputs of each of the users to the respective applications they are interacting with on the MTI.
- the MTI may recognize, and distinguish between, finger and stylus inputs of the users such that both finger and stylus inputs may be sensed as contacting the screen as different types of touches.
- the MTI may adapt the user interface of an application being displayed on the touchscreen to behave differently when a finger interacts with it as opposed to when a stylus interacts with it.
- the features provided by the application for the user may vary depending on whether the user utilizes a finger or a stylus to interact with the application (for example, even when the shape of the user's gesture on the touchscreen of the MTI is the same with the finger and the stylus).
- a finger touch-based gesture may provide the user with an eraser tool in a drawing application, while the same gesture using a stylus may provide a drawing tool in the drawing application.
- some user controls may be activated by stylus touch (and for example, not by a finger touch), enabling new hybrid touch gestures defined by how the stylus and finger are used simultaneously in a gesture.
- touchscreen application software (or "apps") may dedicate and/ or divide specific tracking processes to be performed on either the finger or stylus, or both.
- a touchscreen application executing on the MTI may apply additional smoothing when fingers are used to draw compared to when a stylus (or styli) are used to draw in the application.
- FIGURES 2A-D show block diagrams illustrating example aspects of multimodal touch sensing in some embodiments of the MTI.
- the MTI may include touchscreens that utilize, for touch sensing, a wide variety of technologies including, without limitation, resistive/capacitive films, "overlays" comprising a frame mounted on a display surface, cameras observing a surface from behind, audio sensors for triangulating the position of an object based on the acoustic vibrations the object makes as it moves around the display surface.
- the sensors may be made of a plastic polymer providing pre-calibrated and optimized resilience and flexibility, and host an electrostatic field that is sensitive to distortions caused by proximity to or contact with electro-statically charged objects such as a finger.
- the MTI may provide resistive/ capacitive touchscreens may that include extendable sensitivity ranges and proximity sensing capabilities.
- the overlay surface may be pressure sensitive measuring the amount of force being applied to the surface.
- the touchscreen may include the use of high resolution pixel sensors, with fast refresh rates (e.g., over 120Hz), high contrast ratios with no-haze transparency.
- the touchscreen sensors may be automatically calibrated or customized to user/group preferences, application being executed, environmental conditions in the vicinity of the touchscreen, etc.
- the various implementations described above may be combined in touch screens that detect, track or interpret touch interactions using multiple modes.
- a laser light plane (LLP), infrared (IR) or other optical waves may be projected across the display surface and a touch detected through sensors when an object disturbs the projected optical waves.
- a touchscreen 210 may incorporate the display surface with infrared light sources 215 mounted to shine light parallel to the surface, and sensors mounted to observe this light and any disturbance to it.
- the touchscreen display surface may be flat, but in others may be operatively curved for certain types of curvature, e.g. a cylinder section.
- embodiments may operate for varying wavelengths of electromagnetic radiation, e.g. visible light.
- Some embodiments may utilize a rectangular frame 211 around a portion of the surface, with infrared light sources and sensors embedded in the frame.
- infrared light sources may be incorporated (e.g., continuously, with periodic spacing, at equal angular spacing as observed from a predetermined reference point, etc.) around the interior of the frame, and sensors may be located in two or more corners of the rectangular frame (see 214).
- light emitters and sensors may be embedded as matched pairs across from each other in the frame, e.g. one side of frame may include emitters, and the opposite side may include sensors corresponding to these emitters.
- a frame around a touch screen may include a hybrid set of sensors at different sensitivity levels, resolutions and/ or timing attributes.
- illumination sensors may be positioned on the sensing plane, e.g. one-dimensional IR-LEDs.
- the frame may also include multiple sensors positioned strategically over a given interaction region.
- the touchscreen may include sensors outside the surface plane, e.g. two-dimensional via complimentary metal-oxide semiconductor (CMOS) and IR Laser Diodes.
- CMOS complimentary metal-oxide semiconductor
- IR Laser Diodes IR Laser Diodes
- interaction with the touchscreen may not require the touch object and/or stylus physically contact the surface, and permit the touchscreen to receive remote interactive input, e.g. from a mobile or remote device.
- the object interacting with the touchscreen may take many forms.
- the object being detected may be a finger, a stylus, or a member having a distal end with a predefined pattern, e.g. a regular or irregular shape.
- the touchscreen may triangulate multiple sensor readings to determine an object's location.
- a stylus with an infrared light emitter may be used to interact with the touchscreen.
- the touchscreen may detect the infrared light stylus via light sensor (either observing from behind the screen or in plane of screen) as a bright spot.
- the touchscreen may emit infrared light to detect a finger touch action through reflection or occlusion.
- Some screens may also embed infrared light sources shining in plane of touchscreen, so that finger touching screen is illuminated by IR light and is detectable as a bright spot in light sensors.
- an overlay frame around the touchscreen may include embedded infrared lights shining parallel to the surface and light sensors that sense increased brightness when objects break a defined plane to reflect light back to sensors.
- a touchscreen panel may receive input from a finger 212 and stylus 213 simultaneously while tracking each independently.
- sensors 214 may be tuned to detect emitted light from the stylus or reflected light because of the finger touch.
- the intensity of light emitted by the stylus 213 may be brighter than the light reflected by the finger touch or the normal intensities of the light emitted above the plane of the screen in the absence of a user touch.
- the overlay frame may include an embedded infrared light source shining parallel to surface, and sensors that detect when light is blocked by an object (such as a finger) making contact on the surface between the light source and sensor.
- some embodiments may utilize touchscreens where touches are detected by blocked or occluded light.
- the instance of a touch event 222 may be detected via sensors 220 tuned to recognize breaks in or lowered intensity of emitted or transmitted light 225, and then 1 the location of the detected touch event may be triangulated (e.g., via touch processor
- a distinction algorithm may instruct the sensors to detect locations that
- the stylus 8 normal on may be interpreted as finger touches 222.
- 9 223 may include an RF transmitter, and the position of the stylus may be triangulated
- a touchscreen panel 11 [ 0023 ] With reference to FIGURE 2C, in some embodiments, a touchscreen panel
- 12 230 may receive input from a finger 234 and styli (see 235) while communicating with
- input touchscreen panel 230 may be tracked and processed by touch processor 231 into
- networked screens 232-233 may themselves be touch screens with
- the networked is touchscreens may include a number of additional input types including camera based
- touch/proximity input screens e.g., surface backed cameras, front mount cameras, rear
- resistive/capacitive touch screen-based input screens 20 positioned cameras
- resistive/capacitive touch screen-based input screens 20 positioned cameras
- the styli utilized may include an IR LED
- the styli may also include a switch attached externally or embedded, for closing an electrical circuit that may activate the LED or RF transmitter when the stylus is actuated or pressed against an object.
- the sensors may distinguish between multiple styli 235.
- a given stylus with an LED in tip may continuously emit IR light while in contact with a touch screen surface where it is detected and tracked by sensors trained on the display surface (either in plane, from behind or in front). With multiple styli emitting the same light, sensors may read a series of similar bright spots without distinguishing between them.
- the IR LED of a particular stylus may blink on and off, where different styli may use a different pattern or frequency of blinking, enabling the sensors to distinguish between them. While frequency patterns permit distinction, some touchscreens may also benefit from precise tracking.
- each stylus may create a different spatial pattern of light when contacting/approaching the touchscreen surface. With an appropriately defined stylus size and sensor range, patterns may be recognizable when stylus is at various locations relative to the IR sensors.
- the styli may include color LEDs to enhance contrast for the sensors. Implementations may include two LEDs where their brightness varies over time. This way, stylus may be continuously visible to sensors (doesn't goes dark), but modulation between "bright and brighter" can be performed in different time patterns or frequencies so that different styli may be distinguished. Thus, high fidelity location tracking may be retained while allowing multiple stylus tracks to be distinguished from each other.
- FIGURE 2D illustrates examples of input styli.
- input member 243 is a stylus with an IR LED at a given distal end.
- the input member may include an IR LED pair located at a proximal end.
- the stylus input member may include a toggle switch for turning the stylus on/ off and/ or control additional stylus functions 242.
- a linear touch sensitive slide may provide further control, e.g. precision of line weight outputted to the touchscreen.
- the stylus 241 may include wireless communication hardware, an audio microphone and/ or embedded biometric identification software.
- the styli of FIGURE 2D may further include an RF transmitter/receiver for sensor triangulation and identification purposes.
- a stylus identifier, stylus ID may be associated with different time modulation patterns. Each ID may be associated with a different time frequency of a sinusoidal or step pattern, offset well above zero brightness.
- the stylus ID may include a Morse code-like time patterns. Implementations may further include LED pairs at both ends of a stylus, each end using a different time modulation pattern.
- a switch on side of stylus-pen may be used to change time modulation pattern, and hence switch "ID" of stylus.
- Time modulation pattern recognition may occur with some delay from first observation of a stylus on a touch screen surface. However, for high frequency patterns, and sensors that operate at high frame rate, this delay can be very small.
- this initial estimate can be used until observations can be used to verify or correct the stylus ID(s) a few frames later, and this initial estimate may be likely to be correct a very high percentage of the time for normal touchscreen usage.
- a stylus may include a Radio Frequency (RF) transmitter antenna and/ or receiver to establish communication with the touchscreen.
- RF Radio Frequency
- Implementations of a stylus and touchscreen utilizing RF transmissions may use radio waves to transmit signals between a transmitter and a receiver.
- the stylus antenna may be attached to a stylus transmitter unit embedded in the stylus or otherwise coupled in operative communication.
- the stylus transmitter is positioned in a manner allowing the touchscreen receiver to receive signals from the stylus.
- the RF communications between the styli may occur over single channel and/ or multi-channel systems.
- One embodiment of a multi-channel system may further include a channel selector on an RF stylus and/ or touchscreen transmitter/receiver.
- FIGURE 3 shows block diagrams illustrating example aspects of light- based touch input recognition in some embodiments of the MTI.
- Sub-figures 3(a)-(b) illustrate example output graphs of IR light sensitivity to stylus and finger input touches, where finger touches are detected by measuring reflection caused by the finger touch.
- normal light levels may be measured as seen by sensors when IR light sources are on, and set two thresholds, one relating to finger touches and one to stylus touches.
- both thresholds may be above the normal light level and the stylus threshold may remain the still the higher one.
- Sub-figures 3(c)-(d) illustrate example output graphs of IR light sensitivity to stylus and finger input touches, where finger touches are detected by measuring occlusion caused by the finger touch.
- the graphs may show what a lD camera sees at each of many angles in plane of surface. So, horizontal axis "theta", for example, may refer to an angle the IR imager is looking at.
- the threshold lines may be dynamically varying rather than the constant level, as noted by the arrows.
- the MTI may assume a noisy, non-uniform baseline light level, and set the threshold to have the same shape, but offset above or below.
- the MTI could calculate the thresholds required as a percentage (e.g. 120% or 80%) of the normal light level at each position in the graph, where the normal light levels may vary over the touchscreen space, and in time as well.
- the sensors may measure and define a normal light level observed by each sensor when IR sources are turned on.
- the touchscreen software may set "thresholdi" above this normal light level, and detect stylus touches where brightness exceeds this threshold. In one embodiment, it may set "threshold2" below this normal light level, and detect finger touches where brightness falls below this second threshold.
- thresholds may be set differently for each sensor, and may be spatially varied if the sensor is operable to see a range of spatial locations along plane of screen. This may include a non-uniform "normal" brightness level and non-uniform thresholds above and below.
- the calibration of touch overlay software may be set so that neutral (no contact with finger or stylus) represents a middle value.
- the touchscreen may detect, interpret and differentiate touch interactions from multiple object types (e.g., fingers and styli), and also touch interactions from more than one of the same object type (e.g., distinct styli), 1 whether from a single or multiple users. As discussed in greater detail below, one
- 4 embodiment may be implemented with touch screens using at least optical touch
- FIGURES 4A-B show logic flow diagrams illustrating example aspects of
- a user may provide a touch input, 401, into a touchscreen of the MTI.
- the user may utilize one or more finger touches, one or more light/RF-
- the touchscreen sensors may
- the touchscreen sensors may generate a light intensity
- the sensors may communicate the light intensity
- the sensors may
- the touch processor may obtain the light intensity signal, and may
- the touch processor may execute a touch coordinate determination
- the touch processor may produce data such as the example coordinates provided in the inset with reference to FIGURE 7, 701.
- the touch processor may set each of the coordinate sets (e.g., ⁇ x,y,z ⁇ ) as a touch input, 405.
- the touch processor may identify a type (e.g., finger, stylus, etc.) for each touch input provided by the user, 406.
- the touch processor may execute a touch type identification component such as the example TTI 600 component described below in the discussion with reference to FIGURE 6. Based on this computation, the touch processor may produce data such as the example touch types provided in the inset with reference to FIGURE 7, 701.
- the touch processor may determine, 407, which touch inputs provided by the user should be grouped together as part of a single gesture (e.g., "should the two finger touches and one stylus touch be considered part of a single gesture on behalf of one user?").
- the touch processor may execute a touch group resolution component such as the example TGR 700 component described further below in the discussion with reference to FIGURES 7A-B. Based on this computation, the touch processor may produce data such as the example touch groups provided in the inset with reference to FIGURE 7, 705.
- the touch processor may generate query(ies) for a database, 408, for prior touch input groups within a pre-determined time window to be combined as part of a gesture sequence, 408.
- a four-finger swipe may be considered not an instantaneous gesture; rather, the gesture may be identified by tracking the movement of four fingers of a user over a finite time window.
- a gesture may require two distinct sets of user touches (e.g., a two-finger tap, and a one-stylus tap).
- the queried database/memory may provide prior touch inputs sets, 409, for identifying gesture sequences.
- the touch processor may utilize a Hypertext Preprocessor (PHP) script including Structured Query Language (SQL) commands to query a relational database for the prior touch input sets.
- PGP Hypertext Preprocessor
- SQL Structured Query Language
- the touch processor may generate gesture patterns/sequences from the touch input groups, 410.
- the touch processor may tag each gesture pattern/sequence with a user ID (either of a user known to be at the approximate spatial location (e.g., using camera-based facial recognition, user login at the touchscreen location, etc.), or a randomly generated ID, which may be assigned to any other gesture sequences performed at the approximate location).
- the touch process may query a database/memory for user command(s) associated with the gesture patterns/sequences, 412.
- the database/memory may provide the requested user command(s), which may be stored in a process queue for execution.
- the touch processor may select a user command from a process queue (e.g., optionally generated as per the procedure described above in the discussion with reference to FIGURE 4A), 414.
- the touch processor may generate a query for the gesture pattern associated with the user command, 415.
- the database/memory may provide the prior touch input sets that formed part of the gesture pattern, 416.
- the touch processor may extract the touch inputs forming part of the gesture pattern, 417.
- the touch process may parse the data using a parser such as the example ones described below in the discussion with reference to FIGURE 8.
- the touch processor may determine whether any of the touch inputs sets included a hybrid stylus-finger user input, 418. If any of the touch inputs sets included a hybrid stylus-finger user input, 418, option "Yes," the touch process may generate a query for any modifications to the user command 1 normally associated with the gesture, 419. Upon obtaining any modifications to the user
- the touch processor may execute the
- processor may perform such a procedure for each user command stored in the process
- FIGURE 5 shows a logic flow diagram illustrating example aspects of
- TCD Coordinate Determination
- processor of the MTI may obtain a light intensity signal from a touchscreen sensor for
- the touch processor may optionally generate a digital touch map
- the touch processor may apply a
- 15 threshold are set to zero, and all above are set to one.
- two separate threshold are set to zero, and all above are set to one.
- 16 thresholds may be applied so that the pixels corresponding to both light-emitting styli
- the touch processor may identify each touch (or its
- the touch processor may use an image segmentation algorithm
- the touch processor may calculate a centroid based on an Intensity-
- FIGURE 6 shows a logic flow diagram illustrating example aspects of touch type identification in some embodiments of the MTI, e.g., a Touch Type Identification ("TTP") component 600.
- a touch processor of the MTI may obtain touch IDs, and location coordinates for each touch (see, e.g., FIGURE 5, 506), for identifying a type of touch for each touch ID, 601.
- the touch processor may also obtain the original light intensity signal (see, e.g., FIGURE 4A, 403), 602.
- the touch process may select a touch ID, 603, and look up the location coordinates for the selected touch ID, 604. Using the location coordinates, the touch processor may lookup the original intensity level of the pixel corresponding to the location coordinates (or an average for a window of pixels in its vicinity) using the light intensity signal, 605. The touch processor may compare the light intensity level samples to the threshold(s) for stylus input to be detected and/or for a finger input to be detected. Based on the comparison, the touch processor may identify the touch type as either a stylus input or a finger input, 606. The touch processor may perform such a procedure for each touch ID obtained (see 607). The touch process may return the touch IDs and touch types for further processing, 608.
- FIGURES 7A-B show logic flow diagrams illustrating example aspects of touch group resolution in some embodiments of the MTI, e.g., a Touch Group Resolution ("TGR") component 700.
- a touch processor of the MTI may obtain touch IDs, and location coordinates for each touch, 701 (see inset), to resolve which touches of one or more users should be grouped together as part of a single gesture or gesture pattern/sequence.
- the touch processor may calculate the distance between each pair of touch inputs using the location coordinates, 702 (see inset, distance matrix).
- the touch processor may apply a thresholding procedure to the distance matrix, such that all matrix elements above the threshold are set to zero, and those below are set to one.
- the touch processor may utilize the proximity matrix of 703 to identify those touches that are proximal pairs, 704 (see inset, pair matrix).
- the touch processor may merge proximal pairs together that have at least one common touch ID, 705, to generate the touch group (see 705, inset), which the touch process may return, 706, for further processing.
- FIGURE 8 shows a block diagram illustrating embodiments of a MTI controller 801.
- the MTI controller 801 may serve to aggregate, process, store, search, serve, identify, instruct, generate, match, and/or facilitate interactions with a computer through various technologies, and/or other related data.
- users e.g., 833a, which may be people and/or other systems, may engage information technology systems (e.g., computers) to facilitate information processing.
- computers employ processors to process information; such processors 803 may be referred to as central processing units (CPU).
- CPUs use communicative circuits to pass binary encoded signals acting as instructions to enable various operations.
- These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory 829 (e.g., registers, cache memory, random access memory, etc.). Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations. These stored instruction codes, e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations.
- One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources.
- Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components.
- the MTI controller 801 may be connected to and/or communicate with entities such as, but not limited to: one or more users from user input devices 811; peripheral devices 812; an optional cryptographic processor device 828; and/or a communications network 813.
- the MTI controller 801 may be connected to and/or communicate with users, e.g., 833a, operating client device(s), e.g., 833b, including, but not limited to, personal computer(s), server(s) and/or various mobile device(s) including, but not limited to, cellular telephone(s), smartphone(s) (e.g., iPhone®, Blackberry®, Android OS-based phones etc.), tablet computer(s) (e.g., Apple iPadTM, HP SlateTM, Motorola XoomTM, etc.), eBook reader(s) (e.g., Amazon KindleTM, Barnes and Noble's NookTM eReader, etc.), laptop computer(s), notebook(s), netbook(s), gaming console(s) (e.g., XBOX LiveTM, Nintendo® DS, Sony PlayStation® Portable, etc.), portable scanner(s), and/or the like.
- users e.g., 833a, operating client device(s), e.g., 833b
- Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology.
- server refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting "clients.”
- client refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network.
- a computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a "node.”
- Networks are generally thought to facilitate the transfer of information from source points to destinations.
- a node specifically tasked with furthering the passage of information from a source to a destination is commonly called a "router.”
- There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc.
- LANs Local Area Networks
- WANs Wide Area Networks
- WLANs Wireless Networks
- the MTI controller 801 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 802 connected to memory 829.
- a computer systemization 802 may comprise a clock 830, central processing unit (“CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 803, a memory 829 (e.g., a read only memory (ROM) 806, a random access memory (RAM) 805, etc.), and/or an interface bus 807, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 804 on one or more (mother )board(s) 802 having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effectuate communications, operations, storage, etc.
- the computer systemization may be connected to a power source 886; e.g., optionally the power source may be internal.
- a cryptographic processor 826 and/or transceivers (e.g., ICs) 874 may be connected to the system bus.
- the cryptographic processor and/or transceivers may be connected as either internal and/or external peripheral devices 812 via the interface bus I/O.
- the transceivers may be connected to antenna(s) 875, thereby effectuating wireless transmission and reception of various communication and/or sensor protocols; for example the antenna(s) may connect to: a Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.1m, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing MTI controller to determine its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.1m, Bluetooth 2.1 + EDR, FM, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA communications); and/or the like.
- a Texas Instruments WiLink WL1283 transceiver chip e.g., providing 802.1m, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing MTI controller to determine its location)
- the system clock typically has a crystal oscillator and generates a base signal through the computer systemization's circuit pathways.
- the clock is typically coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization.
- the clock and various components in a computer systemization drive signals embodying information throughout the system.
- Such transmission and reception of instructions embodying information throughout a computer systemization may be commonly referred to as communications.
- These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like.
- any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems.
- the CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests.
- the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like.
- processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 829 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc.
- the processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state.
- the CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s).
- the CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques. Such instruction passing facilitates communication within the MTI controller and beyond through various interfaces.
- MTI Distributed MTI
- mainframe multi-core
- parallel and/or super-computer architectures
- PDAs Personal Digital Assistants
- features of the MTI may be achieved by implementing a microcontroller such as CAST'S R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like.
- some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit ("ASIC"), Digital Signal Processing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or the like embedded technology.
- ASIC Application-Specific Integrated Circuit
- DSP Digital Signal Processing
- FPGA Field Programmable Gate Array
- any of the MTI component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like.
- some implementations of the MTI may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.
- the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/ software solutions.
- MTI features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called “logic blocks", and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx.
- Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the MTI features.
- a hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the MTI system designer/administrator, somewhat like a one-chip programmable breadboard.
- An FPGA's logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or 1 more complex combinational operators such as decoders or simple mathematical
- the logic blocks also include memory elements, which may
- 4 MTI may be developed on regular FPGAs and then migrated into a fixed version that
- microprocessors may be considered the "CPU” and/or “processor” for the MTI.
- the power source 886 may be of any standard form for powering small
- the case provides an aperture through which the solar cell may
- the power cell 886 is connected to at least one of the
- the power source 886 is connected to the
- USB 19 886 is provided through a connection across the I/O 808 interface.
- a USB connection across the I/O 808 interface For example, a USB
- 20 and/or IEEE 1394 connection carries both data and power across the connection and is
- Interface bus(ses) 807 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 808, storage interfaces 809, network interfaces 810, and/or the like.
- cryptographic processor interfaces 827 similarly may be connected to the interface bus.
- the interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization.
- Interface adapters are adapted for a compatible interface bus.
- Interface adapters conventionally connect to the interface bus via a slot architecture.
- Storage interfaces 809 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 814, removable disc devices, and/or the like.
- Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.
- connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.
- Network interfaces 810 may accept, communicate, and/or connect to a communications network 813.
- the MTI controller is accessible through remote clients 833b (e.g., computers with web browsers) by users 833a.
- Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 8o2.na-x, and/or the like.
- connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 8o2.na-x, and/or the like.
- distributed network controllers e.g., Distributed MTI
- architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the MTI controller.
- a communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like.
- a network interface may be regarded as a specialized form of an input output interface.
- multiple network interfaces 810 may be used to engage with various communications network types 813. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks.
- I/O 808 may accept, communicate, and/or connect to user input devices 811, peripheral devices 812, cryptographic processor devices 828, and/or the like.
- I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE I394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 8o2.na/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet
- CDMA code division multiple access
- One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used.
- the video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame.
- Another output device is a television set, which accepts signals from a video interface.
- the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.).
- User input devices 811 often are a type of peripheral device 812 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.
- peripheral device 812 may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.
- Peripheral devices 812 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the MTI controller.
- Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices 828), force-feedback devices (e.g., vibrating motors), network interfaces, printers, scanners, storage devices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, and/or the like.
- audio devices e.g., line-in, line-out, microphone input, speakers, etc.
- cameras e.g., still, video, webcam, etc.
- dongles e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like
- Peripheral devices often include types of input devices (e.g., cameras).
- the MTI controller may be embodied as an embedded, dedicated, and/or monitor-less (i.e., headless) device, wherein access would be provided over a network interface connection.
- Cryptographic units such as, but not limited to, microcontrollers, processors 826, interfaces 827, and/or devices 828 may be attached, and/or communicate with the MTI controller.
- a MC68HC16 microcontroller, manufactured by Motorola Inc., may be used for and/or within cryptographic units.
- the MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation.
- Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions.
- Cryptographic units may also be configured as part of the CPU. Equivalent microcontrollers and/or processors may also be used.
- Typical commercially available specialized cryptographic processors include: the Broadcom's CryptoNetX and other Security Processors; nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable of performing 500+ MB/s of cryptographic instructions; VLSI Technology's 33 MHz 6868; and/or the like.
- Memory e.g., L2100, L2200, U2400
- any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory 829.
- memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another.
- the MTI controller and/or a computer systemization may employ various forms of memory 829.
- a computer systemization may be configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; however, such an embodiment would result in an extremely slow rate of operation.
- memory 829 will include ROM 806, RAM 805, and a storage device 814.
- a storage device 814 may be any conventional computer system storage. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like.
- RAID Redundant Array of Independent Disks
- SSD solid state drives
- the memory 829 may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s) 815 (operating system); information server component(s) 816 (information server); user interface component(s) 817 (user interface); Web browser component(s) 818 (Web browser); database(s) 819; mail server component(s) 821; mail client component(s) 822; cryptographic server component(s) 820 (cryptographic server); the MTI component(s) 835; and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus.
- operating system component(s) 815 operating system
- information server component(s) 816 information server
- user interface component(s) 817 user interface
- Web browser component(s) 818 Web browser
- database(s) 819 mail server component(s) 821; mail client component(s) 822; cryptographic server component(s) 820 (cryptographic
- non-conventional program components such as those in the component collection, typically, are stored in a local storage device 814, they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like.
- the operating system component 815 is an executable program component facilitating the operation of the MTI controller. Typically, the operating system facilitates access of I/O, network interfaces, peripheral devices, storage devices, and/or the like.
- the operating system may be a highly fault tolerant, scalable, and secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution 1 (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux
- An operating system may communicate to and/or with other components in a
- the operating system may contain, communicate, generate, obtain, and/or0 provide program component, system, user, and/or data communications, requests,1 and/or responses.
- the operating system once executed by the CPU, may enable the2 interaction with communications networks, data, I/O, peripheral devices, program3 components, memory, user input devices, and/or the like.
- the operating system may4 provide communications protocols that allow the MTI controller to communicate with5 other entities through a communications network 813.
- Various communication6 protocols may be used by the MTI controller as a subcarrier transport mechanism for7 interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the8 like.
- An information server component 816 is a stored program component that1 is executed by a CPU.
- the information server may be a conventional Internet2 information server such as, but not limited to Apache Software Foundation's Apache,3 Microsoft's Internet Information Server, and/or the like.
- the information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like.
- the information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo!
- FTP File Transfer Protocol
- HTTP HyperText Transfer Protocol
- HTTPS Secure Hypertext Transfer Protocol
- SSL Secure Socket Layer
- messaging protocols e.g., America Online (A
- the information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components.
- DNS Domain Name System
- a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request "123.124.125.126” resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the "/mylnformation.html” portion of the request and resolve it to a location in memory containing the information "mylnformation.html.”
- other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like.
- An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like.
- the information server communicates with the MTI database 819, operating systems, other program components, user interfaces, Web browsers, and/or the like.
- Access to the MTI database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the MTI.
- the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such.
- the entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields.
- the parser may generate queries in standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the MTI as a query.
- the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web 1 page is then provided to the information server, which may supply it to the requesting
- an information server may contain, communicate, generate, obtain,
- Automobile operation interface elements such as steering wheels, gearshifts,
- Computer interaction interface elements such as check boxes, cursors,
- GUIs Graphical user interfaces
- GNOME web interface libraries
- JavaScript etc. interface libraries such as, but not limited to, Dojo, jQuery(UI),
- 22 may be used and) provide a baseline and means of accessing and displaying information
- a user interface component 817 is a stored program component that is executed by a CPU.
- the user interface may be a conventional graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed.
- the user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities.
- the user interface provides a facility through which users may affect, interact, and/or operate a computer system.
- a user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like.
- the user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
- a Web browser component 818 is a stored program component that is executed by a CPU.
- the Web browser may be a conventional hypertext viewing application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web browsing may be supplied with I28bit (or greater) encryption by way of HTTPS, SSL, and/or the like.
- Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like.
- Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices.
- a Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the MTI enabled nodes. The combined application may be nugatory on systems employing standard Web browsers. Mail Server
- a mail server component 821 is a stored program component that is executed by a CPU 803.
- the mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/or the like.
- the mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like.
- the mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like.
- IMAP Internet message access protocol
- MAPI Messaging Application Programming Interface
- PMP3 post office protocol
- simple mail transfer protocol SMTP
- the mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the MTI.
- Access to the MTI mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system.
- a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.
- a mail client component 822 is a stored program component that is executed by a CPU 803.
- the mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like.
- Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like.
- a mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like.
- the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.
- the mail client provides a facility to compose and transmit electronic mail messages.
- a cryptographic server component 820 is a stored program component that is executed by a CPU 803, cryptographic processor 826, cryptographic processor interface 827, cryptographic processor device 828, and/or the like.
- Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU.
- the cryptographic component allows for the encryption and/or decryption of provided data.
- the cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption.
- PGP Pretty Good Protection
- the cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like.
- the cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like.
- digital certificates e.g., X.509 authentication
- the MTI may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network.
- the cryptographic component facilitates the process of "security authorization" whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource.
- the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file.
- a cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like.
- the cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the MTI component to engage in secure transactions if so desired.
- the cryptographic component facilitates the secure accessing of resources on the MTI and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources.
- the cryptographic component communicates with information servers, operating systems, other program components, and/or the like.
- the cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.
- the MTI database component 819 may be embodied in a database and its stored data.
- the database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data.
- the database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase.
- Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys.
- Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the "one" side of a one-to-many relationship.
- the MTI database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files.
- an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like.
- Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of capabilities encapsulated within a given object. If the MTI database is implemented as a data- structure, the use of the MTI database 819 may be integrated into another component such as the MTI component 835. Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated.
- the database component 819 includes several tables 8i9a-j.
- a Users table 819a may include fields such as, but not limited to: user_id, ssn, dob, first_name, last_name, age, state, address_firstline, address_secondline, zipcode, devices_list, contact_info, contact_type, alt_contact_info, alt_contact_type, and/or the like.
- the Users table may support and/or track multiple entity accounts on a MTI.
- a Devices table 819b may include fields such as, but not limited to: device_ID, device_name, device_IP, device_MAC, device_type, device_model, device_version, device_OS, device_apps_list, device_securekey, and/or the like.
- An Apps table 819c may include fields such as, but not limited to: app_ID, app_name, app_type, app_dependencies, and/or the like.
- a Gestures table 8i9d may include fields such as, but not limited to: gesture_id, gesture_name, gesture_touch_group_definition, gesture_timing_sequence, gesture_enabled_flag, gesture_settings_list, gesture_settings_values, and/or the like.
- An Input Devices table 8i9e may include fields such as, but not limited to: device_ID, device_name, device_IP, device_MAC, device_type, device_model, device_version, device_OS, device_apps_list, device_securekey, and/or the like.
- a Commands table 8i9f may include fields such as, but not limited to: command_id, command_name, command_syntax, command_compiler, command_inputs, command_exceptions_list, command_gesture_trigger, and/or the like.
- a Sensors table 8i9g may include fields such as, but not limited to: sensor_id, sensor_name, sensor_type, last_calibrated, sensor_data_rate, sensor_data_format, sensor_data_error_estimate, sensor_trigger_type, sensor_trigger_condition, sensor_burst_enable_flag, sensor_continuous_enable_flag, and/or the like.
- a Calibration Data table 819I1 may include fields such as, but not limited to: calibration_id, calibration_type, calibration_device_applicable, calibration_variables_list, calibration_variables_values, and/or the like.
- a Thresholds table 8191 may include fields such as, but not limited to: threshold_id, threshold_name, threshold_type, threshold_dynamic_parameter, threshold_value, threshold_delta, threshold_last_update, threshold_calibrated_flag, and/or the like.
- a Touch History table 8i9j may include fields such as, but not limited to: timestamp, user_id, user_app_id, user_device_id, user_gesture_id, user_command_id, and/or the like.
- the MTI database may interact with other database systems. For example, employing a distributed database system, queries and data access by search MTI component may treat the combination of the MTI database, an integrated data security layer database as a single database entity.
- user programs may contain various user interface primitives, which may serve to update the MTI.
- various accounts may require custom database tables depending upon the environments and the types of clients the MTI may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables).
- configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 8i9a-j.
- the MTI may be configured to keep track of various settings, inputs, and parameters via database controllers.
- the MTI database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MTI database communicates with the MTI component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data. 1 The MTIs
- the MTI component 835 is a stored program component that is executed
- the MTI component incorporates any and/or all
- the MTI component may transform multi-user, multi-modal touchscreen
- the MTI component 835 takes
- 10 inputs e.g., touch input 401; prior touch input sets 409; user commands 413, 416;
- 11 modified user commands 420 light intensity signal 501; touch IDs, location coordinates
- MTI components e.g., MTP 841;
- TCD 842; TTI 843; TGR 844; and/or the like into outputs (e.g., executed user
- the MTI component enabling access of information between nodes may
- mapping tools procedural and object oriented development tools, PERL, PHP, Python,
- the MTI server employs a cryptographic server to encrypt and decrypt communications.
- the MTI component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the MTI component communicates with the MTI database, operating systems, other program components, and/or the like.
- the MTI may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Distributed MTIs
- any of the MTI node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment.
- the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion.
- the component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.
- the configuration of the MTI controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra- application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like.
- data referencing e.g., pointers
- internal messaging e.g., object instance variable communication, shared memory space, variable passing, and/or the like.
- component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RMI), SOAP, process pipes, shared files, and/or the like.
- API Application Program Interfaces
- D Distributed) Component Object Model
- CORBA Common Object Request Broker Architecture
- JSON JavaScript Object Notation
- RMI Remote Method Invocation
- SOAP process pipes, shared files, and/or the like.
- Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar.
- a grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components.
- a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.:
- parsing mechanism may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data.
- inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data.
- parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment.
- the MTI controller may be executing a PHP script implementing a Secure Sockets Layer ("SSL") socket server via the information server, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format.
- the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language ("SQL").
- SQL Structured Query Language
- $address 1 192.168.0.100 ' ;
- socket_bind ($sock, $address, $port) or die ( 'Could not bind to address');
- $client socket_accept ($sock) ; // read input data from client device in 1024 byte blocks until end of message do ⁇
- $obj j son_decode ( $data, true) ; // store input data in a database
- MTI Mobility Management Entities
- database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like various embodiments of the MTI may be implemented that enable a great deal of flexibility and customization.
- aspects of the MTI may be adapted for 3D immersion systems, virtual reality experiences, office productivity suites, and/or the like. While various embodiments and discussions of the MTI have been directed to human-computer interaction, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
- Position Input By Displaying (AREA)
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201280008070.0A CN103534674A (en) | 2011-02-08 | 2012-02-08 | Multimodal touchscreen interaction apparatuses, methods and systems |
KR1020137023873A KR20140024854A (en) | 2011-02-08 | 2012-02-08 | Multimodal touchscreen interaction apparatuses, methods and systems |
EP12744926.2A EP2673698A1 (en) | 2011-02-08 | 2012-02-08 | Multimodal touchscreen interaction apparatuses, methods and systems |
AU2012214445A AU2012214445A1 (en) | 2011-02-08 | 2012-02-08 | Multimodal touchscreen interaction apparatuses, methods and systems |
CA2826390A CA2826390A1 (en) | 2011-02-08 | 2012-02-08 | Multimodal touchscreen interaction apparatuses, methods and systems |
JP2013552739A JP2014507726A (en) | 2011-02-08 | 2012-02-08 | Multimodal touch screen interaction apparatus, method and system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161440591P | 2011-02-08 | 2011-02-08 | |
US61/440,591 | 2011-02-08 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012109368A1 true WO2012109368A1 (en) | 2012-08-16 |
Family
ID=46638946
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2012/024350 WO2012109368A1 (en) | 2011-02-08 | 2012-02-08 | Multimodal touchscreen interaction apparatuses, methods and systems |
Country Status (8)
Country | Link |
---|---|
US (1) | US20120274583A1 (en) |
EP (1) | EP2673698A1 (en) |
JP (1) | JP2014507726A (en) |
KR (1) | KR20140024854A (en) |
CN (1) | CN103534674A (en) |
AU (1) | AU2012214445A1 (en) |
CA (1) | CA2826390A1 (en) |
WO (1) | WO2012109368A1 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9310929B2 (en) | 2014-06-06 | 2016-04-12 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Unlocking touch screen devices |
JP2016517991A (en) * | 2013-05-07 | 2016-06-20 | ノーム ザタロブスキ、ヨーニ | Personalized and customizable smart browser |
US9596319B2 (en) | 2013-11-13 | 2017-03-14 | T1V, Inc. | Simultaneous input system for web browsers and other applications |
EP3350681A4 (en) * | 2015-09-16 | 2018-10-10 | Samsung Electronics Co., Ltd. | Electromagnetic interference signal detection |
JP2018160265A (en) * | 2014-01-21 | 2018-10-11 | セイコーエプソン株式会社 | Position detection system, and control method of position detection system |
US10181218B1 (en) | 2016-02-17 | 2019-01-15 | Steelcase Inc. | Virtual affordance sales tool |
US10182210B1 (en) | 2016-12-15 | 2019-01-15 | Steelcase Inc. | Systems and methods for implementing augmented reality and/or virtual reality |
US10318090B2 (en) | 2013-08-13 | 2019-06-11 | Samsung Electronics Company, Ltd. | Interaction sensing |
US10404938B1 (en) | 2015-12-22 | 2019-09-03 | Steelcase Inc. | Virtual world method and system for affecting mind state |
Families Citing this family (71)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI386656B (en) * | 2009-07-02 | 2013-02-21 | Novatek Microelectronics Corp | Capacitance measurement circuit and method |
US9471192B2 (en) | 2011-05-23 | 2016-10-18 | Haworth, Inc. | Region dynamics for digital whiteboard |
US20140055400A1 (en) | 2011-05-23 | 2014-02-27 | Haworth, Inc. | Digital workspace ergonomics apparatuses, methods and systems |
EP2715490B1 (en) | 2011-05-23 | 2018-07-11 | Haworth, Inc. | Digital whiteboard collaboration apparatuses, methods and systems |
US9465434B2 (en) | 2011-05-23 | 2016-10-11 | Haworth, Inc. | Toolbar dynamics for digital whiteboard |
CN109582180A (en) | 2011-10-18 | 2019-04-05 | 卡内基梅隆大学 | Method and apparatus for the touch event on touch sensitive surface of classifying |
KR101493558B1 (en) * | 2011-12-22 | 2015-02-16 | 엘지디스플레이 주식회사 | Touch sensor integrated type display and method for transmitting touch coordinates data thereof |
US9479548B2 (en) | 2012-05-23 | 2016-10-25 | Haworth, Inc. | Collaboration system with whiteboard access to global collaboration data |
US9479549B2 (en) | 2012-05-23 | 2016-10-25 | Haworth, Inc. | Collaboration system with whiteboard with federated display |
TWI462033B (en) * | 2012-11-02 | 2014-11-21 | Wistron Corp | Touch system and method of making a drawing thereon |
WO2014106910A1 (en) * | 2013-01-04 | 2014-07-10 | 株式会社ユビキタスエンターテインメント | Information processing device and information input control program |
US9836154B2 (en) * | 2013-01-24 | 2017-12-05 | Nook Digital, Llc | Selective touch scan area and reporting techniques |
US11861561B2 (en) | 2013-02-04 | 2024-01-02 | Haworth, Inc. | Collaboration system including a spatial event map |
US10304037B2 (en) | 2013-02-04 | 2019-05-28 | Haworth, Inc. | Collaboration system including a spatial event map |
US9671953B2 (en) * | 2013-03-04 | 2017-06-06 | The United States Of America As Represented By The Secretary Of The Army | Systems and methods using drawings which incorporate biometric data as security information |
KR20140114766A (en) * | 2013-03-19 | 2014-09-29 | 퀵소 코 | Method and device for sensing touch inputs |
US9612689B2 (en) | 2015-02-02 | 2017-04-04 | Qeexo, Co. | Method and apparatus for classifying a touch event on a touchscreen as related to one of multiple function generating interaction layers and activating a function in the selected interaction layer |
US9013452B2 (en) | 2013-03-25 | 2015-04-21 | Qeexo, Co. | Method and system for activating different interactive functions using different types of finger contacts |
ES1079832Y (en) * | 2013-05-08 | 2013-08-22 | Gutierrez Santiago Fornet | TOUCH SCREEN IDENTIFIER |
US9176614B2 (en) | 2013-05-28 | 2015-11-03 | Google Technology Holdings LLC | Adapative sensing component resolution based on touch location authentication |
US20150006385A1 (en) * | 2013-06-28 | 2015-01-01 | Tejas Arvindbhai Shah | Express transactions on a mobile device |
US10073578B2 (en) | 2013-08-13 | 2018-09-11 | Samsung Electronics Company, Ltd | Electromagnetic interference signal detection |
US10101869B2 (en) * | 2013-08-13 | 2018-10-16 | Samsung Electronics Company, Ltd. | Identifying device associated with touch event |
US10141929B2 (en) | 2013-08-13 | 2018-11-27 | Samsung Electronics Company, Ltd. | Processing electromagnetic interference signal using machine learning |
JP6349838B2 (en) * | 2014-01-21 | 2018-07-04 | セイコーエプソン株式会社 | POSITION DETECTION DEVICE, POSITION DETECTION SYSTEM, AND POSITION DETECTION DEVICE CONTROL METHOD |
JP6398248B2 (en) | 2014-01-21 | 2018-10-03 | セイコーエプソン株式会社 | Position detection system and method for controlling position detection system |
JP6201824B2 (en) * | 2014-03-05 | 2017-09-27 | 株式会社デンソー | Operating device |
KR102265143B1 (en) * | 2014-05-16 | 2021-06-15 | 삼성전자주식회사 | Apparatus and method for processing input |
WO2015181163A1 (en) * | 2014-05-28 | 2015-12-03 | Thomson Licensing | Method and system for touch input |
US9558455B2 (en) * | 2014-07-11 | 2017-01-31 | Microsoft Technology Licensing, Llc | Touch classification |
US9329715B2 (en) | 2014-09-11 | 2016-05-03 | Qeexo, Co. | Method and apparatus for differentiating touch screen users based on touch event analysis |
US11619983B2 (en) | 2014-09-15 | 2023-04-04 | Qeexo, Co. | Method and apparatus for resolving touch screen ambiguities |
US10606417B2 (en) | 2014-09-24 | 2020-03-31 | Qeexo, Co. | Method for improving accuracy of touch screen event analysis by use of spatiotemporal touch patterns |
US10282024B2 (en) | 2014-09-25 | 2019-05-07 | Qeexo, Co. | Classifying contacts or associations with a touch sensitive device |
CN104333962A (en) * | 2014-11-28 | 2015-02-04 | 浙江晶日照明科技有限公司 | Intelligent LED (light emitting diode) lamp as well as man-machine interactive system and man-machine interactive method thereof |
US9811256B2 (en) | 2015-01-14 | 2017-11-07 | International Business Machines Corporation | Touch screen tactile gestures for data manipulation |
US20160210038A1 (en) * | 2015-01-21 | 2016-07-21 | Microsoft Technology Licensing, Llc | Electronic inking |
US10031638B2 (en) * | 2015-02-10 | 2018-07-24 | Etter Studio Ltd. | Multi-touch GUI featuring directional compression and expansion of graphical content |
US9977519B2 (en) * | 2015-02-25 | 2018-05-22 | Synaptics Incorporated | Active pen with bidirectional communication |
EP3292524B1 (en) | 2015-05-06 | 2020-07-08 | Haworth, Inc. | Virtual workspace viewport follow mode in collaboration systems |
US10642404B2 (en) | 2015-08-24 | 2020-05-05 | Qeexo, Co. | Touch sensitive device with multi-sensor stream synchronized data |
US20170068414A1 (en) * | 2015-09-09 | 2017-03-09 | Microsoft Technology Licensing, Llc | Controlling a device |
US10481645B2 (en) | 2015-09-11 | 2019-11-19 | Lucan Patent Holdco, LLC | Secondary gesture input mechanism for touchscreen devices |
US10955977B2 (en) * | 2015-11-03 | 2021-03-23 | Microsoft Technology Licensing, Llc | Extender object for multi-modal sensing |
JP6733451B2 (en) * | 2015-12-17 | 2020-07-29 | 株式会社リコー | Coordinate detection system, coordinate detection method, image processing device, and program |
US10317988B2 (en) * | 2016-02-03 | 2019-06-11 | Disney Enterprises, Inc. | Combination gesture game mechanics using multiple devices |
US10255023B2 (en) | 2016-02-12 | 2019-04-09 | Haworth, Inc. | Collaborative electronic whiteboard publication process |
US10545658B2 (en) | 2017-04-25 | 2020-01-28 | Haworth, Inc. | Object processing and selection gestures for forming relationships among objects in a collaboration system |
US20200348817A1 (en) * | 2017-08-23 | 2020-11-05 | Flatfrog Laboratories Ab | Pen touch matching |
US11126258B2 (en) * | 2017-10-14 | 2021-09-21 | Qualcomm Incorporated | Managing and mapping multi-sided touch |
US12019850B2 (en) | 2017-10-23 | 2024-06-25 | Haworth, Inc. | Collaboration system including markers identifying multiple canvases in multiple shared virtual workspaces |
US11126325B2 (en) | 2017-10-23 | 2021-09-21 | Haworth, Inc. | Virtual workspace including shared viewport markers in a collaboration system |
US11934637B2 (en) | 2017-10-23 | 2024-03-19 | Haworth, Inc. | Collaboration system including markers identifying multiple canvases in multiple shared virtual workspaces |
JP2019159865A (en) * | 2018-03-14 | 2019-09-19 | 富士通株式会社 | Control program, control method, and information processing apparatus |
WO2019236764A1 (en) * | 2018-06-05 | 2019-12-12 | Google Llc | Confidence-based application-specific user interactions |
US11009989B2 (en) | 2018-08-21 | 2021-05-18 | Qeexo, Co. | Recognizing and rejecting unintentional touch events associated with a touch sensitive device |
CN110874200B (en) * | 2018-08-29 | 2023-05-26 | 斑马智行网络(香港)有限公司 | Interactive method, device, storage medium and operating system |
US10845985B2 (en) | 2018-09-14 | 2020-11-24 | Sigmasense, Llc. | Identification in touch systems |
CN109271069B (en) * | 2018-10-29 | 2021-06-29 | 深圳市德明利技术股份有限公司 | Secondary area searching method based on capacitive touch, touch device and mobile terminal |
WO2020176517A1 (en) | 2019-02-25 | 2020-09-03 | Haworth, Inc. | Gesture based workflows in a collaboration system |
JP2022527280A (en) * | 2019-03-28 | 2022-06-01 | ジーエイチエスピー・インコーポレイテッド | Interactive kitchen display |
US10942603B2 (en) | 2019-05-06 | 2021-03-09 | Qeexo, Co. | Managing activity states of an application processor in relation to touch or hover interactions with a touch sensitive device |
US11164508B2 (en) * | 2019-05-16 | 2021-11-02 | Asustek Computer Inc. | Electronic device |
US11231815B2 (en) | 2019-06-28 | 2022-01-25 | Qeexo, Co. | Detecting object proximity using touch sensitive surface sensing and ultrasonic sensing |
US11592423B2 (en) | 2020-01-29 | 2023-02-28 | Qeexo, Co. | Adaptive ultrasonic sensing techniques and systems to mitigate interference |
WO2021162602A1 (en) | 2020-02-10 | 2021-08-19 | Flatfrog Laboratories Ab | Improved touch-sensing apparatus |
US11212127B2 (en) | 2020-05-07 | 2021-12-28 | Haworth, Inc. | Digital workspace sharing over one or more display clients and authorization protocols for collaboration systems |
US11750672B2 (en) | 2020-05-07 | 2023-09-05 | Haworth, Inc. | Digital workspace sharing over one or more display clients in proximity of a main client |
US11790820B2 (en) * | 2021-06-14 | 2023-10-17 | Samsung Electronics Co., Ltd. | Electronic device including rollable display rolled into circle |
KR20230023158A (en) * | 2021-08-10 | 2023-02-17 | 삼성전자주식회사 | Electronic device and the method for electronic pen operation |
CN115268757A (en) * | 2022-07-19 | 2022-11-01 | 武汉乐庭软件技术有限公司 | Gesture interaction recognition system on picture system based on touch screen |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060012580A1 (en) * | 2004-07-15 | 2006-01-19 | N-Trig Ltd. | Automatic switching for a dual mode digitizer |
US20090128516A1 (en) * | 2007-11-07 | 2009-05-21 | N-Trig Ltd. | Multi-point detection on a single-point detection digitizer |
US20100309148A1 (en) * | 2009-06-07 | 2010-12-09 | Christopher Brian Fleizach | Devices, Methods, and Graphical User Interfaces for Accessibility Using a Touch-Sensitive Surface |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4686332A (en) * | 1986-06-26 | 1987-08-11 | International Business Machines Corporation | Combined finger touch and stylus detection system for use on the viewing surface of a visual display device |
US8479122B2 (en) * | 2004-07-30 | 2013-07-02 | Apple Inc. | Gestures for touch sensitive input devices |
US8125459B2 (en) * | 2007-10-01 | 2012-02-28 | Igt | Multi-user input systems and processing techniques for serving multiple users |
WO2004070396A2 (en) * | 2003-02-10 | 2004-08-19 | N-Trig Ltd. | Touch detection for a digitizer |
CN101057271A (en) * | 2004-07-15 | 2007-10-17 | N-Trig有限公司 | Automatic switching for a dual mode digitizer |
US7728823B2 (en) * | 2004-09-24 | 2010-06-01 | Apple Inc. | System and method for processing raw data of track pad device |
US7877707B2 (en) * | 2007-01-06 | 2011-01-25 | Apple Inc. | Detecting and interpreting real-world and security gestures on touch and hover sensitive devices |
WO2008138030A1 (en) * | 2007-05-11 | 2008-11-20 | Rpo Pty Limited | User-defined enablement protocol |
US9335869B2 (en) * | 2007-10-01 | 2016-05-10 | Igt | Method and apparatus for detecting lift off on a touchscreen |
AR064377A1 (en) * | 2007-12-17 | 2009-04-01 | Rovere Victor Manuel Suarez | DEVICE FOR SENSING MULTIPLE CONTACT AREAS AGAINST OBJECTS SIMULTANEOUSLY |
US20100205190A1 (en) * | 2009-02-09 | 2010-08-12 | Microsoft Corporation | Surface-based collaborative search |
US8269511B2 (en) * | 2009-09-08 | 2012-09-18 | Synaptics Incorporated | Sensing and defining an input object |
US20120019453A1 (en) * | 2010-07-26 | 2012-01-26 | Wayne Carl Westerman | Motion continuation of touch input |
-
2012
- 2012-02-08 CA CA2826390A patent/CA2826390A1/en not_active Abandoned
- 2012-02-08 US US13/369,137 patent/US20120274583A1/en not_active Abandoned
- 2012-02-08 JP JP2013552739A patent/JP2014507726A/en active Pending
- 2012-02-08 AU AU2012214445A patent/AU2012214445A1/en not_active Abandoned
- 2012-02-08 CN CN201280008070.0A patent/CN103534674A/en active Pending
- 2012-02-08 EP EP12744926.2A patent/EP2673698A1/en not_active Withdrawn
- 2012-02-08 WO PCT/US2012/024350 patent/WO2012109368A1/en active Application Filing
- 2012-02-08 KR KR1020137023873A patent/KR20140024854A/en not_active Application Discontinuation
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060012580A1 (en) * | 2004-07-15 | 2006-01-19 | N-Trig Ltd. | Automatic switching for a dual mode digitizer |
US20090128516A1 (en) * | 2007-11-07 | 2009-05-21 | N-Trig Ltd. | Multi-point detection on a single-point detection digitizer |
US20100309148A1 (en) * | 2009-06-07 | 2010-12-09 | Christopher Brian Fleizach | Devices, Methods, and Graphical User Interfaces for Accessibility Using a Touch-Sensitive Surface |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016517991A (en) * | 2013-05-07 | 2016-06-20 | ノーム ザタロブスキ、ヨーニ | Personalized and customizable smart browser |
US10318090B2 (en) | 2013-08-13 | 2019-06-11 | Samsung Electronics Company, Ltd. | Interaction sensing |
US9596319B2 (en) | 2013-11-13 | 2017-03-14 | T1V, Inc. | Simultaneous input system for web browsers and other applications |
US11570222B2 (en) | 2013-11-13 | 2023-01-31 | T1V, Inc. | Simultaneous input system for web browsers and other applications |
US10447744B2 (en) | 2013-11-13 | 2019-10-15 | TIV, Inc. | Simultaneous input system for web browsers and other applications |
JP2018160265A (en) * | 2014-01-21 | 2018-10-11 | セイコーエプソン株式会社 | Position detection system, and control method of position detection system |
US9310929B2 (en) | 2014-06-06 | 2016-04-12 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Unlocking touch screen devices |
EP3350681A4 (en) * | 2015-09-16 | 2018-10-10 | Samsung Electronics Co., Ltd. | Electromagnetic interference signal detection |
US11006073B1 (en) | 2015-12-22 | 2021-05-11 | Steelcase Inc. | Virtual world method and system for affecting mind state |
US11856326B1 (en) | 2015-12-22 | 2023-12-26 | Steelcase Inc. | Virtual world method and system for affecting mind state |
US10404938B1 (en) | 2015-12-22 | 2019-09-03 | Steelcase Inc. | Virtual world method and system for affecting mind state |
US11490051B1 (en) | 2015-12-22 | 2022-11-01 | Steelcase Inc. | Virtual world method and system for affecting mind state |
US10614625B1 (en) | 2016-02-17 | 2020-04-07 | Steelcase, Inc. | Virtual affordance sales tool |
US10984597B1 (en) | 2016-02-17 | 2021-04-20 | Steelcase Inc. | Virtual affordance sales tool |
US11222469B1 (en) | 2016-02-17 | 2022-01-11 | Steelcase Inc. | Virtual affordance sales tool |
US11521355B1 (en) | 2016-02-17 | 2022-12-06 | Steelcase Inc. | Virtual affordance sales tool |
US10181218B1 (en) | 2016-02-17 | 2019-01-15 | Steelcase Inc. | Virtual affordance sales tool |
US11178360B1 (en) | 2016-12-15 | 2021-11-16 | Steelcase Inc. | Systems and methods for implementing augmented reality and/or virtual reality |
US10659733B1 (en) | 2016-12-15 | 2020-05-19 | Steelcase Inc. | Systems and methods for implementing augmented reality and/or virtual reality |
US10182210B1 (en) | 2016-12-15 | 2019-01-15 | Steelcase Inc. | Systems and methods for implementing augmented reality and/or virtual reality |
US11863907B1 (en) | 2016-12-15 | 2024-01-02 | Steelcase Inc. | Systems and methods for implementing augmented reality and/or virtual reality |
Also Published As
Publication number | Publication date |
---|---|
JP2014507726A (en) | 2014-03-27 |
CA2826390A1 (en) | 2012-08-16 |
CN103534674A (en) | 2014-01-22 |
AU2012214445A1 (en) | 2013-08-01 |
EP2673698A1 (en) | 2013-12-18 |
US20120274583A1 (en) | 2012-11-01 |
KR20140024854A (en) | 2014-03-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20120274583A1 (en) | Multimodal Touchscreen Interaction Apparatuses, Methods and Systems | |
US11550399B2 (en) | Sharing across environments | |
US20170255450A1 (en) | Spatial cooperative programming language | |
US8446367B2 (en) | Camera-based multi-touch mouse | |
US10809910B2 (en) | Remote touch detection enabled by peripheral device | |
WO2011029055A1 (en) | Apparatuses, methods and systems for a visual query builder | |
US20160139762A1 (en) | Aligning gaze and pointing directions | |
US20140210728A1 (en) | Fingerprint driven profiling | |
TWI552791B (en) | Laser diode modes | |
KR20200100671A (en) | Data processing method, terminal device, and data processing system | |
WO2021213274A1 (en) | Method and apparatus for preventing false touch of mobile terminal, and computer device and storage medium | |
US20200142582A1 (en) | Disambiguating gesture input types using multiple heatmaps | |
WO2022000959A1 (en) | Captcha method and apparatus, device, and storage medium | |
WO2016131364A1 (en) | Multi-touch remote control method | |
US20140104179A1 (en) | Keyboard Modification to Increase Typing Speed by Gesturing Next Character | |
US20180253181A1 (en) | Replay of Recorded Touch Input Data | |
US10175825B2 (en) | Information processing apparatus, information processing method, and program for determining contact on the basis of a change in color of an image | |
CN109710075B (en) | Method and device for displaying content in VR scene | |
US20170123623A1 (en) | Terminating computing applications using a gesture | |
CN107544695B (en) | Input device | |
KR20150003694A (en) | Touch sensing device utilizing assist device and method for operating the same | |
CN111339339A (en) | Annotation method and system for user comment photos, computer storage medium and terminal | |
Wang et al. | Converting a display screen into a touchscreen | |
TW201539303A (en) | Electronic apparatus with virtual input feature | |
KR20140113064A (en) | Touch sensing device utilizing assist device and method for operating the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12744926 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2012214445 Country of ref document: AU Date of ref document: 20120208 Kind code of ref document: A Ref document number: 2826390 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2013552739 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012744926 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20137023873 Country of ref document: KR Kind code of ref document: A |