In recent years, portable computing and communication devices have inundated the market place. Competition has become fierce among manufacturers as they compete for the attention of consumers as well as their dollars. Thus, it is not uncommon for the average consumer to own a variety of portable devices such as a cell phone and a personal digital assistant (PDA) made from the same or different manufacturers or brands. Traditionally, different computing devices are not made to communicate with each other—especially if manufactured by or sold under different brands. For example, a Brand Q PDA typically cannot “talk” to a Brand Z PDA. Similarly, Brand Q PDA cannot interact with a Brand Z smartphone. For most users, this can cause many inconveniences and result in large amounts of wasted time because information must be entered separately into each device.
Associating peripheral input/output devices such as wireless keyboards and printers with a particular portable device can involve complex and cumbersome pairing procedures as well. For example, Bluetooth technology provides one conventional technique for pairing a device with a peripheral input/output tool. Unfortunately, Bluetooth only allows for fixed pairings. When a user of the tool is changed, the pairing process must be re-done. For instance, imagine that TOM's Bluetooth-enabled keyboard is paired with his laptop computer. TOM lends MARY his keyboard for her use with her tablet PC. When MARY is finished with the keyboard, she returns it to TOM. In this brief scenario, the Bluetooth-enabled tool requires the pairing process to be performed 3 separate times: twice by TOM and once by MARY.
In addition to the lack or inability of communication between different devices, technology, in general, as well as consumers have converged on the desire and/or need for smaller and smaller devices. Unfortunately, the smaller the device, the smaller the display area or user interface. Consequently, the amount of information which can be viewed at once or readily viewed at all may be substantially reduced or non-existent. For instance, personalizing the device or mere general use of the device can be time-consuming and frustrating for the user and result in an overall poor user experience.
The following presents a simplified summary in order to provide a basic understanding of some aspects of the systems and/or methods discussed herein. This summary is not an extensive overview of the systems and/or methods discussed herein. It is not intended to identify key/critical elements or to delineate the scope of such systems and/or methods. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
The subject application relates to a system(s) and/or methodology that facilitate operation of at least one mobile device and/or interaction between multiple mobile devices via an interactive surface. In particular, one or more mobile devices can connect to the interactive surface. Once connected, the one or more mobile devices can make use of the expanded display space of the interactive surface, thus making it much easier for the user to operate, customize, or manipulate data on the mobile device. Although such operations are particularly well suited to a horizontal or slightly angled interactive surface, which allows placing and letting go of multiple devices on the surface, similar interactions could be supported on a vertical or otherwise oriented surface by touching device(s) to the surface and then holding them there or putting them down elsewhere.
According to a first approach, for example, a mobile device can establish a wireless connection with the interactive surface. The interactive surface comprises a display space that is substantially larger than the display of the mobile device. Thus, when connected thereto, the display of the mobile device can be visualized on an expanded scale via the interactive surface. A variety of operations that may otherwise be performed directly on the mobile device with at least some difficulty can now be performed with greater ease via the interactive surface. Moreover, the interactive surface component acts as a portal to the mobile device display and/or data and hence, the user maintains control of the mobile device and its contents. To further enhance the user's overall experience, the interactive surface can be touch-sensitive and/or include a touch-sensitive pad and/or one or more other input mechanisms (e.g., keyboard, mouse, stylus, etc.) to facilitate navigation of data displayed on the interactive surface as well as on the mobile device.
Connection with the interactive surface can be accomplished in one or more different manners. For instance, the mobile device can be placed on the surface. Using a visual pattern located on the mobile device, the surface can read the pattern and identify the type and/or name of the device and call up the appropriate protocol(s) in order to open or create the proper channels to communicate and interact with the device. Alternatively, the visual pattern can be read from the mobile device when the mobile device is located within a physical proximity of the interactive surface. In either case, the connection can be established automatically or at the discretion of the user by way of employing one or more controls or buttons on the interactive surface. For example, when the presence of a mobile device is detected, a dialogue box may appear and ask the user whether a connection is desired—to which the user must respond before the connection is established. Disconnection can be accomplished in a similar manner. That is, the device may be removed from the surface or explicit controls or commands may be required to disconnect the mobile device from the surface.
Non-visual patterns or codes associated with the device can be employed as well to identify when the device is on or near the surface. Examples of such non-visual patterns or codes include RFID, short range wireless radio, capacitive coupling between device and the interactive surface, and an optical connection (e.g., blinking IR LED on bottom of mobile device).
According to a second approach, multiple mobile devices can communicate and/or interact with each other via the interactive surface. Initially, each device can establish a connection with the interactive surface. Once connected to the surface, the devices can share data and/or otherwise communicate with one another through the interactive surface. This can be particularly advantageous for sharing information among different types of mobile devices whether owned by either a single user or multiple users. In some cases, maintaining privacy of some information may be a concern for the user. To mitigate this concern, the user can control which information is openly displayed on the interactive surface and which information is concealed or hidden from “public” view.
In addition to providing enhanced input/output resources for mobile devices, the interactive surface can also provide temporary or long-term data storage for mobile devices, most of which tend to have limited storage capacities. Furthermore, the interactive surface allows data or objects such as files, documents, and photographs to be moved or copied between one or more mobile devices. The interactive surface can also permit background monitoring of various tasks or program applications such as email, file transfers, program updates, and the like while the user is more actively involved in another task or application. Moreover, the interactive surface provides a rich user interface for mobile devices that are characteristically deficient in display capabilities and augments the usability and visibility of such devices.
To the accomplishment of the foregoing and related ends, certain illustrative aspects of the invention are described herein in connection with the following description and the annexed drawings. These aspects are indicative, however, of but a few of the various ways in which the principles of the invention may be employed and the subject invention is intended to include all such aspects and their equivalents. Other advantages and novel features of the invention may become apparent from the following detailed description of the invention when considered in conjunction with the drawings.
The subject systems and/or methods are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the systems and/or methods. It may be evident, however, that the subject systems and/or methods may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing them.
As used herein, the terms “component” and “system” are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
The subject systems and/or methods can incorporate various inference schemes and/or techniques in connection with recognizing and identifying mobile devices and ritualistic or routine interactions there-between. For example, an exemplary interactive surface component can learn to perform particular actions or display certain information when one or more particular mobile devices connect to the surface component. In practice, for instance, imagine that when a smartphone device named BOBSTAR establishes a connection to the surface, the surface is trained to automatically show the address book in its display space. Similarly, when PDA-1 and PDA-101 reconnect to the interactive surface component, their state of activity can resume from their previous connection.
As used herein, the term “inference” refers generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
Referring now to
The mobile device 110 often lacks adequate display space or input capabilities. However, when the mobile device 110 establishes a connection (e.g., WiFi, infrared, etc.) with the interactive surface component 120, the display space of the interactive surface component 120 can act as an additional input/output resource for the device 110. In particular, information displayed on the mobile device can be mirrored and enhanced and/or enlarged on the surface component 120. As a result, a user can more readily and with greater ease enter and/or manipulate information on his/her mobile device 110 by way of the larger display space and additional input capabilities of the surface component 120.
Connection to the surface component 120 can be established in a wireless manner such as by contacting the device to at least a portion of the surface component 120 or by placing the device 110 on the surface component 120. When the appropriate contact is made, the surface component 120 can read an identification marker on the device 110 to identify the type and/or name of the device 110. The identification marker can be a barcode, an RFID tag, or some other visual pattern or code unique to the particular mobile device that can be read by the surface component 120.
As demonstrated in the later figures, a PDA or tablet PC placed on the surface 120, for example, can use the surface 120 as a personal portal into the data displayed on the PDA or tablet PC. This portal provides an additional parallel plane of interaction for the user. When multiple devices and multiple users are connected to the surface component 120, the position and orientation of each device 110 can be sensed and used to determine where each different user is located (e.g., sitting) around the surface 120. In practice, for instance, the position and orientation of the device's identification marker can be employed to determine the device's overall position and orientation on the surface relative to other devices located thereon.
Referring now to
When a plurality of mobile devices 210 are connected to the interactive surface component 220 and interaction between at least two devices 210 is desired, an association component 240 can be employed to facilitate the passage of data from one device to another via the interactive surface component 220. More specifically, the association component 240 can group related devices together or suggest such groupings to the user(s). The relatedness of devices can be determined in part by examining their spatial relationships and physical proximity to each other. For example, devices belonging to the same group are more likely positioned closer together. It should be appreciated that the at least two devices can be different, alike, or even identical.
The association component 240 can also be employed to couple or link at least one mobile device 210 with one or more input/output components 250 also connected to the interactive surface component 220. Examples of input/output components 250 include but are not limited to a keyboard, mouse, stylus, pen, and/or printer. Because most if not all mobile devices have limited input capabilities, a user may desire to make use of the richer and larger display space of the interactive surface component to enter data into the device. Therefore, the user may desire to connect a wireless keyboard to the interactive surface component 220. If multiple devices are connected to the interactive surface component 220, the keyboard can be readily associated and/or employed with such devices without needing to perform complicated pairing procedures each time the device or user changes. To mitigate security concerns when using such input components, on-screen buttons or controls located on the interactive surface component 220, and/or on the devices themselves, may be utilized to indicate which device 210 is currently linked to the respective input component 260.
Referring now to
Next, imagine that a mouse, keyboard, and PDA are all placed on the interactive surface component 300 and all face the same direction. Based on the alignment of their primary orientation vectors, these three devices can be bound together and treated as a group. As a result, the user can have high-bandwidth text entry on his/her PDA.
When multiple devices are connected to the interactive surface component, data can be shared or moved between such devices by way of an object sharing component 350. For example, data such as files, documents, or photographs can be moved or copied to the interactive surface from the first device 310. Using a navigation component 360 such as on-screen controls (e.g., touch-sensitive surface, command buttons, etc.), the data can be moved or copied to the second device 320 as desired by the user. Alternatively, the data can be stored on the interactive surface component 300 for later retrieval and use.
In general, the navigation component 360 can assist the user in viewing and manipulating the relevant data on the interactive surface component 300. That is, the user can navigate through information displayed on the interactive surface component as if he/she were navigating through the same information on the mobile device to create a seamless and transparent experience for the user.
Turning now to the next several figures, exemplary views of the interactive surface component interfacing with one or more mobile devices as described hereinabove are illustrated. For instance,
In practice, for example, a user could place a cell phone on the interactive surface component (display space). When a connection is established to the surface component, the cell phone could automatically be transitioned to speakerphone mode for the duration of the connection or until the user turns it off or manually switches the mode. The display space could then show a list of contacts with a picture for each contact whereby touching a picture initiates a call or another action specific to that person (e.g., opening a shared web browser on the interactive surface).
As another example, the user could establish a connection between his/her watch and the interactive surface component. When connected, the surface display space can show various forms to the user to customize the information which the watch intends to display. Thus, the user can achieve customization of his/her watch using the enhanced controls of the interactive surface component rather than dealing with an impoverished display and a paucity of buttons on the watch to achieve the same task.
It should be appreciated that the view of information in the surface display space can change to present various options for interaction with the device. Therefore, the information in view in the surface display space may not always mirror the mobile device display. When the device is removed or picked up from the surface component, the connection can be severed automatically as a result and the display on the mobile device can stay the same or return to a default or standby appearance. In some instances, the user can be asked to verify whether disconnection is desired before the connection is severed.
Moving on to
Objects can be moved or copied to the device 500 from “the interactive surface” 410 or moved or copied from the device 500 to the surface 410 via the device's clipboard 602. In
The diagram 800 in
At 920, a second device (W) 904 is put down on the interactive surface (display space 410). A connection between the two devices (902 and 904) can be hypothesized by showing both cords connected to the connection target 906 (shaded to indicate a connection). The user can touch the target area 906 or some other symbol, icon, or command to connect the devices, or touch and hold it (e.g., target area 906, symbol, icon, command button, etc.) to bring up other options.
At 930, both the first and second devices (902 and 904) are connected to each other. If one of the devices is removed from the interactive surface (display space 410), the connection can be automatically broken. Alternatively, the connection can persist when the second device has been physically removed, as is illustrated at 930. This can allow the user to pick up his/her device and use it as a private display, or even to wander about at some distance from the interactive surface while staying connected to his/her colleagues positioned at the interactive surface. When the second device has been moved some distance away, such as down the hall or to another room, a virtual indication 908 of the connection to the second device W 904 can be shown on the surface, and the second device can communicate with the surface component and/or any other connected devices remotely. The surface can display an “antenna tower” 912 to provide feedback of the ongoing connection, and a connection icon can give local users the option to close the connection to the second device W.
While the second device W 904 is away or interacting remotely, the local screen on W 904 can show similar feedback indicating the connection to the surface (display space 410) (and the first device) as well as the option to close that connection. In addition, the local screen on the device can be manipulated to reflect or clarify any activity occurring on the interactive surface. For instance, points of connection can be displayed on the mobile device to indicate that they are available to the device. A matching connection on the surface (display space 410) could tie directly into that point graphically (on the same side of the display, corner, etc.).
As information is being communicated between devices via the surface, such as between the first and second devices, one or more graphics or graphical illustrations can be employed to visually indicate the status of activity between at least two devices. For example, the connection between any two devices can glow or pulse to depict the flow of data and/or the current state of the connection. This can assist the user(s) in determining the quantity or type of information that has been shared or passed, time remaining to complete the transfer, and/or time required to complete the transfer. Graphics displayed on the interactive surface can also be utilized to terminate, reassign, or add connections between devices. As a result, the user can interact with the relevant connection(s) directly rather than through the various devices.
Turning now to
When multiple devices are present on the interactive surface but communication is only desired with one particular device, the spatial relationship between such devices can assist in identifying the desired device. In practice, for example, imagine that JOHN wants to share pictures with JANE. Their devices as well as 2 others belonging to other users are connected to the interactive surface. To facilitate the exchange of the pictures between only JOHN's and JANE's devices, they can point their devices to face each other. Alternatively, they can orient them in a similar manner and within close proximity of each other. Other variations are possible as well to indicate that communication between only the designated devices is desired. Commands or additional controls associated with the interactive surface may also be employed.
The interactive surface also remembers which devices have previously been placed upon it, and what tasks or files were used among the devices. If the same set of devices is placed on the interactive surface again, the surface may offer to restore the old state of the surface. This allows several colleagues to temporarily stop working on a project, and then return to it later just by placing their same devices on the table. A single user could similarly restore the workspace for a project just by placing a tagged paper folder or electronic device used specifically for that project on the table. For example, placing an MP3 player on the table would bring up the user's music files and web sites he/she had last used for sharing and purchasing music.
Devices on the interactive surface and connected thereto (e.g., the devices of groups 1004, 1006, or 1008) can also operate as storage containers for data and proxies similar to network folders or shares. For instance, a PDA can be a proxy that points to a URL for a network share. In this type of arrangement of devices on the interactive surface, the interactive surface can facilitate visualization of a wireless network.
The interactive surface can also serve as an extended workspace area for a user who desires additional screen real estate. For example, the user can connect his tablet PC to the interactive surface and create a workspace arranged in the surface display space around the tablet PC. The user can use various hand gestures or other navigation controls to bring new documents onto the tablet screen (or remove them from it). This alleviates screen real estate restrictions on the tablet when working with lots of documents. The interactive surface provides a large peripheral view of backburner tasks and programs like email that the user can monitor even when not directly using them.
Mobile devices such as a tablet PC, for instance, can also be placed in a slate mode on the interactive surface to provide an additional horizontal layer. The user can dynamically transition to a vertical surface by flipping up the screen to be perpendicular to the surface. This can be sensed by the surface which can give a separate view that is private. Alternatively or in addition, the surface might switch from an overhead plan view on the tablet PC to a 3D immersive view. To mitigate undesired occlusion of any portion of the display space, the tablet PC can be placed near the edges of the display space.
Various methodologies will now be described via a series of acts. It is to be understood and appreciated that the subject system and/or methodology is not limited by the order of acts, as some acts may, in accordance with the subject application, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with the subject application.
Referring now to
At 1120, the at least one mobile device can be identified by way of its unique visual pattern (e.g., barcode, RFID tag, etc.). Once identified by name and/or device type (make and/or model), the interactive surface component can determine the position and orientation of the mobile device as it rests on its surface and can register the device's user interface and any content appearing thereon at 1130. At 1140, the contents of the mobile device display can be visualized in the display space of the interactive surface component to facilitate transparent user interaction with the interactive surface. In other words, the mobile device display can be mirrored on the larger and richer user interface of the interactive surface component. As a result, the user can interact with his/her mobile device as usual with the assistance of the expanded input/output capabilities of the interactive surface.
Referring now to
At 1230, the interactive surface can project one or more suitable displays specific to the mobile device onto the display space of the interactive surface. For instance, the user or the device itself may have set a default screen to view when initially connected to the interactive surface. At 1240, the interactive surface can provide enhanced customization and/or visualization controls particularly for mobile devices with little or no display capabilities or inadequate input or navigation controls or for users who desire additional workspace. At 1250, the device can be optionally removed from the surface to terminate or end communication and interaction with the interactive surface. Termination can be automatic or can be affirmatively verified by the user before the connection is ended. When transferring or sharing data between the interactive surface and the device, the connection can remain open for the duration of the data exchange and end as soon as the exchange is completed.
In some cases, the device can maintain a virtual presence on the interactive surface and communicate with the interactive surface from a remote location. This can provide users with some flexibility when interacting with the interactive surface so that they do not always need to disconnect and then re-connect if they need to step away from the interactive surface with their device for a brief time. The remote connection can be terminated from either the interactive surface or from the remote device.
Turning now to
At 1350, it can be optionally determined whether some devices can or should be grouped according to their respective spatial arrangements on the interactive surface. For instance, one user may have two mobile devices and a wireless keyboard connected to the interactive surface. The interactive surface can suggest a grouping of these devices to facilitate data sharing and input capabilities. Alternatively, various teams of users involved on the same project may be interacting with the interactive surface. Thus, each team of users can have their devices grouped together to make data sharing more efficient. At 1360, communication and/or interaction between the multiple devices can be performed. Examples of such types of interaction include moving and copying data between devices or groups of devices, viewing data from the devices on the interactive surface, sharing input devices such as a wireless keyboard between different users and for different devices without requiring complex pairing procedures, etc.
In order to provide additional context for various aspects of the subject application,
Generally, however, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular data types. The operating environment 1410 is only one example of a suitable operating environment and is not intended to suggest any limitation as to the scope of use or functionality of the system and/or method. Other well known computer systems, environments, and/or configurations that may be suitable for use with the system and/or method include but are not limited to, personal computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include the above systems or devices, and the like.
With reference to
The system bus 1418 can be any of several types of bus structure(s) including the memory bus or memory controller, a peripheral bus or external bus, and/or a local bus using any variety of available bus architectures including, but not limited to, 11-bit bus, Industrial Standard Architecture (ISA), Micro-Channel Architecture (MCA), Extended ISA (EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Universal Serial Bus (USB), Advanced Graphics Port (AGP), Personal Computer Memory Card International Association bus (PCMCIA), and Small Computer Systems Interface (SCSI).
The system memory 1416 includes volatile memory 1420 and nonvolatile memory 1422. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer 1412, such as during start-up, is stored in nonvolatile memory 1422. By way of illustration, and not limitation, nonvolatile memory 1422 can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory 1420 includes random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).
Computer 1412 also includes removable/nonremovable, volatile/nonvolatile computer storage media.
It is to be appreciated that
A user enters commands or information into the computer 1412 through input device(s) 1436. Input devices 1436 include, but are not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, TV tuner card, digital camera, digital video camera, web camera, and the like. These and other input devices connect to the processing unit 1414 through the system bus 1418 via interface port(s) 1438. Interface port(s) 1438 include, for example, a serial port, a parallel port, a game port, and a universal serial bus (USB). Output device(s) 1440 use some of the same type of ports as input device(s) 1436. Thus, for example, a USB port may be used to provide input to computer 1412 and to output information from computer 1412 to an output device 1440. Output adapter 1442 is provided to illustrate that there are some output devices 1440 like monitors, speakers, and printers among other output devices 1440 that require special adapters. The output adapters 1442 include, by way of illustration and not limitation, video and sound cards that provide a means of connection between the output device 1440 and the system bus 1418. It should be noted that other devices and/or systems of devices provide both input and output capabilities such as remote computer(s) 1444.
Computer 1412 can operate in a networked environment using logical connections to one or more remote computers, such as remote computer(s) 1444. The remote computer(s) 1444 can be a personal computer, a server, a router, a network PC, a workstation, a microprocessor based appliance, a peer device or other common network node and the like, and typically includes many or all of the elements described relative to computer 1412. For purposes of brevity, only a memory storage device 1446 is illustrated with remote computer(s) 1444. Remote computer(s) 1444 is logically connected to computer 1412 through a network interface 1448 and then physically connected via communication connection 1450. Network interface 1448 encompasses communication networks such as local-area networks (LAN) and wide-area networks (WAN). LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet/IEEE 1102.3, Token Ring/IEEE 1102.5 and the like. WAN technologies include, but are not limited to, point-to-point links, circuit switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, and Digital Subscriber Lines (DSL).
Communication connection(s) 1450 refers to the hardware/software employed to connect the network interface 1448 to the bus 1418. While communication connection 1450 is shown for illustrative clarity inside computer 1412, it can also be external to computer 1412. The hardware/software necessary for connection to the network interface 1448 includes, for exemplary purposes only, internal and external technologies such as, modems including regular telephone grade modems, cable modems and DSL modems, ISDN adapters, and Ethernet cards.
What has been described above includes examples of the subject system and/or method. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the subject system and/or method, but one of ordinary skill in the art may recognize that many further combinations and permutations of the subject system and/or method are possible. Accordingly, the subject system and/or method are intended to embrace all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
This application is a continuation of and claims priority to U.S. patent application Ser. No. 11/166,364, filed Jun. 24, 2005, entitled “Extending Digital Artifacts Through An Interactive Surface,” and incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
5060135 | Levine | Oct 1991 | A |
5276680 | Messenger | Jan 1994 | A |
5488204 | Mead et al. | Jan 1996 | A |
5732227 | Kuzunuki | Mar 1998 | A |
5813009 | Johnson et al. | Sep 1998 | A |
5969720 | Lisle | Oct 1999 | A |
6005547 | Newman | Dec 1999 | A |
6243724 | Mander et al. | Jun 2001 | B1 |
6340978 | Mindrum | Jan 2002 | B1 |
6375344 | Hanson et al. | Apr 2002 | B1 |
6408278 | Carney | Jun 2002 | B1 |
6545660 | Shen | Apr 2003 | B1 |
6572015 | Norton | Jun 2003 | B1 |
6597255 | Turton | Jul 2003 | B1 |
6710754 | Hanson | Mar 2004 | B2 |
6725427 | Freeman et al. | Apr 2004 | B2 |
6760884 | Vertelney et al. | Jul 2004 | B1 |
6874037 | Abram et al. | Mar 2005 | B1 |
6886047 | Leong et al. | Apr 2005 | B2 |
6894703 | Vernier | May 2005 | B2 |
7058419 | Kotzin | Jun 2006 | B2 |
7134756 | Drucker | Nov 2006 | B2 |
7239867 | Kotzin | Jul 2007 | B2 |
7254665 | Yee | Aug 2007 | B2 |
7257426 | Witkowski | Aug 2007 | B1 |
7327376 | Shen | Feb 2008 | B2 |
7349722 | Witkowski | Mar 2008 | B2 |
7358962 | Dehlin | Apr 2008 | B2 |
7376901 | Shen | May 2008 | B2 |
7379047 | Drucker | May 2008 | B2 |
7394459 | Bathiche | Jul 2008 | B2 |
7397464 | Robbins | Jul 2008 | B1 |
7466308 | Dehlin | Dec 2008 | B2 |
7467380 | Kurlander | Dec 2008 | B2 |
7511703 | Wilson | Mar 2009 | B2 |
7525538 | Bathiche | Apr 2009 | B2 |
7577451 | Saint-Hilaire | Aug 2009 | B2 |
7627831 | Chiu et al. | Dec 2009 | B2 |
7639231 | Parry | Dec 2009 | B2 |
7657846 | Banks et al. | Feb 2010 | B2 |
7686682 | Diakopoulos et al. | Mar 2010 | B2 |
7743348 | Robbins et al. | Jun 2010 | B2 |
7898505 | Blythe | Mar 2011 | B2 |
8081964 | Enzmann | Dec 2011 | B1 |
8159350 | Bauchot et al. | Apr 2012 | B2 |
8199117 | Izadi et al. | Jun 2012 | B2 |
8380251 | Witkowski | Feb 2013 | B2 |
8494449 | Witkowski | Jul 2013 | B2 |
8519952 | Yee | Aug 2013 | B2 |
8543455 | Damera-Venkata | Sep 2013 | B2 |
8731614 | Kim | May 2014 | B2 |
8827792 | Sylla | Sep 2014 | B2 |
8838152 | Tang | Sep 2014 | B2 |
8897708 | Witkowski | Nov 2014 | B2 |
8899474 | Ackley | Dec 2014 | B2 |
8923760 | Iwasaki | Dec 2014 | B2 |
8930834 | Sunday | Jan 2015 | B2 |
8979654 | Baerlocher | Mar 2015 | B2 |
9001082 | Rosenberg et al. | Apr 2015 | B1 |
9002380 | Sabatelli | Apr 2015 | B2 |
9129473 | Nguyen | Sep 2015 | B2 |
9134798 | Morris | Sep 2015 | B2 |
9176749 | Kim | Nov 2015 | B2 |
9201624 | Joo | Dec 2015 | B2 |
9244598 | David | Jan 2016 | B1 |
9370041 | Witkowski | Jun 2016 | B2 |
9420420 | Sabatelli | Aug 2016 | B2 |
9430178 | David | Aug 2016 | B1 |
9454338 | David | Sep 2016 | B1 |
9654207 | Tang | May 2017 | B2 |
9911396 | Chen | Mar 2018 | B2 |
20010006855 | Koitsalu | Jul 2001 | A1 |
20010011026 | Nishijima | Aug 2001 | A1 |
20020087588 | McBride et al. | Jul 2002 | A1 |
20020101418 | Vernier | Aug 2002 | A1 |
20020146981 | Saint-Hilaire | Oct 2002 | A1 |
20020163537 | Vernier | Nov 2002 | A1 |
20020197955 | Witkowski | Dec 2002 | A1 |
20030018708 | Hlasny | Jan 2003 | A1 |
20030069874 | Hertzog et al. | Apr 2003 | A1 |
20030098845 | Hanson | May 2003 | A1 |
20030110291 | Chen | Jun 2003 | A1 |
20030147386 | Zhang | Aug 2003 | A1 |
20030156097 | Kakihara | Aug 2003 | A1 |
20030165128 | Sisodia | Sep 2003 | A1 |
20030228879 | Witkowski | Dec 2003 | A1 |
20040046784 | Shen | Mar 2004 | A1 |
20040098721 | Alverson | May 2004 | A1 |
20040150627 | Luman | Aug 2004 | A1 |
20040192274 | Vuori | Sep 2004 | A1 |
20040252075 | Matsubara | Dec 2004 | A1 |
20040267873 | Shen | Dec 2004 | A1 |
20050052156 | Liebenow | Mar 2005 | A1 |
20050090242 | Kotzin | Apr 2005 | A1 |
20050090279 | Witkowski | Apr 2005 | A9 |
20050108485 | Perego | May 2005 | A1 |
20050116683 | Cheng et al. | Jun 2005 | A1 |
20050120381 | Yamaguchi | Jun 2005 | A1 |
20050122308 | Bell et al. | Jun 2005 | A1 |
20050147218 | Novack | Jul 2005 | A1 |
20050156952 | Orner | Jul 2005 | A1 |
20050181839 | Tiainen et al. | Aug 2005 | A1 |
20050183035 | Ringel | Aug 2005 | A1 |
20050219204 | Huddleston | Oct 2005 | A1 |
20050248729 | Drucker | Nov 2005 | A1 |
20050251800 | Kurlander | Nov 2005 | A1 |
20050275635 | Dehlin | Dec 2005 | A1 |
20050275636 | Dehlin | Dec 2005 | A1 |
20050280631 | Wong | Dec 2005 | A1 |
20050285845 | Dehlin | Dec 2005 | A1 |
20060001645 | Drucker | Jan 2006 | A1 |
20060001650 | Robbins | Jan 2006 | A1 |
20060007123 | Wilson | Jan 2006 | A1 |
20060007124 | Dehlin | Jan 2006 | A1 |
20060007170 | Wilson | Jan 2006 | A1 |
20060039030 | Peterschmidt | Feb 2006 | A1 |
20060044289 | Yee | Mar 2006 | A1 |
20060066564 | Yee | Mar 2006 | A1 |
20060068870 | Crawford, III | Mar 2006 | A1 |
20060084442 | Kotzin | Apr 2006 | A1 |
20060092170 | Bathiche | May 2006 | A1 |
20060109199 | Yee | May 2006 | A1 |
20060119541 | Blythe | Jun 2006 | A1 |
20060125799 | Hillis | Jun 2006 | A1 |
20060205381 | Beart et al. | Sep 2006 | A1 |
20060227099 | Han | Oct 2006 | A1 |
20060230192 | Parry | Oct 2006 | A1 |
20060244719 | Brigham, II | Nov 2006 | A1 |
20060267952 | Alcorn | Nov 2006 | A1 |
20060274046 | Hillis | Dec 2006 | A1 |
20060284852 | Hofmeister | Dec 2006 | A1 |
20060284874 | Wilson | Dec 2006 | A1 |
20070024463 | Hall et al. | Feb 2007 | A1 |
20070030254 | Robrecht et al. | Feb 2007 | A1 |
20070052540 | Hall et al. | Mar 2007 | A1 |
20080045274 | Witkowski | Feb 2008 | A1 |
20080198138 | McFarlane | Aug 2008 | A1 |
20080216125 | Li | Sep 2008 | A1 |
20080227539 | Sato | Sep 2008 | A1 |
20080235747 | Choi | Sep 2008 | A1 |
20080248781 | Cedo Perpinya | Oct 2008 | A1 |
20080262916 | Damera-Venkata | Oct 2008 | A1 |
20090075724 | Breeding | Mar 2009 | A1 |
20090082928 | Witkowski | Mar 2009 | A1 |
20090086042 | Vartiainen | Apr 2009 | A1 |
20090095804 | Agevik et al. | Apr 2009 | A1 |
20090134973 | Sandler et al. | May 2009 | A1 |
20090143056 | Tang | Jun 2009 | A1 |
20090195513 | Dybalski | Aug 2009 | A1 |
20090254980 | Kanaparti | Oct 2009 | A1 |
20090267867 | Gonia | Oct 2009 | A1 |
20100041332 | Flygh et al. | Feb 2010 | A1 |
20100069158 | Kim | Mar 2010 | A1 |
20100125684 | Lee | May 2010 | A1 |
20110001686 | Belvin | Jan 2011 | A1 |
20110115818 | Chung | May 2011 | A1 |
20110124401 | Durham | May 2011 | A1 |
20110252320 | Arrasvuori | Oct 2011 | A1 |
20110273368 | Hinckley et al. | Nov 2011 | A1 |
20110298589 | McFarlane | Dec 2011 | A1 |
20110298751 | Merel | Dec 2011 | A1 |
20110303741 | Bolton et al. | Dec 2011 | A1 |
20120081207 | Toprani et al. | Apr 2012 | A1 |
20120095749 | Capretta | Apr 2012 | A1 |
20120154265 | Kim | Jun 2012 | A1 |
20120200759 | Vartiainen | Aug 2012 | A1 |
20120206391 | Kim | Aug 2012 | A1 |
20130130626 | Witkowski | May 2013 | A1 |
20130285796 | Witkowski | Oct 2013 | A1 |
20130331127 | Sabatelli | Dec 2013 | A1 |
20140123038 | Ahn | May 2014 | A1 |
20140159992 | Cai | Jun 2014 | A1 |
20140184487 | Cai | Jul 2014 | A1 |
20140295814 | Heo et al. | Oct 2014 | A1 |
20140364166 | Tang | Dec 2014 | A1 |
20150220300 | Reynaga | Aug 2015 | A1 |
20150289095 | Sabatelli | Oct 2015 | A1 |
20150311935 | Witkowski | Oct 2015 | A1 |
20160232878 | Chen | Aug 2016 | A1 |
20170123622 | Koenders | May 2017 | A1 |
20170215055 | Tang | Jul 2017 | A1 |
Number | Date | Country |
---|---|---|
2394843 | May 2004 | GB |
WO2005024865 | Mar 2005 | WO |
WO2014137054 | Sep 2014 | WO |
Entry |
---|
James Patten, Sensetable: A Wireless Object Tracking Platform for Tangible User Interfaces, Mar. 31-Apr. 4, 2001, Tangible Media Group, MIT Media Lab, Cambridge, MA 02139, vol. 3, Issue 1, pp. 253-260. |
Izadi et al., “Dynamo: A public interactive surface supporting the cooperative sharing and exchange of media”, Proceedings of the 16th annual ACM symposium on User interactive software and technology, 2003, pp. 159-168. |
Patten et al., “Sensetable: A Wireless Object Tracking Platform for Tangible User Interfaces”, Proceedings of CHI 2001, Mar. 31-Apr. 5, 2001, ACM Press, 8 pages. |
Abowd, et al., “The Family Video Archive: An Annotation and Browsing Environment for Home Movies”, available at least as early as Mar. 12, 2007, at <<http://delivery.acm.org/10.1145/980000/973266/p1-abowd.pdf?key1=973266&key2=9710583711&coll=&dl=acm&CFID=15151515&CFTOKEN=6184618>>, ACM, 2003, pp. 1-8. |
Apted, et al., “Sharing Digital Media on Collaborative Tables and Displays”, Technical Report 602, School of IT, The University of Sydney, Nov. 2006, 10 pgs. |
Beagrie, “Plenty of Room at the Bottom? Personal Digital Libraries and Collections”, retrieved on Mar. 14, 2007, at <<http://www.dlib.org/dlib/june05/beagrie/06beagrie.html>>, Neil Beagrie, vol. 11, No. 6, 2005, pp. 1-9. |
Buxton, “Multi-Touch Systems That I Have Known and Loved”, available available at least as early as Feb. 9, 2007, at <<http://www.billbuxton.com.multitouchOverview.html>>, 2007, pp. 1-21. |
“DiamondTouch”, retrieved on Mar. 9, 2007, at <<http://www.merl.com/projects/DiamondTouch>>, Mitsubishi Research Laboratories, 2006, pp. 1-2. |
“Ecoupled Technology Executive Summary”, Version 1.2, available as early as May 2007, pp. 1-6. |
Everitt, “UbiTable: Impromptu Face-to-Face Collaboration on Horizontal Interactive Surfaces”, Mitsubishi Electric Research Laboratories Inc., TR2003-49 Sep. 2003, In the Proceedings of the Fifth International Conference on Ubiquitous Computing, 2003, pp. 281-288 (11 pgs.). |
Mazalek, “Sharing and Browsing Media on a Digital Tabletop”, available as early as Mar. 12, 2007, at <<http://alumni.media.mit.edu/˜matt/cv/tviews_carpe_03.pdf>>, pp. 1-11. |
Niclass, et al., “A CMOS 3D Camera with Millimetric Depth Resolution”, IEEE Custom Integrated Circuits Congerence, p. 705-708, Oct. 2004, pp. 1-4. |
Shen, et al., “Personal Digital Historian: Story Sharing Around the Table”, ACM, Interactions, vol. 10, Issue 2, Mar. 2003, pp. 15-22. |
“Socio-Digital Systems”, available at least as early as Mar. 14, 2007, at <<http://research.microsoft.com/sds/>>, pp. 1-10. |
Wilson, “PlayAnywhere: A Compact Interactive Tabletop Projection-Vision System”, UIST '05, Oct. 23-27, 2005, pp 1-10. |
Gokturk et al., “A Time-of-Flight Sensor-System Description, Issues and Solutions,” Proceedings of the 2004 Conference on Computer Vision and Pattern Recognition Workshop, 2004, pp. 1-9. |
Ishii et al., “ClearBoard: A Seamless Medium for Shared Drawing and Conversation with Eye Contact,” ACM, 1992, pp. 1-10. |
Koike et al., “Information Layout and Interaction on Virtual and Real Rotary Tables,” In the Proceedings of the Second Annual IEEE International Workshop on Horizontal Interactive Human-Computer Systems, 2007, pp. 95-102. |
Leigh et al., “DiamondTouch Characteristics and Capabilities,” In: UbiComp 2002 Workshop on Collaboration with Interactive Tables and Walls, Goteborg, Sweden (2002) , retrieved at <<http://www.ipsi.fraunhofer.de/ambiente/ collabtablewallws/papers/leigh,%20merl,%20dt.pdf>> pp. 1-2. |
Newman et al., “CamWorks: A Video-Based Tool for Efficient Capture from Paper Source Documents,” Proceedings of the IEEE International Conference on Multimedia Computing Systems, vol. 2, p. 647, 1999, pp. 1-7. |
Office action for U.S. Appl. No. 13/493,497, dated Oct. 3, 2013, Izadi et al., “Interacting With Physical and Digital Objects Via a Multi-Touch Device,” 23 pages. |
Office Action for U.S. Appl. No. 13/493,497, dated Oct. 1, 2014, Shahram Izadi, “Interacting With Physical and Digital Objects Via a Multi-Touch Device,” 28 pages. |
Office action for U.S. Appl. No. 13/493,497, dated Mar. 20, 2015, Izadi et al., “Interacting With Physical Digital Objects Via a Multi-Touch Device,” 32 pages. |
Office action for U.S. Appl. No. 13/493,497, dated Apr. 29, 2013, Izadi et al., “Interacting With Physical and Digital Objects Via a Multi-Touch Device,” 28 pages. |
Office action for U.S. Appl. No. 13/493,497, dated May 15, 2014, Izadi et al., “Interacting With Physical and Digital Objects Via a Multi-Touch Device,” 31 pages. |
Office action for U.S. Appl. No. 13/493,497, dated Sep. 11, 2012, Izadi et al., “Interacting With Physical and Digital Objects Via a Multi-Touch Device,” 27 pages. |
“Swiss Ranger SR-2 Datasheet,” CSEM, 2004, pp. 1. |
Apple, Inc. “About External Accessories,” published on Jun. 14, 2015, retrieved on Aug. 19, 2015, available at <<https://developer.apple.com/library/ios/featuredarticles/ExternalAccessoryPT/Introduction/Introduction.html>>, 2 pages. |
“The Sensel Morph: Interaction, Evolved,” retrieved on Aug. 25, 2015 at <https://www.kickstarter.com/projects/1152958674/thesenselmorphinteractionevolved>, pp. 1-29. |
“Intuos,” Published on: Nov. 29, 2014, available at: <<http://www.wacom.com/en-in/products/pen-tablets/intuospen-and-touch-medium>>, 6 pages. |
Office action for U.S. Appl. No. 13/493,497, dated May 9, 2017 ,, Izadi et al., “Interacting With Physical and Digital Objects Via a Multi-Touch Device”, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20110273368 A1 | Nov 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11166364 | Jun 2005 | US |
Child | 13109765 | US |