Patent Grant
8522308
As display device technologies have advanced, increasingly large sizes of display devices such as flat-screen computer monitors and televisions have become available to consumers. Nevertheless, traditional uses of display devices, such as computer monitors and televisions, have remained personal experiences controlled by a single user. For example, a person utilizing a computer to surf the World Wide Web (“Web”) typically has full and exclusive control of the operation of the computer (via a mouse and keyboard attached to the computer) and, consequently, of the content displayed on a computer monitor driven by the computer. Another person looking over the shoulder of the person surfing the Web has no direct control over the operation of the computer and is therefore relegated to simply watching and/or providing suggestions as the person surfing the Web singularly controls the experience. This can be a frustrating experience when the Web surfing choices made by the person in control of the computer are not the same as the choices that the other person would have made. As another example, although watching television programming is often an activity shared by multiple people, the person holding the television remote control device has singular control over the viewing experience. This, too, can be a frustrating experience when the television viewing choices made by the person in control of the television remote control device are not the same as the choices that another person would have made.
The accompanying drawings illustrate various embodiments and are a part of the specification. The illustrated embodiments are merely examples and do not limit the scope of the disclosure. Throughout the drawings, identical or similar reference numbers designate identical or similar elements.
Exemplary systems and methods for providing a spatial-input-based multi-user shared display experience are disclosed herein. As described in more detail further below, one or more of the exemplary systems and methods disclosed herein may enable multiple users to share control of a display presented on a display screen. For example, an exemplary system may be configured to detect user input (e.g., gestures) provided by multiple users, authenticate the users, execute a multi-user shared display session that provides the authenticated users with concurrent control of a display on a display screen through the detected gestures, and manage, based on a shared session heuristic, how at least one resource associated with the display is shared between the authenticated users during the multi-user shared display session.
Accordingly, multiple users may operate together and/or interact by sharing control of a display on a display screen. In certain implementations, for example, multiple users may concurrently control a display presented on a television or a computer monitor by providing spatial input that may be detected and used to determine one or more display operations. As a result, surfing the web, watching television, or any other activity associated with a display screen may be an experience shared by multiple users who have concurrent control of the display screen and/or the activity as opposed to an experience in which only one of the users has control of the display screen and/or the activity at any given time.
As used herein, a resource associated with a display (also referred to herein as a “display resource”) may include, but is not limited to, screen space of a display screen on which the display is presented, one or more defined regions of the display screen (which may be referred to as “screen zones”), memory and/or processing resources of a computing device driving the display, applications running on and/or accessible by a computing device driving the display, content presented in the display (which may be referred to as “display content”), and any other resource associated with a display presented on a display screen of a display device. Display content may include graphical assets (e.g., frames, windows, cursors, and other graphical objects) presented in the display, application content presented in the display, media content presented in the display, and any other content presented in the display. Media content may include, without limitation, any television program, on-demand media program, pay-per-view media program, broadcast media program (e.g., broadcast television program), IPTV media content, advertisement (e.g., commercial), video, movie, video game, image, photograph, or any segment, component, or combination of these or other forms of media content that may be displayed for viewing by a user. Application content may include any content associated with an application running on a computing device, such as server-based application content, content associated with applications that execute on a local processor, video game content, web-based content like webpage content, and any combination or sub-combination thereof that may be displayed for viewing by one or more users.
As mentioned, a sharing of such resources between users may be managed based on a shared display heuristic, which may include data specifying one or more rules configured to govern how the display resources are to be shared between users included in a multi-user shared display session. Examples of such rules are described in detail further below.
Exemplary systems and methods for providing a spatial-input-based multi-user shared display experience will now be described in reference to the drawings.
Display subsystem 102 may include a display device configured to provide a display on a display screen of the display device for viewing by a user. The display device may include, without limitation, a television, a computer monitor, or other display device having a display screen on which a display may be presented for viewing by one or more users. A display may include any combination and/or layout of display content, including any of the types of display content described above. Data representative of display content may be stored as display data 112 in storage subsystem 110 and/or accessed from another content source.
Display subsystem 102 may include any hardware, firmware, and/or software configured to facilitate a display of content on a display screen for viewing by one or more users. For example, display subsystem 102 may include a display device, display screen, display driver(s), graphics engine, and/or other components configured to provide and/or control a display on a display screen. In certain embodiments, display subsystem 102 may include one or more components of a computing device such as a set-top box or a personal computer that are configured to generate and provide data representative of display content to a display device such as a television or a computer monitor for display on a display screen of the display device.
Spatial input subsystem 104 may be configured to perform any of the spatial input operations and applications described herein. Spatial input may include any user input that is provided by a user within a physical user space associated with a display screen and that may be detected by spatial input subsystem 104. In certain embodiments, spatial input may be provided by one or more users within the physical user space associated with the display screen without the users having to hold or otherwise utilize user input devices within the physical user space. For example, one or more users may perform gestures, such as hand gestures, within the physical user space, and spatial input subsystem 104 may detect the gestures. Spatial input subsystem 104 may be able to detect spatial input in any suitable way, including, for example, by employing two-dimensional and/or three-dimensional spatial sensing technologies capable of detecting spatial input within the physical user space associated with the display screen. For instance, spatial input subsystem 104 may include a single video camera, a stereo vision video camera, an array of video cameras, one or more infrared cameras, one or more time-of-flight sensors, one or more motion detectors, any other spatial input sensing technologies, and any combination or sub-combination thereof positioned relative to a display screen so as to monitor the physical user space associated with the display screen. An exemplary physical user space associated with a display screen is described in more detail further below.
Certain examples described herein are described in reference to spatial input subsystem 104 being configured to visually detect user input such as gestures performed by one or more users within a physical user space associated with a display screen. These examples are illustrative only. Other spatial input detection technologies, including any of those listed above, may be employed in addition or alternative to the visual input detection technologies described herein.
In certain embodiments, for example, spatial input subsystem 104 may be configured to visually detect user input provided by one or more users. To this end, spatial input subsystem 104 may be configured to visually monitor a physical user space associated with a display screen. Such a physical user space may include a three-dimensional space in which one or more users may be typically located when viewing the display screen. In certain embodiments, for instance, spatial input subsystem 104 may include one or more video cameras positioned relative to the display screen and configured to capture images of a physical user space located in front of the display screen. In some examples, the monitored physical user space may substantially coincide with a field of view of one or more cameras. To illustrate, spatial input subsystem 104 may include a single Charge-Coupled Device (“CCD”) or CMOS-sensor camera configured for two-dimensional sensing, a stereo vision camera for three-dimensional sensing, or an array of cameras for higher-fidelity three-dimensional sensing.
In certain embodiments, visually detected user input may include one or more gestures made by one or more users within the physical user space. For example, one or more users may act out one or more gestures, such as hand gestures, within the physical user space. Spatial input subsystem 104 may visually detect such gestures made within the physical user space. Examples of user input gestures are described in more detail further below.
Spatial input subsystem 104 may be further configured to identify and apply predefined input commands associated with visually detected user input. For example, spatial input subsystem 104 may visually detect user input such as one or more gestures, identify predefined input commands associated with the detected gestures, and initiate execution of one or more operations based on the predefined input commands. The gestures may be predefined and/or learned. Spatial input subsystem 104 may be configured to learn gestures to detect and accommodate differences in how users physically perform canonical, predefined gestures and/or to allow users to define custom gestures according to personal abilities and/or preferences. In some examples, the input commands may be configured to initiate operations that may control a display device, including a display presented on a display screen of the display device.
To support spatial-input-based control of operations of system 100, spatial input such as one or more user gestures may be predefined and associated with particular input commands (e.g., display screen input commands). Data representative of the predefined gestures may be stored as spatial input data 114 in storage subsystem 110 such that a detected gesture may be compared to one or more of the predefined gestures represented by spatial input data 114. When a comparison is made and a match is found, one or more input commands associated with the matching predefined gesture may be applied by spatial input subsystem 104 such that system 100 may consider the input command(s) and/or perform one or more operations in response to the input command(s).
As an example, a particular hand gesture may be predefined and associated with a user input command such as a user request to access system 100 (e.g., a request to login to system 100). Data representative of the predefined hand gesture may be stored as spatial input data 114 in storage subsystem 110. Subsequently, spatial input subsystem 104 may detect a hand gesture made by a user within the monitored physical user space, compare the detected hand gesture to spatial input data 114 representative of predefined hand gestures, determine that the detected hand gesture matches the predefined hand gesture associated with a user request to access system 100, determine that the predefined hand gesture is associated with a user request to access system 100, and apply the user access request such as by providing the user access request to one or more other components of system 100 to initiate one or more user access operations (e.g., user login and/or authentication operations).
In certain exemplary embodiments, spatial input subsystem 104 may be configured to visually detect user input gestures without the user having to hold, be attached to, or otherwise utilize a user input device. For example, a user may be able to use only his body to act out gestures that may be visually detected by spatial input subsystem 104. In some examples, a user may use one or more of his hands to act out hand gestures that may be visually detected by spatial input subsystem 104, without the user having to hold a user input device such as a remote control device, a mouse, a marker, or other input device.
Shared display subsystem 106 may be configured to perform any of the shared display operations described herein, including executing a multi-user display sharing session associated with a display and controlling, based on a shared session heuristic, how at least one resource associated with the display is shared between users during the multi-user display sharing session. Accordingly, one or more users may share control of one or more resources associated with the display by providing user input that may be visually detected and applied by spatial input subsystem 104 as described herein. Shared display subsystem 106 may interact with spatial input subsystem 104, including receiving user input commands from spatial input subsystem 104 and controlling, based on the shared session heuristic, how at least one resource associated with the display is shared between multiple users during execution of the multi-user display sharing session.
To support the execution and management of a multi-user shared display session and the controlling of how at least one resource of the display is shared between users during the session, shared display subsystem 106 may manage user identities, which may include authenticating and tracking users based on visually detected input. For example, when a user provides visually detected input, shared display subsystem 106 may identify a user identity based on the visually detected input, associate the user identity with the visually detected input, and control how display resources are shared during a multi-user shared display session based at least in part on the user identity. Examples of identifying and associating user identities with user input, as well as examples of basing sharing of display resources on user identities are described further below.
Shared display subsystem 106 may be further configured to create, manage, and terminate display sessions and user sessions. When multiple user sessions are added to a display session, the display session may be referred to a multi-user shared display session that is configured to provide concurrent control of a display to multiple users.
Shared display subsystem 106 may be further configured to control how display resources are shared between users during a multi-user shared display session. For example, shared display subsystem 106 may control how physical screen space of a display screen on which the display is provided is allocated and/or re-allocated between multiple users participating in the multi-user shared display session. The manner in which resources are shared may be determined by shared display subsystem 106 based on a shared display heuristic, visually detected user input, user identities of the users participating in the session, and/or other factors that may facilitate sharing of display resources between multiple users who share control of a display. Examples of how the sharing of display resources may be governed during a multi-user shared display session are described further below.
To support the management and control of a multi-user shared display session and/or the sharing of display resources, shared display subsystem 106 may be configured to maintain and access user identity data 116, session data 118, and shared session heuristic data 120 stored in storage subsystem 110. User identity data 116 may include any information about one or more users who may participate and/or who are participating in a multi-user shared display session. For example, user identity data 116 may include authentication information that may be used to authenticate users to system 100. Session data 118 may include any information about an active display session such as a multi-user shared display session and/or one or more user sessions that are part of a multi-user shared display session. Shared session heuristic data 120 may include any data representative of a shared session heuristic that may be configured for use by shared display subsystem 106 to determine how to control sharing of one or more display resources between multiple users during a multi-user shared display session.
Interface subsystem 108 may be configured to provide one or more interfaces between display subsystem 102, spatial input subsystem 104, shared display subsystem 106, and any computing hardware, firmware, and/or software associated with system 100. For example, interface subsystem 108 may provide an interface by which display subsystem 102, spatial input subsystem 104, and/or shared display subsystem 106 may communicate with an operating system and/or display content managers (e.g., application and/or media content managers) of a computing device. Interface subsystem 108 may include and/or employ any suitable technologies to provide such interfaces.
Storage subsystem 110 may store electronic data maintained and/or accessible by display subsystem 102, spatial input subsystem 104, shared display subsystem 106, and/or interface subsystem 108. Storage subsystem 110 may include one or more data storage media, devices, or configurations and may employ any type, form, and combination of data storage media and/or devices. For example, storage subsystem 110 may include, but is not limited to, a hard drive, network drive, flash drive, magnetic disc, optical disc, random access memory (“RAM”), dynamic RAM (“DRAM”), other non-volatile and/or volatile data storage units, or a combination or sub-combination thereof. Electronic data, including data described herein, may be temporarily and/or permanently stored in storage subsystem 110.
System 100, including facilities 102-110, may include any computer hardware and/or computer-implemented instructions (e.g., firmware and/or software), or combinations of computer-implemented instructions and hardware, configured to perform one or more of the processes described herein. In particular, system 100 may be implemented on one physical computing device or may be implemented on more than one physical computing device. Accordingly, system 100 may include or be implemented on any number of computing devices. Moreover, it will be recognized that although facilities 102-110 are shown to be separate facilities in
Accordingly, one or more of the processes described herein may be implemented at least in part as instructions executable by one or more appropriately configured computing devices. In general, a processor (e.g., a microprocessor) receives instructions, from a computer-readable medium, (e.g., a memory, etc.), and executes those instructions, thereby performing one or more processes, including one or more of the processes described herein. Such instructions may be stored and/or transmitted using any of a variety of known computer-readable media.
A computer-readable medium (also referred to as a processor-readable medium) includes any medium that participates in providing data (e.g., instructions) that may be read by a computer (e.g., by a processor of a computer). Such a medium may take many forms, including, but not limited to, non-volatile media and/or volatile media. Non-volatile media may include, for example, optical or magnetic disks and other persistent memory. Volatile media may include, for example, dynamic random access memory (“DRAM”), which typically constitutes a main memory. Common forms of computer-readable media include, for example, a floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, or any other tangible medium from which a computer can read.
In certain embodiments, sensing devices 208 may include a set of video cameras, which may be referred to as cameras 208 herein. Each camera in the set of cameras 208 may be configured to capture video frame images within a field of view of the camera. In such embodiments, a field of view associated with each camera is delineated by dashed lines extending from each camera in
Display device 204 may include any device configured to provide a display, the control of which may be shared by multiple users during a multi-user shared display session. Computing device 202 may include any device configured to drive display device 204 and execute and control a multi-user shared display session based on visually detected input as described herein. In certain embodiments, computing device 202 may include a set-top box and display device 204 may include a television connected to the set-top box. In other embodiments, computing device 202 may include a computer and display device 204 may include a monitor connected to the computer. In yet other embodiments, computing device 202 may include a gaming console and display device 204 may include a television or other display device connected to the gaming console. In yet other embodiments, computing device 202 may include a mobile computing device such as a mobile phone or mobile entertainment device.
Computing device 202 may include an input/output (“I/O”) module 212, a processor 214, and a storage device 216 communicatively coupled one to another via a communication infrastructure 218. The components of computing device 202 may communicate with one another, including sending data to and receiving data from one another, using any suitable communication technologies. While exemplary components of computing device 202 are shown in
I/O module 212 may be configured to transmit output signals and receive input signals to/from one or more other devices. For example, I/O module 212 may be configured to receive camera image data from cameras 208 and to output display signals to display device 204 for use by display device 204 to generate a display on display screen 206. I/O module 212 may include any suitable hardware, firmware, and/or software for transmitting output signals and receiving input signals to/from display device 204 and cameras 208. I/O module 212 may be connected to display device 204 and cameras 208 using any suitable technologies, such as IEEE 1394, DVI, HDMI, VGA, component video, Ethernet, USB, wireless, analog, digital, and/or other connections.
Processor 214 generally represents any type or form of processing unit capable of processing data or interpreting, executing, and/or directing execution of one or more of the instructions, processes, and/or operations described herein. Processor 214 may direct execution of operations in accordance with one or more applications 220 or other computer-executable instructions such as may be stored in storage device 216 or another computer-readable medium. As an example, processor 214 may be configured to process data, including processing raw image data received from cameras 208.
Storage device 216 may include one or more data storage media, devices, or configurations and may employ any type, form, and combination of data storage media and/or device. For example, storage device 216 may include, but is not limited to, a hard drive, network drive, flash drive, magnetic disc, optical disc, random access memory (“RAM”), dynamic RAM (“DRAM”), other non-volatile and/or volatile data storage units, or a combination or sub-combination thereof. Electronic data, including data described herein, may be temporarily and/or permanently stored in storage device 216. For example, data representative of one or more executable applications 220 configured to direct processor 214 to perform any of the operations described herein may be stored within storage device 216.
In some examples, display subsystem 102, spatial input subsystem 104, shared display subsystem 106, interface subsystem 108, and/or storage subsystem 110 may be partially or fully implemented by or within one or more components of computing device 202. For example, one or more applications 220 residing within storage device 216 may be configured to direct processor 214 to perform one or more processes or functions associated with display subsystem 102, spatial input subsystem 104, and/or shared display subsystem 106. Likewise, storage subsystem 110 may be implemented by or within storage device 216. For example, display data 112, spatial input data 114, user identity data 116, session data 118, and/or shared session heuristic data 120 may be stored within storage device 216.
As shown in
Hand recognizer module 302 may be configured to receive and process images captured by cameras 208. For example, raw image data captured by cameras 208 may be received and stored in frame buffers. Hand recognizer module 302 may process the images in the frame buffers in real time, such as by performing an isochronous transformation function that converts raw camera data into recognizable hand objects. For example, starting with raw camera input data B at time t, Bt=(b1t, b2t), where btt represents a frame buffer of camera 208-1 at time t and bet represents a frame buffer of camera 208-2 at time t, a first transformation function h( ) may be performed by hand recognizer module 302 to convert the raw image data B into recognized hand objects. A given hand at time t may be described as Ht=h(Bt, Rh)=(u,c), where u represents a user identifier, c represents a hand configuration vector, and Rh represents hand reference models stored in hand reference data store 304.
The function h( ) may be computed in any way suitable for converting raw image data captured by cameras 208 into data representative of recognized hand objects. In certain embodiments, for example, an execution of function h( ) may include using edge detection heuristics in combination with feature extraction heuristics (e.g., scaled Euclidean distance from a class mean, nearest neighbor search, and/or decision tree heuristics) to detect individual finger segments of a hand, a palm of a hand, a back of a hand, and/or other fixed shapes of a hand. The function h( ) may also be configured to consider basic affine transformations (e.g., scale, rotation, and translation) to account for movement and/or orientation of a hand relative to cameras 208. Detected parts of a hand may be compared with reference hand object models stored in hand reference data store 304 to identify matching hand parts, to connect hand parts together, to generate a vector of hand reference points H, and to identify a matching hand configuration.
When a sufficient number of connected hand parts are detected, hand recognizer module 302 may generate a vector of hand reference points H, and compute a correspondence between reference points in the two frame buffers associated with cameras 208. Because the relative orientation of cameras 208 is known, corresponding points may be computed by using the epipolar constraint.
Parts of a hand such as the hand 402 shown in
Hand recognizer module 302 may be configured to output data indicating when hands visually detected in sensing space 210 match one or more user hand reference models stored in hand reference data store 304. Hand recognizer module 302 may be configured to provide output to gesture recognizer module 306, including output indicating that a match has been identified and/or data representative of a generated vector of hand reference points Hat time t.
Gesture recognizer module 306 may be configured to detect hand gestures based on data representative of sequences of detected hand configurations, which may be represented by vectors of hand reference points H received from hand recognizer module 302. In certain embodiments, gesture recognizer module 306 may be configured to perform an isochronous transformation function g( ) that converts sequences of hand objects into recognizable gestures. For example, a given gesture G that began at time t and continued through time t+n may be described by Gt+n=g([Ht, Ht+n], Rg), where Rg represents gesture reference models stored in gesture reference data store 308.
The function g( ) may be computed in any way suitable for converting sequences of visually detected hand objects into recognizable gestures. In certain embodiments, for example, an execution of function g( ) may include comparing a sequence of hand object vectors Ht through Ht+n with reference gestures stored in gesture reference data store 308 to identify a match. When a match is identified, gesture recognizer module 306 may generate and output data representative of the gesture G to command generator module 310.
Command generator module 310 may be configured to identify one or more user input commands based on data representative of gestures, which may include data representative of a gesture G received from gesture recognizer module 306. Command generator module 310 may identify a command C associated with a gesture G by using data representative of the gesture G to identify command C in a lookup table that provides a mapping of gestures to corresponding user input commands. This may be accomplished by command generator module 310 executing a lookup function c( ) to identify command C based on gesture G and a command reference table Rc stored in command reference data store 312 as described by C=c(G, Rc).
Gestures may be acted out by users within a visually monitored user space to control and/or participate in a multi-user shared display session and/or to otherwise control a display. Accordingly, multiple users located within the sensing space 210 shown in
In certain embodiments, gestures may be mapped to commands for requesting to login to a session (e.g., a multi-user shared display session, a user session, and/or a display control session), to logout from a session, to invite another user to a multi-user shared display session, to un-invite another user from a multi-user shared display session, to block another user from a multi-user shared display session, to unblock another user from a multi-user shared display session, to transfer a user to/from a multi-user shared display session, to create a frame in a display, to resize a frame in a display, to create a window in a display, to move a window in a display, to resize a window in a display, to delete a frame or a window from a display, to maximize a size of a frame or window in a display, to return a maximized frame or window to a previous state in the display (e.g., to a previous size and location in the display), to convert a frame to a window in a display, to convert a window to a frame in a display, to move a cursor in a display, to select or highlight an object in a display, to open and/or execute an object in a display, to create a “rubber-band” box object in a display, to undo a previous operation, to redo an undone operation, to play, pause, or stop a media stream, to skip, fast forward, or rewind within a media stream, to increase or decrease audio volume, to mute audio volume, to tune to another media content carrier channel, to delete a media stream, to create an American Sign Language (“ASL”) letter, and to create an ASL word. These user input commands, which may be mapped to gestures that may be acted out by a user, are illustrative only. Additional and/or alternative user input commands may be mapped to gestures in other embodiments.
Gestures defined for use by a user to participate in a multi-user shared display session and/or to otherwise control a display may include categories of gestures. For example, gestures may include one or more authentication gestures configured to be used to request authentication operations (e.g., to login and/or logout to/from a session), one or more session management gestures configured to be used to manage a multi-user shared display session (e.g., to invite, un-invite, block, unblock, and/or transfer another user to/from a session), one or more screen layout gestures configured to be used to manage a layout and/or content of a shared display (e.g., to create, resize, move, delete, maximize, and/or convert a frame or window in a display), one or more screen object control gestures configured to be used to manipulate objects (e.g., graphical assets) in a display (e.g., to move a cursor, to select, highlight, open, or execute an object in a display), one or more media control gestures configured to be used to control media operations (e.g., to play, pause, stop, skip, fast forward, rewind, and/or delete a media stream), one or more data entry controls configured to be used to input text or other data (e.g., to input ASL letters and/or ASL words), or any combination or sub-combination of the above-listed categories of gestures.
Other exemplary gestures and mappings of the gestures to user input commands are depicted in Table 1. The examples of gestures and corresponding user input commands depicted in Table 1 are illustrative only. Other gestures and/or user input commands may be defined in other embodiments.
In certain embodiments, a gesture may be classified as a discrete gesture or a continuous gesture. A discrete gesture may include singe gesture expression that may be acted out one time and for which the corresponding command is immediately applied following the detection of the gesture. An example of a discrete gesture may include gesture 502 shown in
As described above, system 100 may be configured to visually detect user input, such as gestures performed by one or more users, identify user input commands associated with the detected user input, and apply the user input commands to execute operations associated with the commands. The operations associated with the commands may include any operations that may be performed by system 100, including any of the operations described herein. In certain embodiments, the operations may be associated with the providing and/or controlling of a display and/or content of the display for viewing by one or more users.
As mentioned, system 100 may be configured to allow multiple users to share control of one or more resources associated with a display. For example, multiple users may provide user input within sensing space 210, and system 100 may visually detect the user input, execute a multi-user shared display session, and control, based on a shared session heuristic, how at least one resource associated with the display is shared between users during the multi-user display sharing session.
To illustrate, display subsystem 102 may provide a display on a display screen. One or more resources, including any of the display resources described herein, may be associated with the display. One or more users may provide visual input to control the display provided by display subsystem 102. For example, one or more users may act out gestures within a physical user space (e.g., a physical user space within sensing space 210) associated with the display screen on which the display is shown. Spatial input subsystem 104 may detect the gestures and identify and apply user input commands corresponding with the gestures as described above to control the display. Shared display subsystem 106 may manage the multi-user shared display session and control how resources associated with the display are shared between the users participating in the session.
In certain embodiments, shared display subsystem 106 may be configured to utilize an object class model to manage how resources of a display are shared.
Display screen object class 602 may represent a physical display screen on which a display may be shown. Display session object class 604 may represent a display session during which a display is shown on the display screen represented by display screen object class 602. As shown in
Display session object class 604 may have a one-to-n relationship with user session object class 608, which indicates that a display session may include one or more user sessions. A display session that contains only a single user session may be referred to as a single-user display session. A display session that contains multiple user sessions may be referred to as a multi-user shared display session and may provide a shared display environment. Exemplary display sessions are described in more detail further below.
User session object class 608 may be associated with user object class 606, which may represent an identity of an authenticated user who may control a user session. As shown in
A user session associated with a display (e.g., contained within a display session) may be associated with one or more resources of the display. The resources associated with the user session may comprise a collection of resources that are owned and/or managed by a user who controls the user session. To illustrate, user session object class 608 may have a one-to-n relationship with screen zone object class 610, which indicates that a user session may own one or more screen zones within the display screen (e.g., physical regions of the display screen) on which the display is shown. A screen zone may include a physical region of the display screen. User session object class 608 may also have a one-to-n relationship with graphical asset object class 612, which indicates that a user session may own one or more graphical assets shown in the display. In some examples, user session object class 608 may have a one-to-one relationship with cursor object class 614 as illustrated in FIG. 6, which indicates that a user session may own a single cursor (or pointer or other icon) shown in the display. In other examples, user session object class 608 may have a one-to-n relationship with cursor object class 614 such that a user session may own multiple cursors. Accordingly, a user may have control of multiple cursors shown in a display. For example, two cursors may be shown concurrently in a display, and each hand of a user may be able to control a different one of the cursors. As another example, multiple cursors may be shown concurrently in a display, and each finger of a hand of a user may be used to control a different one of the cursors. Relationships of screen zone object class 610, graphical asset object class 612, and cursor object class 614 with user session object class 608 may be used by shared display subsystem 104 to determine ownership of display resources and to control how the display resources are controlled and/or shared between users associated with user sessions contained with a display session.
As shown in
Accordingly, a display shown on a display screen during a display session may include one or more screen zones, graphical assets, and/or cursors owned and/or controlled by one or more users. For example,
Shared display subsystem 106 may be configured to maintain access permission settings for each resource associated with a display, including for each screen zone 702 associated with the display. The permission settings may designate that a user who owns a screen zone 702 has full access to the screen zone 702, based on the user's ownership of the screen zone 702, such that the user may control the display content included in the screen zone 702. In addition, the permission settings may specify a level of access that another authenticated user participating in a display session may be given to the screen zone 702. For example, the permission settings may specify whether or not another authenticated user is allowed to move his cursor within the screen zone 702 and/or control or otherwise operate on display content within the screen zone 702.
Shared display subsystem 106 may be configured to cause a display session to operate in a collaborative mode and/or a static mode. In a static mode, a user may be provided access only to a screen zone 702 that is owned by the user. Accordingly, in a strictly static mode, each user participating in a display session may be provided access only to the screen zone 702 that is owned by the same user. For example, one user may watch media content presented within one screen zone 702 on the display screen, while another user may be browsing the web and viewing application content presented within another screen zone 702 on the display screen. In a collaborative mode, a user may be provided full access to a screen zone 702 that is owned by the user and partial or full access to at least one other screen zone 702 that is owned by another authenticated user participating in the display session. Accordingly, in collaborative mode, users may interact by controlling display content across screen zones 702. In some examples, a display session may be operated using a combination of one or more collaborative modes and one or more static modes. For example, one or more screen zones 702 within a display may be set to operate in a collaborative mode based on permission settings of the screen zones 702, and one or more other screen zones 702 within the display may be set to operate in a static mode based on permission settings of the other screen zones 702.
Shared display subsystem 106 may be configured to toggle between operating in a collaborative mode and a static mode. For example, access permission settings for a screen zone 702 may be changed in a way that toggles the screen zone 702 between operating in a collaborative mode and a static mode. In certain embodiments, shared display subsystem 106 may be configured to provide a session management tool configured to allow a user to manage a display session such as by inputting one or more access permission settings for a screen zone 702 owned by the user.
Using session management tool 802, a user may adjust screen zone settings such as by dragging user icons into and/or out of a screen zone 702 to grant or withdraw the corresponding user's access to the screen zone 702, resize screen zones 702, and/or merge screen zones 702. A user may select a “full share” button 804 in session management tool 802 to set screen zone permission settings to a full collaboration mode or a “full partition” button 806 to set screen zone permission settings to a full static mode. In response to user input received by session management tool 802, shared display subsystem 104 may adjust screen zone settings such as by toggling between a collaborative mode and a static mode in the display session.
Shared display subsystem 106 may be configured to manage display resources by controlling how screen space of a display screen is shared between users. For example, shared display subsystem 106 may control allocation and management of screen space for inclusion in screen zones 702. In certain embodiments, shared display subsystem 106 may be configured to control how screen space is shared based on a shared session heuristic, which may specify one or more rules and/or conditions to be considered when determining how to allocate and/or manage screen space. In certain examples, for instance, the shared session heuristic may specify that screen space is to be allocated evenly between authenticated users participating in a display session. Accordingly, when a new user joins the display session, shared display subsystem 106 may dynamically reallocate screen space by rebalancing the shared screen allocation among the authenticated users in the new user set. The shared session heuristic may specify one or more rules configured to govern the rebalancing of screen space based on, without limitation, a prior display screen layout, user precedence settings, preferred layout settings, and/or specific user preferences (e.g., a user preference specifying preferred positions for screen zones 702 on a display screen). Examples of user precedence settings may include, without limitation, settings indicating that a user who joined the display session first may have precedence over a user who joined the display session later, a user who is a head of a household may have precedence over other users within the household, an account holder of a subscriber account may have precedence over other users associated with the account, and a parent may have precedence over children users within a household.)
To further facilitate an understanding of how sharing of display resources may be controlled by shared display subsystem 106 during a display session,
Next, a second user (“User B”) may request to login to system 100. System 100 may detect the login request, authenticate User B, and add User B to the display session. Shared display subsystem 106 may rebalance the screen space of the display screen such as by dividing the screen space into equal screen zones 902-1 and 902-2 owned by User A and User B, respectively, as shown in
Next, User A may request to resize his screen zone 902-1. System 100 may detect the request and determine, based on the shared session heuristic, whether the request will be performed. For example, shared display subsystem 106 may access information in the shared display heuristic to determine whether User A has higher precedence than User B, or whether User B has granted User A permission to control User B's screen zone 902-2. If either determination is affirmative, shared display subsystem 106 may resize screen zones 902-1 and 902-2, as well as frames A1 and B1, such as is shown in
Next, User A may request to open windows within his screen zone 902-1. System 100 may detect the request, determine, based on the shared display heuristic, that User A owns screen zone 902-1, and open the windows in screen zone 902-1.
Next, User B may request to split his screen zone 902-2 into two parts. For example, User B may wish to watch two media programs at once. System 100 may detect the request, determine, based on the shared display heuristic, that User B owns screen zone 902-2, and split screen zone 902-2 into two screen zones 902-2 and 902-3 as shown in
Next, system 100 may detect a request to maximize frame B2 to fill the entire display screen. For example, User A and User B may agree to focus on frame B2. User A and/or User B may request that frame B2 be maximized. System 100 may determine, based on the shared display heuristic and/or input provided by User A and/or User B, that frame B2 may be maximized as requested. System 100 may then maximize frame B2 to temporarily fill the display screen, as shown in
Next, system 100 may detect a request to restore frame B2 to its pre-maximization state and to maximize window A3 to fill the entire display screen. For example, User A and User B may agree to shift the focus of the display from frame B2 to window A3. User A and/or User B may request that frame B2 be restored to its pre-maximization state and that window A3 be maximized. System 100 may determine, based on the shared display heuristic and/or input provided by User A and/or User B, that window A3 may be maximized as requested. System 100 may then restore frame B2 and maximize window A3 to temporarily fill the display screen, as shown in
Next, system 100 may detect a request to restore window A3 to its pre-maximization state. For example, User A and User B may agree to return to the screen layout shown in
Next, a third user (“User C”) may request to login to system 100. System 100 may detect the login request, authenticate User C, and add User C to the display session. Shared display subsystem 106 may rebalance the screen space of the display screen such as by equally dividing the screen space between User A, User B, and User C, respectively. As shown in
Next, User B may request to logout of system 100. System 100 may detect the logout request and remove User B from the display session. Shared display subsystem 106 may rebalance the screen space of the display screen based on user precedence settings specified in the display session heuristic. For example, User A and User C may have equal precedence in the display session heuristic, and, as a result, the screen space allocated to User B before logout may be equally divided between User A and User C. As another example, the screen space allocated to User B before logout may be divided in proportion to the screen space allocated to User A and User C at logout of User B.
Next, User C may request to open a window within his screen zone 902-4. System 100 may detect the request, determine, based on the shared display heuristic, that User C owns screen zone 902-4, and open the window in screen zone 902-4.
Next, User A may request to move window A3, in part or in whole, from his screen zone 902-1 into User C's screen zone 902-4. System 100 may detect the request and determine, based on the shared display heuristic, whether the request will be performed. For example, shared display subsystem 106 may access information in the shared display heuristic to determine whether User A has higher precedence than User C, or whether User C has granted User A permission to move graphical assets into User C's screen zone 902-4. If either determination is affirmative, shared display subsystem 106 may move window A3 into screen zone 902-4 as shown in
Next, User C may request to move window C2 from his screen zone 902-4 to User A's screen zone 902-1. System 100 may detect the request and determine, based on the shared display heuristic, whether the request will be performed. For example, shared display subsystem 106 may access information in the shared display heuristic to determine whether User C has higher precedence than User A, or whether User A has granted User C permission to move graphical assets into User A's screen zone 902-1. If neither determination is affirmative, shared display subsystem 106 may prevent window C2 from being moved beyond the boundary of screen zone 902-4, as shown in
Next, User C may request to logout of system 100. System 100 may detect the logout request and remove User C from the display session. Shared display subsystem 106 may rebalance the screen space of the display screen based on user precedence settings specified in the display session heuristic. In this case, User A is now the sole user participating in the display session, so shared display subsystem 106 may allocate the full screen space to User A.
Next, User A may request to close windows A2 and A3 within his screen zone 902-1. System 100 may detect the request, determine, based on the shared display heuristic, that User A owns windows A2 and A3, and close the windows A2 and A3, as shown in
The above-described sequence of user inputs and management of display 900 shown on a display screen during a display session is illustrative only. Other operations may be performed by system 100 in other examples based on the shared display heuristic and other sequences of user inputs.
To facilitate management of how resources associated with a display are shared between users during a multi-user shared display session, shared display subsystem 106 may be configured to manage user identities, the display session, and the use of display resources. Returning to
Identity manager module 314 may compare the data representative of a detected hand features to reference hand data, which may be stored in hand reference data store 304, to identify a match. When a match is identified, identity manager module 314 may determine a user identity associated with the matching reference hand data and provide data representative of the user identity to session manager module 316. Identity manager module 314 may also generate an association between the detected hand and the user identity.
The above-described determination of a user identity that matches a detected hand may be used to authenticate a user to system 100. However, this is illustrative only. Other user authentication techniques may be employed in other embodiments. For example, fingerprint matching and/or retina scanning may be used to provide a higher level of authentication security.
Once the user is authenticated, identity manager module 314 may pass the login request to session manager module 316, which may either create and add the user requesting login to a new display session if no other user is currently logged in to system 100 or add the user requesting login to an existing display session. Session manager module 316 may then send a new user request to display manager module 318, which may be configured to determine how to allocate display resources in view of the new user request. For example, display manager module 318 may allocate screen space such as a screen zone to the new user based on the shared display heuristic. If the display session is a multi-user shared display session, display manager module 318 may allocate screen space by rebalancing the screen space among the new set of authenticated users participating in the session based on the shared display heuristic. Display manager module 318 may also control, based on the shared display heuristic, how other resources (e.g., display content) associated with the display are shared between users during the display session. Accordingly, the new user may participate together with one or more other users in controlling the display by providing visual input commands to system 100. This may allow users to interact with one another and with display content in a display to produce a shared screen experience.
During a display session, identity manager module 314 may continually track the hand of each authenticated user (e.g. from frame to frame) to ensure that the appropriate user identity remains associated with the correct hand. For example, hand recognizer module 302 may continue to provide data representative of detected images (e.g., captured frames) to identity manager module 314, which may be configured to utilize the data to verify that a tracked hand satisfies a predetermined continuity constraint. The continuity constraint may specify one or more conditions that should be satisfied to ensure that a tracked hand should remain associated with the same user identity. If the predetermined continuity constraint is not satisfied, the user identity of the hand may no longer be verifiable, and session manager module 316 may initiate performance of one or more session management operations. For example, if a hand is no longer detected (e.g., the hand goes out of sensing space 210), or if the hand is moved too quickly within sensing space 210 to satisfy the continuity constraint, session manager module 316 may initiate performance of one or more session management operations that are configured to respond to the detected lack of continuity.
As an example, in response to an interruption of hand continuity, identity manager module 314 may be configured to apply one or more timed downgrades to display resources associated with the user identity associated with the hand that has lost continuity. For example, when tracked hand continuity is interrupted, identity manager module 314 may set a status of a user session associated with the hand to a first dormant state. In the first dormant state, the user session may be suspended and graphical assets owned by the user session dimmed in the display. If the user is not re-authenticated within a first time duration after the user session is set to the first dormant state (e.g., thirty seconds after being set to the first dormant state), identity manager module 314 may set a status of the user session to a second dormant state. In the second dormant state, graphical assets owned by the user session may be removed from the display such as by minimizing the assets. If the user is not re-authenticated within a second time duration after the user session is set to the second dormant state (e.g., five minutes after being set to the second dormant state), identity manager module 314 may set a status of a user session associated with the hand to a third dormant state. In the third dormant state, the user session may be terminated and the graphical assets owned by the user session released.
The above-described session management operations that may be performed in response to a detected interruption to hand continuity are illustrative only. Other operations may be performed when continuity of hand tracking is lost in other embodiments.
Session manager module 316 may be configured to create, manage, and terminate a display session and one or more user sessions included in the display session. To this end, session manager module 316 may add user sessions to a display session, remove user sessions from a display session, and maintain a register of authenticated users who have user sessions included in a display session.
Display manager module 318 may be configured to determine, based on the shared session heuristic, whether and/or how to apply user input commands received from command generator module 310. Display manager module 318 may also control how display resources are shared and/or used in a display, based on the shared session heuristic. Display manager module 318 may be configured to implement and/or maintain the shared session heuristic, which, in certain embodiments, may include data representing a set of rules for governing the application of user input commands and/or the use of display resources during a multi-user shared display session. The set of rules may include, without limitation, display screen geometry rules configured to govern whether frames or windows are used in a display and whether to maintain fixed aspect ratios of screen zones, frames, or windows (e.g., to support playback of video content having a fixed aspect ratio within a screen zone, frame, or window that is sized in accordance with the fixed aspect ratio), screen space allocation rules configured to govern how screen space is allocated and/or re-allocated among users, asset permission rules configured to govern which users have control, explicit or implicit, of display content such as graphical assets in a display, user precedence rules configured to govern which users and/or user requests are to be given precedence (e.g., based on fixed user priorities and/or order of user entry into a display session), session management rules configured to govern how display sessions are established, managed, and terminated and how users are added to and/or removed from display sessions, user request rules configured to govern how user requests are accepted, applied, and/or rejected, quality-of-service (“QoS”) rules configured to govern operations so as to comply with QoS standards (e.g., by specifying how finite bandwidth is shared among multiple users when a sum of requests exceeds the available bandwidth), and any combination or sub-combination of the above rules.
As mentioned, asset permission rules may be used by display manager module 318 to determine which users are allowed to manipulate graphical assets such as windows and frames in a shared display. To this end, in certain embodiments, a permission descriptor may be attached to each graphical asset. For each graphical asset associated with a multi-user display session, for example, display manager module 318 may instantiate a permission descriptor for each non-owner user participating in the session (i.e., for each user other than the owner of the graphical asset). Accordingly, the permission descriptor associated with a graphical asset may specify permissions to be granted and/or denied to other users for interacting with the graphical asset.
As an example, in certain embodiments, a permission descriptor may include a vector of four variables including a cursor entry variable, a screen space allocation variable, a content control variable, and an existence control variable. The cursor entry variable may be set to a value to indicate whether a given user is allowed to move his cursor into the associated graphical asset. The screen space allocation variable may be set to a value to indicate whether a given user is allowed to modify the screen space occupied by the associated graphical asset (e.g., by moving, resizing, minimizing, or maximizing the graphical asset). The content control variable may be set to a value to indicate whether a given user is allowed to operate on application and/or media content displayed within the associated graphical asset (e.g., by executing application and/or media content operations). The existence control variable may be set to a value to indicate whether a given user is allowed to create and/or delete an associated graphical asset.
To illustrate, a permission descriptor may be defined as Pu=(cursor entry, screen space allocation, content control, existence control), where u represents a given user to whom the permission descriptor applies. A graphical asset that is completely unconstrained to user u may be associated with a permission descriptor defined as Pu=(1, 1, 1, 1). In this case, user u may be allowed to perform any operation on the graphical asset, which may represent a full collaboration mode of operation. Conversely, a graphical asset that is fully restricted to user u may be associated with a permission descriptor defined as Pu=(0, 0, 0, 0). In this case, user u may be prevented from performing any operation on the graphical asset, which may represent a static mode of operation. As another example, a permission descriptor defined as Pu=(1, 1, 1, 0) may allow user u to perform any operation on the associated graphical asset except for making new copies of or deleting the graphical asset. As yet another example, a permission descriptor defined as Pu=(1, 0, 0, 0) may allow user u only to move his cursor into the graphical asset (e.g., to highlight content shown in the graphical asset).
Permission rules may be set statically or dynamically by display manager module 318 for graphical assets associated with a display session. For example, permission rules may be set to default values based on a type of a graphical asset when the graphical asset is added to a display. As another example, system 100 may set and/or modify permission rules based on user input. For example, using session management tool 802 shown in
As mentioned, interface subsystem 108 may be configured to provide one or more interfaces between display subsystem 102, spatial input subsystem 104, shared display subsystem 106, and any computing hardware, firmware, and/or software associated with system 100. For example, interface subsystem 108 may include OS object manager module 320 and media stream manager module 322, which may be configured to connect one or more other modules shown in
In step 1202, user input provided by one or more users may be detected. Step 1204 may be performed in any of the ways described herein. For example, spatial input subsystem 104 may visually detect user input such as one or more hand gestures made by users within a physical user space associated with a display screen.
In step 1204, the users are authenticated. Step 1204 may be performed in any of the ways described herein, including by identifying user identities for the users based on the detected user input.
As part of or in addition to the authentication performed at step 1204, one or more additional operations may be optionally performed at or following step 1204. For example, associations between the hands providing user input and the identified user identities may be created. In addition, a continuity of each hand used to provide the input may be tracked and used to ensure that the associations between the hands and the user identities remain accurate. Accordingly, system 100 may manage display sessions and/or allocations of display resources based at least in part on the user identities associated with hands providing user input.
In step 1206, a multi-user shared display session may be executed. The multi-user shared display session may be configured to provide the users with concurrent control of a display on a display screen through user input. Step 1206 may be performed in any of the ways described above.
In step 1208, how at least one resource associated with the display is shared between the users during the multi-user shared display session may be controlled based on a shared session heuristic. Step 1208 may be performed in any of the ways described above. For example, shared display subsystem 106 may control, based on the shared session heuristic, how at least one resource, such as screen space of the display screen, screen zones, and/or display content associated with the display is shared between the users during the session.
In step 1302, a gesture made by a first user within a physical user space associated with a display screen may be detected. Step 1302 may be performed in any of the ways described above. For example, spatial input subsystem 104 may visually detect a gesture made by the first user within the physical user space associated with the display screen. In certain examples, the gesture may be associated with a login request.
In step 1304, the first user may be authenticated based on the gesture made by the first user. Step 1304 may be performed in any of the ways described herein, including by identifying a user identity based on the gesture made by the first user.
In step 1306, a gesture made by a first user within the physical user space associated with the display screen may be detected. Step 1306 may be performed in any of the ways described above. For example, spatial input subsystem 104 may visually detect a gesture made by the second user within the physical user space associated with the display screen. In certain examples, the gesture may be associated with a login request.
In step 1308, the second user may be authenticated based on the gesture made by the second user. Step 1308 may be performed in any of the ways described herein, including by identifying a user identity based on the gesture made by the second user.
In step 1310, a multi-user shared display session may be executed. The multi-user shared display session may be configured to allow the first user and the second user to concurrently control a display on a display screen in any of the ways described herein.
In step 1312, how at least one resource associated with the display is shared between the first user and the second user during the multi-user shared display session may be managed based on a shared session heuristic. Step 1312 may be performed in any of the ways described herein. For example, shared display subsystem 106 may manage, based on the shared session heuristic, how at least one resource, such as screen space, screen zones, and/or display content associated with the display is shared between the first user and the second user during the multi-user shared display session.
For example, in step 1312, the sharing of screen space may be managed by dividing the screen space of the display screen into a first screen zone and a second screen zone and providing the first user control of the first screen zone and the second user control of the second screen zone. In addition, access permissions for the first screen zone may be set and may specify a level of access that the second user is to be given to the first screen zone. Similarly, access permissions for the second screen zone may be set and may specify a level of access that the first user is to be given to the second screen zone. As described above, such access permissions may be modified by a user utilizing session management tool 802.
One or more steps shown in
In certain implementations, any of the steps shown in method 1200 or 1300 of
In the preceding description, various exemplary embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the scope of the invention as set forth in the claims that follow. For example, certain features of one embodiment described herein may be combined with or substituted for features of another embodiment described herein. The description and drawings are accordingly to be regarded in an illustrative rather than a restrictive sense.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5107443 | Smith et al. | Apr 1992 | A |
| 5239373 | Tang et al. | Aug 1993 | A |
| 5381158 | Takahara et al. | Jan 1995 | A |
| 5442788 | Bier | Aug 1995 | A |
| 5534917 | Macdougall | Jul 1996 | A |
| 5561811 | Bier | Oct 1996 | A |
| 5594469 | Freeman et al. | Jan 1997 | A |
| 5677700 | Schwalba et al. | Oct 1997 | A |
| 5732227 | Kuzunuki et al. | Mar 1998 | A |
| 5767842 | Korth | Jun 1998 | A |
| 5917490 | Kuzunuki et al. | Jun 1999 | A |
| 6008800 | Pryor | Dec 1999 | A |
| 6128003 | Smith et al. | Oct 2000 | A |
| 6191773 | Maruno et al. | Feb 2001 | B1 |
| 6266057 | Kuzunuki et al. | Jul 2001 | B1 |
| 6417841 | Doi et al. | Jul 2002 | B1 |
| 6498628 | Iwamura | Dec 2002 | B2 |
| 6498970 | Colmenarez et al. | Dec 2002 | B2 |
| 6501515 | Iwamura | Dec 2002 | B1 |
| 6594616 | Zhang et al. | Jul 2003 | B2 |
| 6624833 | Kumar et al. | Sep 2003 | B1 |
| 6720949 | Pryor et al. | Apr 2004 | B1 |
| 6788809 | Grzeszczuk et al. | Sep 2004 | B1 |
| 6952199 | Doi et al. | Oct 2005 | B2 |
| 6996460 | Krahnstoever et al. | Feb 2006 | B1 |
| 7003728 | Berque | Feb 2006 | B2 |
| 7007236 | Dempski et al. | Feb 2006 | B2 |
| 7058204 | Hildreth et al. | Jun 2006 | B2 |
| 7134080 | Kjeldsen et al. | Nov 2006 | B2 |
| 7227526 | Hildreth et al. | Jun 2007 | B2 |
| 7327858 | Weiss | Feb 2008 | B2 |
| 7379563 | Shamaie | May 2008 | B2 |
| 7379566 | Hildreth | May 2008 | B2 |
| 7389591 | Jaiswal et al. | Jun 2008 | B2 |
| 7421093 | Hildreth et al. | Sep 2008 | B2 |
| 7430312 | Gu | Sep 2008 | B2 |
| 20020036617 | Pryor | Mar 2002 | A1 |
| 20020186200 | Green | Dec 2002 | A1 |
| 20030032478 | Takahama et al. | Feb 2003 | A1 |
| 20040063480 | Wang | Apr 2004 | A1 |
| 20040063481 | Wang | Apr 2004 | A1 |
| 20040155902 | Dempski et al. | Aug 2004 | A1 |
| 20040193413 | Wilson et al. | Sep 2004 | A1 |
| 20050104850 | Hu et al. | May 2005 | A1 |
| 20050259035 | Iwaki et al. | Nov 2005 | A1 |
| 20060010400 | Dehlin et al. | Jan 2006 | A1 |
| 20060033713 | Pryor | Feb 2006 | A1 |
| 20060044265 | Min | Mar 2006 | A1 |
| 20060168531 | Sato | Jul 2006 | A1 |
| 20080276184 | Buffet et al. | Nov 2008 | A1 |
| 20090079813 | Hildreth | Mar 2009 | A1 |
| Entry |
|---|
| A Prototype Hand Geometry-based Veri—cation System Anil K. Jain & Arun Ross Sharath Pankanti pp. 166-171, Mar. 22-24, 1999. |
| Engadget, Headtracking, 1 page, http://www.engadget.com/2007/12/21/diy-head-tracker-takes-wiimote-hacking-to-dizzying-new-heights/, as accessed on Aug. 4, 2010. |
| Rationalcraft, Winscape, 3 pages, http://rationalcraft.com/Winscape.html,as accessed on Aug. 6, 2010. |
| Gettys, J. “SNAP Computing and the X Window System”. Proceedings of the Linux Symposium, vol. 1. Jul. 20-23, 2005. Ottawa, Canada. |
| Gesturetek, GestPoint, 1 page, http://www.gesturetek.com/gestpoint/holopttrackingfrm.php, as accessed on Apr. 22, 2010. |
| Gesturetek, Gesturetek Tradeshow Demo, 1 page, http://www.youtube.com/watch?v=BrvtvfM-WCw, as accessed on Apr. 22, 2010. |
| EON, TouchLight, 1 page, http://www.youtube.com/watch?v=DTMLdjVoLQw, as accessed on Apr. 22, 2010. |
| Atlas Gloves, Atlas Gloves Demo, 1 page, http://atlasgloves.org/demo, as accessed on Apr. 22, 2010. |
| Oblong Industries, G-Speak, 1 page, http://www.youtube.com/watch?v=dyMVZqJk8s4, as accessed on Apr. 22, 2010. |
| Jeff Han, Multi-Touch Sensing, 1 page, http://www.youtube.com/watch?v=zwGAKUForhM, as accessed on Apr. 22, 2010. |
| Toshiba, Gesture Interface Demo, 1 page, http://www.youtube.com/watch?v=RL9MpXhWCrQ, as accessed on Apr. 22, 2010. |
| Engadget, Winscape Virtual Window, 1 page, http://www.engadget.com/2010/04/15/winscape-virtual-window-features-wiimote-headtracking-absolutel/, as accessed on Apr. 30, 2010. |
| Number | Date | Country | |
|---|---|---|---|
| 20110197263 A1 | Aug 2011 | US |
