WO2018057533A1 - Système multi-utilisateur et interface - Google Patents

Système multi-utilisateur et interface Download PDF

Info

Publication number
WO2018057533A1
WO2018057533A1 PCT/US2017/052329 US2017052329W WO2018057533A1 WO 2018057533 A1 WO2018057533 A1 WO 2018057533A1 US 2017052329 W US2017052329 W US 2017052329W WO 2018057533 A1 WO2018057533 A1 WO 2018057533A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
touch
interface
control
visual indication
Prior art date
Application number
PCT/US2017/052329
Other languages
English (en)
Original Assignee
Segame Technologies Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Segame Technologies Llc filed Critical Segame Technologies Llc
Publication of WO2018057533A1 publication Critical patent/WO2018057533A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/10—Input arrangements, i.e. from user to vehicle, associated with vehicle functions or specially adapted therefor
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
    • B60K35/65—Instruments specially adapted for specific vehicle types or users, e.g. for left- or right-hand drive
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2360/00—Indexing scheme associated with groups B60K35/00 or B60K37/00 relating to details of instruments or dashboards
    • B60K2360/11—Instrument graphical user interfaces or menu aspects
    • B60K2360/111—Instrument graphical user interfaces or menu aspects for controlling multiple devices
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2360/00—Indexing scheme associated with groups B60K35/00 or B60K37/00 relating to details of instruments or dashboards
    • B60K2360/143—Touch sensitive instrument input devices
    • B60K2360/1438—Touch screens
    • B60K2360/1442—Emulation of input devices
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K2360/00—Indexing scheme associated with groups B60K35/00 or B60K37/00 relating to details of instruments or dashboards
    • B60K2360/741—Instruments adapted for user detection

Definitions

  • Conventional user interfaces for system(s) typically provide one set of controls that globally control one or more parameters of the system(s) being controlled, for example volume for an audio system, or temperature or fan speed for an HVAC system.
  • system(s) that provide multi-zone or multi-user support for example multi-zoned HVAC or audio systems
  • conventional user interfaces typically provide two or more sets of controls, with one set corresponding to each zone or user. For example, in an application with separate HVAC zones for two users, there may be two sets of HVAC controls, with one set for each zone/user.
  • Embodiments of methods and systems are described that provide multi-user interfaces for controlled system(s).
  • a multi-user system and graphical user interface are described that provide a method of controlling one or more features of the system using a graphical user interface affordance that provides visual indications of the features, possible feature settings, and at least two current settings or states for the features.
  • a detection mechanism may be used to detect a particular user that is currently interacting with the system.
  • the graphical user interface may be adapted to that user, for example by adapting controls and/or indicators of the interface to be specific to the user. Interactions with the interface by a particular user are applied by the system to state(s) of one or more controlled systems that are specific to that user.
  • the multi-user system may include a touch- or multitouch- enabled screen or panel that displays graphical and/or textual user interface elements including but not limited to control elements (buttons, dials or knobs, sliders, radio buttons, check boxes, scroll bars, etc.) and indicator elements (e.g., graphical and/or textual indications of current states for the controlled system(s)).
  • control elements buttons, dials or knobs, sliders, radio buttons, check boxes, scroll bars, etc.
  • indicator elements e.g., graphical and/or textual indications of current states for the controlled system(s)
  • the multi-user interface may instead or also include physical controls such as mechanical buttons, dials, knobs, joysticks, switches, and/or sliders.
  • At least some of the controls are multi-user, multi-state controls.
  • at least some of the controls may be stateful, with a current state of the controls being determined by detection of a current user that is interacting with the interface; the current state of the controls may be set to states for the controls that are specific to the current user.
  • state here refers to the states of settings or input parameters for one or more controlled systems that correspond to the controls on the multi-user interface.
  • temperature and fan speed may be settings for two or more zones in an HVAC system
  • a first user's states for those settings in their zone may be 68 degrees and 4 on a scale from 0 (off) to 5 (high)
  • a second user's states for those settings in their zone may be 72 degrees and 2 on a scale from 0 (off) to 5 (high).
  • a single set of controls may be provided for a controlled system, and the controls may be modified for or adapted to a particular user/zone upon detecting that the user is interacting with the graphical user interface, for example by associating the states that are specific to that user/zone with the controls.
  • Inputs to the control(s) via the graphical user interface by the user may then be applied to the settings for the controlled system that are specific to the particular user/zone.
  • FIG. 1 graphically illustrates a multi-user system or device that includes a multi-user interface with stateful controls for controlling one or more systems, according to some embodiments.
  • FIG. 2A is a high-level flowchart of a method of providing stateful controls for controlled systems on a multi-user interface, according to some embodiments.
  • FIG. 2B is a flowchart of a method of operation for a multi-user system, according to some embodiments.
  • FIG. 2C is a flowchart of a method of operation for a multi-state control, according to some embodiments.
  • FIG. 3 illustrates an example multi-user interface in default neutral mode, according to some embodiments.
  • FIGS. 5A through 5E illustrate a multi-user interface that includes one or more multiuser, multi-state controls as illustrated in FIGS. 4A through 4F, according to some embodiments.
  • FIGS. 6A through 6G illustrate a multi-user interface that includes one or more multiuser, multi-state controls as illustrated in FIGS. 4G through 41, according to some embodiments.
  • FIGS. 7A through 7D illustrate a multi-user interface that includes one or more multiuser, multi-state controls as illustrated in FIGS. 4J through 4L, according to some embodiments.
  • FIGS. 8A and 8B illustrate a multi-user interface that includes another variation of multi-user, multi-state controls, according to some embodiments.
  • FIGS. 9A through 9E illustrate a multi-user interface that includes yet another variation of multi-user, multi-state controls, according to some embodiments.
  • FIGS. 10A through 10E illustrate an example multi-user interface in which at least a portion of the interface may be adapted to a particular user, according to some embodiments.
  • FIG. 11 illustrates a variation of a multi-user interface as illustrated in FIGS. 10A through 10E, according to some embodiments.
  • FIGS. 12A through 12C illustrate a multi-user interface for a multi-user system that includes physical controls, according to some embodiments.
  • FIG. 13 illustrates another type of multi-user, multi-state control element on an example multi-user interface, according to some embodiments.
  • FIG. 14 illustrates binary multi-state control elements of a multi-user interface, according to some embodiments.
  • FIGS. 15A through 15D illustrate controls of a multi-user interface that provide exclusive access to particular users, according to some embodiments.
  • FIG. 16 illustrates an interface for a multi-user system in which each user has exclusive access to a portion or region of the interface, according to some embodiments.
  • FIGS. 17A and 17B illustrate an interface for a multi-user system in which a user is granted exclusive access to the interface, according to some embodiments.
  • Embodiments of methods and systems are described that provide multi-user interfaces for controlled system(s).
  • a multi-user system and graphical user interface are described that provide a method of controlling one or more features of the system using a graphical user interface affordance that provides visual indications of the features, possible feature settings, and at least two current settings or states for the features.
  • Conventional user interfaces provide one set of controls and indicators that globally control and indicate one or more parameters of the controlled system(s), or alternatively two or more sets of controls and indicators, with each set of controls and indicators corresponding to a different zone or user. For example, in an application with separate HVAC zones for two users, there may be two sets of HVAC and/or audio controls and indicators, with one set for a first zone/user and a second set for a second zone/user.
  • a detection mechanism implemented according to sensing technology may be used to detect a particular user that is currently interacting with the system.
  • the interface Upon detecting interaction by a particular user, the interface is adapted to that user, for example by adapting controls and/or indicators of the interface to be specific to the user. Interactions with the interface by a particular user are applied by the system to state(s) of one or more controlled systems that are specific to that user.
  • Embodiments of the multi-user system and interface may thus adapt the paradigm of direct- manipulation graphical user interface (GUI) controls (whose representation mimics the state of the system(s) under control) in a paradigm where multiple states may be represented and manipulated by each control while maintaining the property of direct manipulation.
  • GUI direct- manipulation graphical user interface
  • the multi-user system may include a touch- or multitouch- enabled screen or panel that displays a graphical user interface including graphical and/or textual user interface elements, the user interface elements including but not limited to control elements (buttons, dials or knobs, sliders, radio buttons, check boxes, scroll bars, trackpads, gestures, etc.) and indicator elements (e.g., graphical and/or textual indications of current states for the controlled system(s)).
  • the multi-user interface may instead or also include physical controls such as mechanical buttons, dials, knobs, joysticks, switches, and/or sliders.
  • At least some of the controls and/or indicators of the multi-user interface may be stateful, with a current state of the controls and/or indicators for a controlled system being determined by detection of a current user that is interacting with the interface; the current state of the controls may be set to states for the controls that are specific to the current user.
  • state here refers to the states of settings or input parameters for the controlled systems that correspond to the controls and/or indicators of the multi-user interface.
  • temperature may be a setting for an HVAC system
  • the current state of the temperature setting for a first user/zone may be 68°
  • the current state of the temperature setting for a second user/zone may be 72°.
  • a single set of controls may be provided, and the controls may be modified for or adapted to a particular user/zone upon detecting that the user is interacting with the user interface, for example by associating the states that are specific to that user/zone with the controls.
  • the controls are multi-user, multi-state controls.
  • a single set of controls may be provided for a controlled system (e.g., an HVAC system, audio system, etc.), and the controls may be modified for or adapted to a particular user (e.g., to show the current user and/or current state(s) for the user) upon detecting that the user is interacting with the user interface.
  • Inputs to the control(s) via the interface by the user may then be applied to the settings for controlled system(s) that are specific to the particular user. For example, in a zoned
  • HVAC system with two zones corresponding to two users, a first user's interactions with the single set of HVAC control(s) on the interface affect HVAC settings (e.g., temperature or fan speed) for the first user's zone, and likewise the second user's interactions with the single set of
  • HVAC control(s) on the interface affect HVAC settings for the second user's zone.
  • the controls may be modified for or adapted to that user (e.g., to show the current state(s) for that user's zone), and inputs to the control(s) via the interface by that user may then be applied to the settings for controlled system(s) that are specific to that user.
  • a multi-user interface may include one or more exclusive controls.
  • An exclusive control is only active for one of the users (the exclusive user).
  • the system responds to interactions with the exclusive control by the exclusive user by performing some action, for example changing a setting associated with the control. In some embodiments, if another user attempts to interact with the exclusive control, the action is not performed.
  • visual, haptic, and/or aural feedback may be provided to indicate to the other user that the user does not have access to that control. Multi-user system
  • FIG. 1 graphically illustrates a multi-user system 10 or device that includes a multiuser interface 100 with stateful controls for controlling one or more systems 188, according to some embodiments.
  • multi-user system 10 may include a detection mechanism 180, a control module, component, or device (referred to as controller 170), a multiuser interface 100, and one or more controlled systems 188.
  • the system 10 may be integrated in an environment with multi-user interface 100 located between user 190A and user 190B, and controlled systems 188 may include one or more of, but not limited to, a media system and an HVAC system for the environment.
  • system 10 is not limited to integrated systems in environments.
  • multi-user system 10 may include a mobile multipurpose device (e.g., a pad, tablet, or smartphone device) that provides a multi-user interface 100 as described herein, and controlled systems 188 may include components or applications of the device and/or controlled systems 188 external to the device.
  • Controller 170 may include, but is not limited to, one or more processors 182 and a memory 184. Controller 170 may also be referred to as Memory 184 may store various code and/or data used by system 10, including but not limited to the current states for the users, user profiles and/or preferences, media files, playlists, graphics, themes, and multi-user system 10 software executable by the processor(s) 182.
  • the multi-user interface 100 may include a touch- or multitouch-enabled screen or panel that displays one or more graphical and/or textual user interface (UI) elements 102 including but not limited to control elements (buttons, dials or knobs, sliders, radio buttons, check boxes, scroll bars, etc.) and indicator elements (e.g., graphical and/or textual indications of current states for the controlled system(s)).
  • UI graphical and/or textual user interface
  • the multi-user interface 100 may instead or also include physical controls such as mechanical buttons, dials, knobs, switches, joysticks, and/or sliders.
  • UI elements 102 and/or physical controls are stateful, multi-user controls, with a single set of controls provided for a controlled system 188.
  • UI elements 102 may include stateful, with a current state of the controls and/or indicators for a controlled system 188 corresponding to a user (e.g., left user 190A or right user 190B) that is current interacting with the interface 100.
  • System 10 may include a detection mechanism 180 that detects interactions with interface 100, determines which user (e.g., left user 190A or right user 190B) is interacting with interface 100, and signals controller 170 to indicate the user that is currently interacting with interface 100.
  • a detection mechanism 180 that detects interactions with interface 100, determines which user (e.g., left user 190A or right user 190B) is interacting with interface 100, and signals controller 170 to indicate the user that is currently interacting with interface 100.
  • Any of various sensing technologies for example camera/image processing, haptic, or electromagnetic technologies, or combinations thereof, may be used by the detection mechanism 180 to detect interactions and determine which user is interacting.
  • detection mechanism 180 may detect that a particular user's hand is approaching, proximate to, or touching the screen on which interface 100 is displayed, or that the particular user's hand is approaching, proximate to, or touching a physical control (e.g., a dial, knob, joystick, etc.) of the interface 100, and in response generate a signal to controller 170 indicating the particular user.
  • a physical control e.g., a dial, knob, joystick, etc.
  • current state of UI elements 102 is determined by the detection, by detection mechanism 180, of the particular user (e.g., 190A or 190B) that is interacting with the interface 100.
  • controller 170 may set one or more UI elements 102 according to the detected user (e.g., to indicate the current user and/or current state(s) for the user). Inputs to the UI elements 102 via the interface 100 by the user may then be processed and applied to the settings for controlled system(s) 188 that are specific to the particular user.
  • a first user's interactions with the single set of HVAC control(s) on the interface 100 affect HVAC settings (e.g., temperature or fan speed) for the first user's zone, and likewise a second user's interactions with the single set of HVAC control(s) on the interface 100 affect HVAC settings for the second user's zone.
  • HVAC settings e.g., temperature or fan speed
  • a second user's interactions with the single set of HVAC control(s) on the interface 100 affect HVAC settings for the second user's zone.
  • one or more UI elements 102 may be modified for or adapted to that user (e.g., to show the current state(s) for that user), and inputs to the one or more UI elements 102 via the interface 100 by that user may then be applied to the settings for controlled system(s) 188 that are specific to that user.
  • FIG. 2A is a high-level flowchart of a method of providing stateful controls for controlled systems on a multi-user interface, according to some embodiments.
  • the multi-user system may provide one set of controls that is shared by two or more users; the controls are adapted according to a user's state(s) for controlled system(s) upon detecting that the user is currently interacting with the interface.
  • the method of FIG. 2A may, for example, be implemented by a multi-user system 10 as illustrated in FIG. 1.
  • a user interaction with the interface by a particular user may be detected.
  • the detection mechanism may detect that a user's hand is reaching for, proximate to, or touching the interface.
  • the detection mechanism includes functionality that allows it to identify which of the users (e.g., either the left user or the right user) is interacting with the interface.
  • the state(s) of controls(s) on the interface may be set according to the particular user.
  • a control with which the user is interacting may be set to the state of a setting for a zone of a controlled system that corresponds to the detected user.
  • the control(s) and interface may be set or adapted according to the detected user.
  • FIGS. 4A through 15D show various examples of ways in which the multi-user interface and controls on the interface may be set or adapted for particular users and user interactions that are detected.
  • user input to a control may be detected and applied to the state of a controlled system corresponding to the detected user.
  • the controlled system corresponding to a manipulated control may be directed to change a respective setting for the particular user. For example, if the control is a volume control for a zoned audio system, then the audio system may be directed to change the volume for the user's zone as indicated by the user, for example by playing audio at a first output level through one or more speakers in the user's zone while playing audio at a second output level through one or more other speakers in another zone.
  • the HVAC system may be directed to change the temperature for the user's zone as indicated by the user, for example by heating or cooling the user's zone to a first temperature level while heating or cooling another zone to a second temperature level.
  • FIG. 2B is a flowchart of a method of operation for a multi-user system, according to some embodiments.
  • the method of FIG. 2B may, for example, be implemented by a multi-user system 10 as illustrated in FIG. 1.
  • FIG. 2B uses an example in which there is a left user and a right user for illustrative purposes.
  • embodiments of a multi-user system are not limited to this example scenario; for example, some embodiments of a multi-user system and interface may support more than two users.
  • the multi-user interface may initially be set to a default, neutral mode, for example as illustrated in FIG. 3.
  • a user interaction with the interface by a particular one of the two users may be detected.
  • the detection mechanism may detect that a user's hand is reaching for, proximate to, or touching the interface.
  • the detection mechanism includes functionality that allows it to identify which of the users (either the left user or the right user) is interacting with the interface.
  • the detection mechanism may then signal control software of the multi-user system executing on one or more processor(s) to indicate the interaction; the signal identifies which of the two users is interacting.
  • the multi-user system may then react according to the particular user that is currently interacting with the system, for example as shown in elements 224-246.
  • the control software sets the interface for the left user.
  • the interface may be set to "glow" on the left side (the side of the current user); the interface may be set to a different color or tint to indicate the left user; a name, icon, avatar, or picture corresponding to the left user may be displayed; or other methods of indicating the current user may be employed.
  • the screen may be turned or tilted towards the left user.
  • one or more of the UI elements on the interface may be set for the left user.
  • one or more indicators may be set to indicate the state(s) of the settings for the left user for one or more controlled systems that correspond to the controls and/or indicators of the multi-user interface.
  • a textual and/or graphical indicator may be displayed that indicates that current setting for the left user.
  • a control UI element may be changed to show the current state of the setting corresponding to that control; the user may manipulate the control UI element to change their state.
  • a graphical indicator e.g., a slider
  • the control UI element may be displayed for the control that indicates that current volume for the left user; the user may manipulate the control UI element by sliding the slider thumb left or right on the slider bar or track to change the volume.
  • one or more of the UI elements of the interface may be binary multi-state control elements (e.g., UI element 318 of FIG. 3; also see FIG. 14); a binary multi-state control element may be set to indicate the current state (e.g., on or off) of the binary UI element for the users.
  • one or more of the UI elements of the interface may be stateless global control elements (e.g., UI element 312-316 of FIG. 3); a global control element shows and controls a global state (e.g., pause or play for an audio system) for a controlled system 188.
  • FIGS. 4A through 15D show various examples of ways in which the multi-user interface and/or UI elements of the interface may be set or adapted for particular users and user interactions that are detected.
  • the control software may receive an indication of a manipulation of a control UI element of the interface by the left user via the touch-enabled screen.
  • the control UI element is a slider (e.g., as illustrated in FIGS. 4A-4B) that controls volume setting for an audio system
  • the user may manipulate the control UI element by sliding the slider thumb left or right on the slider track to change the volume.
  • the control UI element is a virtual dial or knob (e.g., as illustrated in FIG. 8B) or a physical control (e.g., a mechanical dial or knob as illustrated in FIG.
  • the user may manipulate the control UI element by rotating it left or right to change the volume.
  • one or more of the UI elements of the interface may be binary multi-state control elements (e.g., UI element 318 of FIG. 3; also see FIG. 14), and the left user may manipulate a binary UI element by touching and releasing the displayed UI element to change its state (e.g. on »> off or off »> on for the left user).
  • the control software may signal a controlled system corresponding to a manipulated UI element to indicate a change that was input by the left user to a state corresponding to the UI element. For example, if the UI element corresponds to volume control for an audio system, then the control software may signal the audio system to indicate a change in volume as indicated by the user. As another example, if the UI element corresponds to a fan speed control of an HVAC system, then the control software may signal the HVAC system to indicate a change in fan speed as indicated by the user.
  • the method returns to element 220; the interface is reset to the neutral mode, and the system waits until another user interaction (by either the left or the right user) with the interface is detected. In some embodiments, there may be a pause of a few seconds in which the interface remains set for the left user in case the user wants to continue interacting with the interface; after the pause, the interface resets to the neutral mode.
  • the method returns to element 232 to receive and process additional interactions by the left user.
  • the control software sets the interface for the right user, for example by setting the interface to "glow" on the right side and displaying or changing one or more indicators to indicate the state(s) of the settings for the right user.
  • the screen may be turned or tilted towards the right user.
  • the system may then receive 242 and process 244 interactions with the interface by the right user until the right user is done 246 as described above in reference to elements 232 through 236.
  • one or more UI elements may be displayed for a user that are not displayed for the other user. For example, some controls or indicators may only be displayed for the left user, or conversely some controls or indicators may only be displayed for the right user.
  • one or more UI elements that are displayed may be exclusive controls that are only active for (and thus may only be manipulated by) one or the other user. For example, in a system with a video (e.g., DVD) player as one of the controlled systems, video controls may only be displayed for, or alternatively may only be active for, one of the two users.
  • video e.g., DVD
  • the multi-user system may support concurrent interactions by more than one user with the multi-user interface.
  • the system may detect interactions by two users at the same time, detect which part of the interface (e.g., which control) the users are interacting with, and react accordingly, for example by setting the states for the respective controls according to the particular users interacting with the controls.
  • the left user may reach for the interface to adjust the volume for their zone of an audio system; the system detects that the interaction is by the left user, sets the volume control UI element according to the left user's current state for volume, and responds to input to the control by the left user by appropriately adjusting the volume setting for the left zone of the audio system.
  • the right user While the left user is interacting with the volume control UI element, the right user may reach for the interface to adjust the temperature for their zone of an HVAC system; the system detects that the interaction is by the right user, sets the temperature control UI element according to the right user's current state for temperature, and responds to input to the control by the right user by appropriately adjusting the temperature setting for the right zone of the HVAC system.
  • a multi-user system as illustrated in FIGS. 1 and 2 may include a touch- or multitouch-enabled screen or panel that displays graphical and/or textual user interface elements including but not limited to control elements (buttons, dials, knobs, sliders, radio buttons, check boxes, scroll bars, etc.) and indicator elements (e.g., graphical and/or textual indications of current states for the controlled system(s)).
  • the multi-user interface may instead or also include physical controls such as mechanical buttons, dials, knobs, joysticks, switches, and/or sliders.
  • a control In conventional user interface (UI) paradigms, a control both manipulates state (e.g., a current temperature or volume setting) and shows the state at the same time. For example, an interface may provide a slider control that goes from 0 to 10; the state may currently be shown at 5. A user may grab the slider at 5, move it to 7, and the control then shows a state of 7.
  • a control In conventional UI paradigms, a control only supports one state; to support systems (e.g. HVAC systems) with multiple zones and thus multiple states, a typical solution is to provide multiple controls, with one control for each zone and thus each state.
  • Embodiments of a multi-user interface for a multi-user system as illustrated in FIGS. 1 and 2 are described that include multi-user, multi-state UI elements.
  • the controls are multi-user, multi-state controls.
  • a single set of controls may be provided for a controlled system (e.g., an HVAC system, audio system, etc.), and the controls may be modified for or adapted to a particular user (e.g., to show the current user and/or current state(s) for the user) upon detecting that the user is interacting with the user interface.
  • Inputs to the control(s) via the interface by a particular user may then be applied to the settings for controlled system(s) that are specific to the particular user.
  • the controls and/or indicators of the multi-user interface are stateful, with a current state of the controls and/or indicators for a controlled system being determined by detection of a current user that is interacting with the interface.
  • state here refers to the settings for the controlled system(s) that correspond to the controls and/or indicators of the multi-user interface.
  • the current state of a temperature control for a first user may be 68°
  • the current state of the temperature control for a second user may be 72°.
  • FIG. 2C is a flowchart of a method of operation for a multi-state control, according to some embodiments.
  • the method of FIG. 2C may, for example, be implemented by a multi-user system 10 as illustrated in FIG. 1.
  • a multi-user system may maintain states for a setting of a controlled system for two or more users or zones.
  • a multi-user interface that displays a multi-state control for the setting may initially be set to a default, neutral mode, for example as illustrated in FIG. 3.
  • a default mode for example as illustrated in FIG. 3.
  • no states may be displayed, or alternatively the respective states for each of the users/zones may be displayed.
  • the multi-user interface may be changed to visually indicate a user's respective state for the setting in response to detecting an interaction with the multi-state control by the user, for example by displaying a graphical or textual indication of the user's state for the setting on the multi-user interface. For example, if no states are displayed in neutral mode, the user's state may be visually indicated. As another example, if the respective states for each of the users/zones is displayed in neutral mode, the state(s) of other user(s) may be hidden, and/or the state of the user that is interacting with the control may be highlighted or expanded.
  • the visual indication of the user's respective state may be changed according to the interaction to indicate the new state, and the controlled system may be directed to adjust the setting for the user according to the new state.
  • the multi-user interface may be reset to the neutral mode in response to determining that the user is no longer interacting with the multi-state control. The method may then return to element 274 if an interaction by one of the users is detected.
  • Figures 3 through 15 show several non-limiting examples of various multi -user/multi- state user interface elements and techniques of a multi-user interface that may be used in a multiuser system, for example as illustrated in FIGS. 1 and 2. While some of these examples (e.g., FIGS. 4A-4I) show user interface elements (e.g., sliders) that are oriented horizontally, other orientations may be used, such as vertical sliders.
  • user interface elements e.g., sliders
  • FIG. 3 illustrates an example multi -user interface 300 in default neutral mode, according to some embodiments.
  • the UI elements of interface 300 may be binary multi-state control elements; a binary multi-state control element may be set to indicate the current state (e.g., on or off) of the binary UI element for both users.
  • FIG. 3 illustrates a "heart" or "like" UI element 318 that may be used to indicate which user(s) like a current title being played by an audio system. As shown in FIG.
  • the UI element may have a binary state that shows whether neither user has “liked” the title, whether one or the other user has “liked” the title, or whether both users have liked the title.
  • the multi-user system may detect which user interacts with a binary multi- state control element, and in response change state of the element accordingly.
  • one or more of the UI elements of interface 300 may be global control elements (e.g., UI element 312-316 of FIG. 3).
  • a global control element may, for example, show and control a global state for a controlled system (e.g., pause or play 314, reverse 312, or forward 316 controls for an audio system).
  • the controls on interface 300 may be multiuser, multi-state controls.
  • a single set of multi-user controls may be provided for one or more controlled systems (e.g., a zoned HVAC system and/or zoned audio system).
  • one or more of the multi-user controls may be modified for or adapted to a particular user (e.g., to show the current user and/or current state(s) for the user) upon detecting that the user is interacting with the interface 300.
  • Inputs to the multi-user control(s) via the interface 300 by the user may then be applied to the settings for controlled system(s) that are specific to the particular user.
  • a first user's interactions with the single set of multi-user HVAC controls (e.g., fan control 350 and temperature control 370) on the interface 300 affect HVAC settings (e.g., temperature or fan speed) for the first user's zone
  • HVAC settings e.g., temperature or fan speed
  • the a first user's interactions with the single set of multi-user audio controls (e.g., volume control 330) on the interface 300 affect audio settings (e.g., volume) for the first user's zone, and likewise a second user's interactions with the single set of mule-user audio controls on the interface 300 affect audio settings for the second user's zone.
  • the multi-user controls may be modified for or adapted to that user (e.g., to show the current state(s) for that user), and inputs to the controls via the interface 300 by that user may then be applied to the settings for controlled systems that are specific to that user.
  • At least some of the controls on interface 300 may be stateless multi-user controls that do not affect a state of a controlled system, but that instead perform some function that may be specific to the user that is interacting with the control.
  • element 320 illustrates an "add to playlist" UI element that, when selected by a particular user, adds a title being played to that user's playlist.
  • interface 300 may, but does not necessarily, include one or more graphics and/or textual UI elements (e.g., elements 302 and 304).
  • element 304 may indicate a current title being played by the audio system, and may also indicate other information such as the artist and album.
  • element 302 may display graphics such as cover art of an album on which the current title being played appears.
  • one or more of these graphics and/or textual UI elements may be multi-user, interactive elements. For example, selection of element 302 by a particular user may cause that user's playlist to be displayed. The user can then select the "add to playlist" element 320 to add the current title being played by the audio system to the user's displayed playlist. As another example, the user (or the other user) may select a title from their displayed playlist to play the title on the audio system.
  • FIGS. 4A through 4L illustrate several alternative examples of multi-user, multi-state controls that may be used in an interface 400 for a multi-user system, according to some embodiments.
  • a multi-user volume control 430 is used; however, note that similar controls may be used for other settings and/or other controlled systems.
  • FIGS. 4 A through 4F illustrate a multi-user control 430 of an interface 400 that, when selected by a particular user 490 (left user 490A or right user 490B, in this example), shows a UI element (e.g., slider track) 432 that is set to and visually indicates the current state of a respective setting (e.g., volume) for the particular user 490.
  • the user 490 may then adjust the state (e.g., volume) by moving the control 430 (also referred to as the slider thumb) left or right on the slider track 432.
  • the control 430 also referred to as the slider thumb
  • the UI element 432 may disappear, and the control 430 may return to its default position.
  • FIG. 4 A shows interface 400 with control 430 in a default neutral mode (i.e., the state of the interface 400 when there is no user currently detected as interacting with the interface 400).
  • the background of interface 400 may, for example, be in a uniform color and/or pattern that does not visually indicate that a particular user is interacting with the interface 400.
  • Control 430 may, for example, be displayed in the default condition as a "button" in a default position (e.g., at or near the horizontal center of the screen). While the control 430 is shown as being circular with a graphic indicating of what the control 430 is for, note that various shapes, sizes, and textual and/or graphical indications may be used.
  • a UI element 432A e.g., a slider track
  • the slider track 432A is shifted to the left with respect to control 430's default position. Assuming a volume range of 0 to 10, this may indicate that user 490A's volume is currently set to about 7.
  • the interface 400 may change to indicate that the left user 490A is currently interacting with the interface 400, for example by "glowing" on the left side of the screen as shown in FIGS. 4B and 4C.
  • FIG. 4C shows interface 400 as user 490 A interacts with control 430 to change the volume setting by sliding control 430 to the left along slider track 432A. For example, assuming a volume range of 0 to 10, this motion may lower the user 490A's volume setting to about 3. Note that slider track 432A remains stationary.
  • FIG. 4D shows interface 400 with control 430 upon detecting that left user 490A has released control 430.
  • the interface 400 may return to the default neutral mode when there is no user currently detected as interacting with the interface 400.
  • the background of interface 400 may, for example, return to its uniform color and/or pattern that does not visually indicate that a particular user is interacting with the interface 400.
  • Slider track 432A may disappear, and control 430 may return to its default condition as a "button" in its default position (e.g., at or near the horizontal center of the screen).
  • the interface 400 when user 490 A releases the control 430, there may be a pause of a few seconds in which the interface 400, control 430, and slider track 432 A remain as shown in FIG. 4C in case the user 490 A wants to continue interacting with the interface 400, for example by re-adjusting the volume setting; after the pause, the interface 400 is reset to the default neutral mode as shown in FIG. 4D.
  • FIG. 4E shows interface 400 with control 430 upon detecting that right user 490B has selected control 430, for example by touching control 430 with a finger.
  • a UI element 432B may be displayed that visually indicates the current state of the setting (e.g., volume setting) for the user 490B.
  • the slider track 432B is shifted to the right with respect to control 430's default position. Assuming a volume range of 0 to 10, this may indicate that user 490B's volume is currently set to about 2.
  • the interface 400 may change to indicate that the right user 490B is currently interacting with the interface 400, for example by "glowing" on the right side of the screen as shown in FIGS. 4E and 4F.
  • FIG. 4F shows interface 400 as user 490B is interacting with control 430 to change the volume setting by sliding control 430 to the right along slider track 432B. For example, assuming a volume range of 0 to 10, this motion may raise the user 490B's volume setting to about 5. Note that slider track 432B remains stationary. When user 490B releases control 430, interface 400 and control 430 return to the default condition as described in reference to FIG. 4D.
  • FIGS. 4G through 41 illustrate another example multi-user control 430 of an interface
  • a UI element e.g., bar
  • the track 436 is not shifted left or right on the screen relative to the control 430 to visually indicate the current state for the current user 490; instead, the center position of the track 436 is set to correspond to the current user's state for the setting, the left portion of the track 436 corresponds to the range below the current state, and the right portion of the track 436 covers the range above the current state.
  • the left portion or the right portion may not correspond to a respective lower or upper portion of the range for the setting if the user's state is at minimum or maximum for the setting when control 430 is selected.
  • a visual indication of the current state may also be provided.
  • the user 490 may then adjust their state (e.g., volume level for their zone) by sliding the control 430 left or right on the slider track 436; the visual indication of the state may change as the control is moved left or right.
  • the UI element 432 may disappear, and the control 430 may return to its default position.
  • FIG. 4G shows interface 400 with control 430 in a default neutral mode (i.e., the state of the interface 400 when there is no user currently detected as interacting with the interface 400).
  • FIG. 4H shows interface 400 with control 430 upon detecting that left user 490 A has selected control 430, for example by touching control 430 with a finger.
  • the interface 400 may change to indicate that the left user 490A is currently interacting with the interface 400, for example by "glowing" on the left side of the screen as shown in FIG. 4H.
  • a bar or track 436 may be displayed that is set according to the current state of a respective setting (e.g., volume) for the detected user 490 A.
  • a visual indication of the current state for user 490A may be displayed graphically and/or textually on interface 400.
  • FIG. 4H shows the current state displayed as a number "2" above the control 430.
  • the user 490A may then adjust their state (e.g., volume level for their zone) by sliding the control 430 left or right on the track 436. If present, the visual indication of the state may change respectively as the control 430 is moved left or right.
  • the UI element 436 (and state, if displayed) may disappear, and the interface 400 and control 430 may return to the default as shown in FIG. 4G.
  • FIG. 41 shows interface 400 with control 430 upon detecting that right user 490B has selected control 430, for example by touching control 430 with a finger.
  • the interface 400 may change to indicate that the left user 490B is currently interacting with the interface 400, for example by "glowing" on the right side of the screen as shown in FIG. 41.
  • bar 436 may be displayed and set according to the current state of a respective setting (e.g., volume) for the detected user 490B.
  • a visual indication of the current state for user 490B may be displayed graphically and/or textually on interface 400.
  • FIG. 41 shows the current state displayed as a number "7" above the control 430.
  • the user 490A may then adjust their state (e.g., volume level for their zone) by sliding the control 430 left or right on the track 436. If present, the visual indication of the state may change respectively as the control 430 is moved left or right.
  • the UI element 436 (and state, if displayed) may disappear, and the interface 400 and control 430 may return to the default as shown in FIG. 4G.
  • FIGS. 4 J through 4L illustrate another example multi-user control 430 of an interface 400 that, in its default neutral mode, shows UI elements 434 that visually indicate the current states of the respective setting (e.g., volume) for both users 490.
  • control 430 is selected by a particular user 490 (left user 490A or right user 490B, in this example), the UI element 434 corresponding to the other user 490 disappears, and the UI element 434 corresponding to the detected user 490 "unrolls" for control 430.
  • the user 490 may then adjust their state (e.g., volume level for their zone), for example by sliding the control 430 left or right on the display or by a clockwise or counterclockwise circular motion as if they are rotating a dial or knob; the visual indication of the state may change correspondingly as the control is manipulated.
  • their state e.g., volume level for their zone
  • the UI element 432 may disappear, and the interface 400 and control 430 may return to the default neutral mode.
  • FIG. 4J shows interface 400 with control 430 in a default neutral mode (i.e., the state of the interface 400 when there is no user currently detected as interacting with the interface 400).
  • Control 430 may be a graphical representation of a knob or dial.
  • UI elements 434A and 434B visually indicate the current states of the respective setting (e.g., volume) for left and right users 490A and 490B, respectively.
  • FIG. 4K shows interface 400 with control 430 upon detecting that left user 490A has selected control 430, for example by touching control 430 with a finger.
  • the interface 400 may change to indicate that the left user 490A is currently interacting with the interface 400, for example by "glowing" on the left side of the screen as shown in FIG. 4K.
  • UI element 434B corresponding to user 490B disappears, and UI element 434A corresponding to user 490A is "unrolled" (e.g., expanded and/or moved) with respect to control 430 to highlight or indicate that the user 490A is interacting with the control 430.
  • User 490A may then adjust their state (e.g., volume level for the left zone), for example by sliding the control 430 left or right on the display or by a clockwise or counterclockwise circular motion as if they are rotating a dial or knob; the visual indication 434A of the state may change correspondingly as the control 430 is manipulated.
  • the interface 400 and control 430 may return to the default neutral mode.
  • the interface 400 when user 490A releases the control 430, there may be a pause of a few seconds before resetting the interface 400 to the default neutral mode in case the user 490A wants to continue interacting with the interface 400, for example by re-adjusting the volume setting; after the pause, the interface 400 is reset to the default neutral mode as shown in FIG. 4J.
  • FIG. 4L shows interface 400 with control 430 upon detecting that right user 490B has selected control 430, for example by touching control 430 with a finger.
  • the interface 400 may change to indicate that the right user 490B is currently interacting with the interface 400, for example by "glowing" on the right side of the screen as shown in FIG. 4L.
  • UI element 434A corresponding to user 490A disappears, and UI element 434B corresponding to user 490B "unrolls" for control 430.
  • User 490B may then adjust their state (e.g., volume level for the left zone), for example by sliding the control 430 left or right on the display or by a clockwise or counterclockwise circular motion as if they are rotating a dial or knob; the visual indication 434B of the state may change correspondingly as the control 430 is manipulated.
  • state e.g., volume level for the left zone
  • control 430 may return to the default neutral mode. In some embodiments, when user
  • FIGS. 5 A through 9E illustrate several example variations of an example multi-user interface as illustrated in FIG. 3 that include several variations on the multi-user, multi-state controls as illustrated in FIGS. 4A through 4L, as well as other multi-users features.
  • FIGS. 5A through 5E illustrate a multi-user interface 500 that includes one or more multi-user, multi-state controls as illustrated in FIGS. 4A through 4F, according to some embodiments.
  • interface 500 includes multi-user, multi-state controls 530, 550, and 570 that, when selected by a particular user 590 (left user 590A or right user 590B, in this example), show a UI element (e.g., slider track) that is set to and visually indicates the current state of a respective setting for the particular user 590.
  • the user 590 may then adjust the state by moving the control (also referred to as the slider thumb) left or right on the slider track.
  • the control also referred to as the slider thumb
  • the interface 500 may initially be set to a default neutral mode, for example as illustrated in FIG. 5A. As shown in FIG. 5A, the interface 500 may be set to the default neutral mode when there is no user currently detected as interacting with the interface 500.
  • the background of interface 500 may, for example, be set to a uniform color and/or pattern that does not visually indicate that a particular user is interacting with the interface 500.
  • Multi-user, multi- state controls 530, 550, and 570 may be displayed in their default positions (e.g., at or near the horizontal center of the screen).
  • FIG. 5B shows interface 500 upon detecting that left user 590A has selected control 530.
  • the interface 500 may visually indicate that the left user 590A is currently interacting with the interface 500, for example by "glowing" on the left side of the screen as shown in FIG. 5B.
  • a UI element 532A may be displayed that may be shifted to the left or right with respect to control 530' s default position to visually indicates the current state of the setting (e.g., volume setting) for the user 590A.
  • the slider track 432A is shifted to the right with respect to control 530's default position. Assuming a volume range of 0 to 10, this may indicate that user 590A's volume is currently set to about 2.
  • FIG. 5C shows interface 500 as user 590 A interacts with control 530 to change the volume setting by sliding control 530 to the right along slider track 532A. For example, assuming a volume range of 0 to 10, this motion may raise the volume setting for user 490A's zone to about 7. Note that slider track 532A remains stationary.
  • interface 500 and control may return to the default neutral state as illustrated in FIG. 5A.
  • FIG. 5D shows interface 500 upon detecting that right user 590B has selected control 570.
  • the interface 500 may visually indicate that the right user 590B is currently interacting with the interface 500, for example by "glowing" on the right side of the screen as shown in FIG. 5D.
  • a UI element 532B may be displayed that may be shifted to the left or right with respect to control 570' s default position to visually indicates the current state of the setting (e.g., temperature setting) for the user 590B.
  • the slider track 432B is shifted to the left with respect to control 570' s default position.
  • the interface 500 may return to the default neutral mode as shown in FIG. 5C.
  • FIG. 5E shows interface 500 as user 590B interacts with control 570 to change the temperature setting by sliding control 570 to the left along slider track 532B. For example, assuming a temperature range of 65 to 85 degrees, this motion may lower the temperature setting for user 590B's zone to about 68 degrees. Note that slider track 532B remains stationary.
  • interface 500 and control may return to the default neutral state as illustrated in FIG. 5A.
  • FIGS. 6 A through 6G illustrate a multi-user interface 600 that includes one or more multi-user, multi-state controls as illustrated in FIGS. 4G through 41, according to some embodiments.
  • interface 600 includes multi-user, multi-state controls 630, 650, and 670 that, when selected by a particular user 690 (left user 690A or right user 690B, in this example), show a UI element (e.g., track) that is set according to the current state of a respective setting for the particular user 590.
  • a UI element e.g., track
  • the track is not shifted left or right on the screen relative to the control to visually indicate the current state for the current user 590; instead, the center position of the track is set to correspond to the current user's state for the setting, the left portion of the track corresponds to the range below the current state, and the right portion of the track covers the range above the current state.
  • the left portion or the right portion may not correspond to a respective lower or upper portion of the range for the setting if the user's state is at minimum or maximum for the setting when a control is selected.
  • a visual indication of the user 690' s current state for the respective setting may also be provided when the user 690 selects the control.
  • the user 690 may then adjust their state (e.g., volume level, fan speed, or temperature for their zone) by sliding the control left or right on the track; if displayed, the visual indication of the state may change as the control is moved left or right.
  • the track may disappear, and the control may return to its default position.
  • the interface 600 may initially be set to a default neutral mode, for example as illustrated in FIG. 6A. As shown in FIG. 6A, the interface 600 may be set to the default neutral mode when there is no user currently detected as interacting with the interface 600.
  • the background of interface 600 may, for example, be set to a uniform color and/or pattern that does not visually indicate that a particular user is interacting with the interface 600.
  • Multi-user, multi- state controls 630, 650, and 670 may be displayed in their default positions (e.g., at or near the horizontal center of the screen). In some embodiments, a visual indication of each user 490' s current state for controls 630, 650, and 670 may be displayed in the default neutral mode.
  • FIG. 6B shows interface 600 upon detecting that left user 690A has selected control 630.
  • the interface 600 may visually indicate that the left user 690A is currently interacting with the interface 600, for example by "glowing" on the left side of the screen as shown in FIG. 6 A.
  • a bar or track 636 may be displayed that is set according to the current state of a respective setting (e.g., volume) for the detected user 690A.
  • the center position of the track 636 is set to correspond to the current state for user 690 A
  • the left portion of the track 636 corresponds to the range below the current state
  • the right portion of the track 636 covers the range above the current state.
  • a visual indication of the current state for user 690A may be displayed graphically and/or textually on interface 600.
  • the user 690A may then adjust their state (e.g., volume level for their zone) by sliding the control 630 left or right on the track 636. If present, the visual indication of the state may change respectively as the control 630 is moved left or right. When the user 690A releases the control 630, bar 636 may disappear, and the interface 600 and control 630 may return to the default as shown in FIG. 6D. In FIG. 6D, the visual indication 634A of user 690A's state now shows the new volume setting for user 690A's zone.
  • their state e.g., volume level for their zone
  • the interface 600 when user 690 A releases the control 630, there may be a pause of a few seconds before resetting the interface 600 to the default neutral mode in case the user 690A wants to continue interacting with the interface 600, for example by re-adjusting the volume setting; after the pause, the interface 600 is reset to the default neutral mode as shown in FIG. 6D.
  • FIG. 6E shows interface 600 upon detecting that right user 690B has selected control 670.
  • the interface 600 may visually indicate that the right user 690B is currently interacting with the interface 600, for example by "glowing" on the right side of the screen as shown in FIG. 6E.
  • a bar or track 676 may be displayed that is set according to the current state of a respective setting (e.g., temperature) for the detected user 690B.
  • the center position of the track 676 is set to correspond to the current state for user 690B, the left portion of the track 676 corresponds to the range below the current state, and the right portion of the track 676 covers the range above the current state.
  • a visual indication of the current state for user 690B may be displayed graphically and/or textually on interface 600.
  • the user 690B may then adjust their state (e.g., temperature level for their zone) by sliding the control 670 left or right on the track 676. If present, the visual indication of the state may change respectively as the control 670 is moved left or right. When the user 690B releases the control 670, bar 676 may disappear, and the interface 600 and control 670 may return to the default as shown in FIG. 6G. In FIG. 6G, the visual indication 674B of user 690 A' s state now shows the new temperature setting for user 690B's zone.
  • their state e.g., temperature level for their zone
  • the interface 600 when user 690B releases the control 670, there may be a pause of a few seconds before resetting the interface 600 to the default neutral mode in case the user 690B wants to continue interacting with the interface 600, for example by re-adjusting the temperature setting; after the pause, the interface 600 is reset to the default neutral mode as shown in FIG. 6G.
  • FIGS. 7 A through 7D illustrate a multi-user interface 700 that includes one or more multi-user, multi-state controls as illustrated in FIGS. 4J through 4L, according to some embodiments.
  • FIGS. 7 A through 7D illustrate another example multi-user control of an interface 700 that, in its default neutral mode, may provide visual indications of the current states of the respective setting for both users 790.
  • a control is selected by a particular user 790 (left user 790A or right user 790B, in this example)
  • the visual indication of the current state corresponding to the other user 790 disappears, and a UI element corresponding to the detected user 490' s state "unrolls" for the selected control.
  • a UI element such as a slider track is not displayed as in FIGS. 5A-5E or FIGS 6A-6G.
  • the user 790 may then adjust their state, for example by sliding the control left or right on the display; the visual indication of the respective state may change correspondingly as the control is manipulated.
  • the interface 700 and controls may return to the default neutral mode.
  • the interface 700 may initially be set to a default neutral mode, for example as illustrated in FIG. 7A. As shown in FIG. 7A, the interface 700 may be set to the default neutral mode when there is no user currently detected as interacting with the interface 700.
  • the background of interface 700 may, for example, be set to a uniform color and/or pattern that does not visually indicate that a particular user is interacting with the interface 700.
  • Multi-user, multi- state controls 730, 750, and 770 may be displayed in their default positions (e.g., at or near the horizontal center of the screen). Interface 700 includes indications of the current states of the respective settings for both users 790 in the default neutral mode.
  • UI elements 734 A and 734B show the respective current states of the volume setting for users 790 A and 790B, respectively
  • UI elements 754A and 754B show the respective current states of the fan setting for users 790A and 790B, respectively
  • UI elements 774A and 774B show the respective current states of the temperature setting for users 790A and 790B, respectively.
  • FIG. 7B shows interface 400 with control 430 upon detecting that left user 790 A has selected control 730, for example by touching control 730 with a finger.
  • the interface 700 may change to indicate that the left user 790A is currently interacting with the interface 700, for example by "glowing" on the left side of the screen as shown in FIG. 7B.
  • UI element 734B corresponding to user 790B disappears, and UI element 734A corresponding to user 790A "unrolls" for control 730.
  • a UI element such as a slider track is not displayed as in FIGS. 5A-5E or FIGS 6A-6G; the arrows of FIG. 7B simply illustrates directions that control 730 may be moved.
  • the UI elements that visually indicate states for the other controls 750 and 770 may also disappear, as shown in FIG. 7B.
  • user 790A may then adjust their state (e.g., volume level for the left zone), for example by moving the control 730 to the right on the display.
  • the visual indication 734A of the state may change correspondingly as the control 730 is moved.
  • the interface 700 and control 730 may return to the default neutral mode as illustrated in FIG. 7A, with UI element 734A now showing the adjusted state for user 790 A.
  • the interface 700 when user 790 A releases the control 730, there may be a pause of a few seconds before resetting the interface 700 to the default neutral mode in case the user 790A wants to continue interacting with the interface 700, for example by re-adjusting the volume setting; after the pause, the interface 700 is reset to the default neutral mode as shown in FIG. 7A.
  • FIG. 7D illustrates concurrent interactions by the users with the interface 700, according to some embodiments.
  • example multi-user interface 700 is used to illustrate support for concurrent interaction
  • concurrent interaction may be similarly supported by one or more of the other example multi-user interfaces described herein.
  • the multi-user system may support concurrent interactions by more than one user with the multiuser interface.
  • the system may detect interactions by two users at the same time, detect which part of the interface (e.g., which control) the users are interacting with, and react accordingly, for example by setting the states for the respective controls according to the particular users interacting with the controls. As an example, as shown in FIG.
  • the left user 790A may reach for the interface 700 to adjust the volume for their zone of an audio system; the system detects that the interaction is by the left user 790A, sets the volume control UI element 730 according to the left user 790A's current state for volume (e.g., UI element 734B corresponding to user 790B disappears, and UI element 734A corresponding to user 790A "unrolls" for control 730), and responds to input to the control 730 by the left user 790A by appropriately adjusting the volume setting for the left zone of the audio system.
  • the system detects that the interaction is by the left user 790A sets the volume control UI element 730 according to the left user 790A's current state for volume (e.g., UI element 734B corresponding to user 790B disappears, and UI element 734A corresponding to user 790A "unrolls" for control 730), and responds to input to the control 730 by the left user 790A by appropriately adjusting the volume setting for the
  • the right user 790B may reach for the interface 700 to adjust the temperature for their zone of an HVAC system; the system detects that the interaction is by the right user 790B, sets the temperature control UI element 770 according to the right user 790B's current state for temperature (e.g., UI element 774A corresponding to user 790A disappears, and UI element 734B corresponding to user 790B "unrolls" for control 770), and responds to input to the control 770 by the right user 790B by appropriately adjusting the temperature setting for the right zone of the HVAC system.
  • the system detects that the interaction is by the right user 790B, sets the temperature control UI element 770 according to the right user 790B's current state for temperature e.g., UI element 774A corresponding to user 790A disappears, and UI element 734B corresponding to user 790B "unrolls" for control 770
  • FIGS. 8 A and 8B illustrate a multi-user interface 800 that includes another variation of multi-user, multi-state controls, according to some embodiments.
  • FIGS. 8A and 8B illustrate another example multi-user control of an interface 800 that, in its default neutral mode, may provide visual indications of the current states of the respective setting for both users 890.
  • the visual indications of the current states corresponding to the users 890 disappear, the selected control may be expanded in size, and one or more other controls may be reduced in size or alternatively may be hidden.
  • a UI element corresponding to and visually indicating the detected user 890' s state "unrolls" for the selected control.
  • the user 890 may then adjust their state, for example by a clockwise or counterclockwise circular motion as if they are rotating a dial or knob; the visual indication of the respective state may change correspondingly as the control is manipulated.
  • the interface 800 and controls may return to the default neutral mode.
  • the interface 800 may initially be set to a default neutral mode, for example as illustrated in FIG. 8A. As shown in FIG. 8A, the interface 800 may be set to the default neutral mode when there is no user currently detected as interacting with the interface 800.
  • the background of interface 800 may, for example, be set to a uniform color and/or pattern that does not visually indicate that a particular user is interacting with the interface 800.
  • Multi-user, multi- state controls 830, 850, and 870 may be displayed in their default positions (e.g., at or near the horizontal center of the screen). Interface 800 includes indications of the current states of the respective settings for both users 890 in the default neutral mode.
  • UI elements 834A and 834B show the respective current states of the volume setting for users 890A and 890B, respectively
  • UI elements 854A and 854B show the respective current states of the fan setting for users 890A and 890B, respectively
  • UI elements 874A and 874B show the respective current states of the temperature setting for users 890A and 890B, respectively.
  • FIG. 8B shows interface 400 with control 430 upon detecting that left user 890A has selected control 830, for example by touching control 830 with a finger.
  • the interface 800 may change to indicate that the left user 890A is currently interacting with the interface 800, for example by "glowing" on the left side of the screen as shown in FIG. 8B.
  • UI elements 834A and 834B, 854A and 854B, and 874A and 874B may disappear.
  • the selected control 830 may be expanded in size, and controls 850 and 870 may be reduced in size or alternatively may be hidden.
  • a UI element 836 corresponding to and visually indicating the detected user 890's state "unrolls" for the selected control 830.
  • the user 890A may then adjust their state, for example by a clockwise or counterclockwise circular motion as if they are rotating a dial or knob; the visual indication 836 of the respective state may change correspondingly as the control is manipulated.
  • the interface 800 and controls may return to the default neutral mode as shown in FIG. 8A, with UI element 834A now showing the adjusted state for user 890A.
  • the interface 800 when user 890A releases the control 830, there may be a pause of a few seconds before resetting the interface 800 to the default neutral mode in case the user 890A wants to continue interacting with the interface 800, for example by re-adjusting the volume setting; after the pause, the interface 800 is reset to the default neutral mode as shown in FIG. 8A.
  • FIGS. 9A through 9E illustrate a multi-user interface 900 that includes yet another variation of multi-user, multi-state controls, according to some embodiments.
  • the entire interface 900 may be adapted to a particular user upon detecting that the user is currently interacting with the interface 900.
  • the interface 900 may initially be set to a default neutral mode, for example as illustrated in FIG. 9A.
  • the interface 900 may be set to the default neutral mode when there is no user currently detected as interacting with the interface 900.
  • the background of interface 900 may, for example, be set to a uniform color and/or pattern that does not visually indicate that a particular user is interacting with the interface 900.
  • Multi-user, multi-state controls 930, 950, and 970 may be displayed in their default positions (e.g., at or near the horizontal center of the screen).
  • interface 900 may include one or more multi-user, multi-state controls as illustrated in FIGS. 4G through 41.
  • FIGS. 4A through 4F may be used in embodiments.
  • FIG. 9B shows interface 900 upon detecting that left user 990 A is interacting with the interface 900, for example by making a motion with their right hand towards the screen, or by touching the screen.
  • the interface 900 may visually indicate that the left user 990A is currently interacting with the interface 900, for example by "glowing" on the left side of the screen as shown in FIG. 9B.
  • visual indications 934A, 954A, and 974A of the user 990A's current states for controls 930, 950, and 970, respectively may be displayed.
  • FIG. 9C shows interface 900 upon detecting that left user 990A has selected control 930.
  • visual indications 954A and 974A of user 990A's states corresponding to controls 950 and 970 may disappear, while visual indication 934A corresponding to user 990A's state for control 930 may remain.
  • the arrows represent directions in which control 930 may me moved to adjust the state.
  • user 990A may then adjust their state (e.g., volume level for the left zone), for example by moving the control 930 to the right on the display.
  • the visual indication 934A of the state may change correspondingly as the control 930 is moved.
  • the control 930 may return to its default position as illustrated in FIGS. 9A and 9B, with UI element 934A now showing the adjusted state for user 990 A.
  • FIGS. 10A through 10E illustrate an example multi-user interface 1000 in which at least a portion of the interface 1000 may be adapted to the particular user that is detected by the detection mechanism, according to some embodiments.
  • interface 1000 may be divided into multiple regions according to the controlled systems, for example an audio control region 1002 and an HVAC control region 1004 as shown in FIGS. 10A through 10E.
  • One or more of the regions may be changed to indicate a current user interacting with the interface 1000 or region, for example by setting the interface 1000 or region to a theme (colors, textures, graphics, etc.) specified by the particular user.
  • FIG. 10A shows interface 1000 in a default neutral state, according to some embodiments.
  • audio control region 1002 may include one or more multi-user, multi-state controls such as a volume control 1030 that may, for example, be implemented according to one of the methods as illustrated in FIGS. 4 A through 4L.
  • Audio control region 1002 may also include one or more global control elements for the audio system (e.g., pause or play 1014, reverse 1012, and forward 1016 controls). Audio control region 1002 may also include a stateless "add to playlist" UI element 1020 that, when selected by a particular user, adds a title being played to that user's playlist.
  • Audio control region 1002 may also include one or more graphics and/or textual UI elements (e.g., elements 1002 and 1004).
  • element 1004 may display a list of songs and the current song, being played by the audio system, and may also indicate other information such as artists and albums.
  • element 1002 may display graphics such as cover art of an album on which the current song being played appears.
  • one or more of these graphics and/or textual UI elements may be multi-user, interactive elements. For example, selection of element 1002 by a particular user may cause that user's playlist to be displayed. The user can then select the "add to playlist" element 1020 to add the current title being played by the audio system to the user's displayed playlist. As another example, the user may select a title from their displayed playlist to add the song to the list being played on the audio system.
  • HVAC control region 1004 may include one or more multi-user, multi-state controls such as a fan speed control 1050 and temperature control 1070 that may, for example, be implemented according to one of the methods as illustrated in FIGS. 4 A through 4L.
  • multi-user, multi-state controls such as a fan speed control 1050 and temperature control 1070 that may, for example, be implemented according to one of the methods as illustrated in FIGS. 4 A through 4L.
  • HVAC control region 1004 upon detecting an interaction by a particular user (user 1090A, in FIG. 10B) within HVAC control region 1004, the current states of the HVAC controls for the particular user may be graphically and/or textually displayed on interface 1000.
  • HVAC control region 1004 shows a current temperature of 68 degrees, and a fan speed of 3 on a scale from 0 (off) to 5 (max), for user 1090 A.
  • FIG. IOC shows user 1090A adjusting the fan speed using control 1050 according to one of the methods as illustrated in FIGS. 4A through 4L; the visual indication of the fan speed for user 1090A's zone changes as the user 1090A manipulates the control 1050.
  • control 1050 may be changed to display a graphic (e.g., a picture, avatar, etc.) corresponding to user 1090A.
  • FIG. 10D shows the current states of the HVAC controls upon detecting an interaction by user 1090B.
  • the region 1004 changes to show a current temperature of 72 degrees, and a fan speed of 2 on a scale from 0 (off) to 5 (max), for user 1090B.
  • FIG. 10E shows that user 1090A's playlist 1006 may be displayed, for example upon user 1090A selecting UI element 1002.
  • a graphic e.g., a picture, avatar, etc.
  • Playlist 1006 may, for example, be a scrollable window, and may include interactive UI elements, for example elements that allow user 1090A to remove titles from the playlist 1006 if desired.
  • user 1090A may select a title from playlist 1006 to be played, for example by dragging the title from playlist 1006 on to element 1004.
  • user 1090A may select "add to playlist" element 1020 to add a current song being played on the audio system to user 1090A's playlist 1006.
  • FIG. 11 illustrates a variation of a multi-user interface as illustrated in FIGS. 10A through 10E, according to some embodiments.
  • Interface 1100 includes two regions 1102 and 1104 as illustrated in FIG. 10. However, in the default state, the current states of the HVAC controls for both users may be graphically and/or textually displayed on interface 1100.
  • HVAC control region 1004 shows a current temperature of 64 degrees, and a fan speed of 4 on a scale from 0 (off) to 5 (max), for the left user, and a current temperature of 68 degrees, and a fan speed of 2 on a scale from 0 (off) to 5 (max), for the right user.
  • FIG. 1 illustrates a variation of a multi-user interface as illustrated in FIGS. 10A through 10E, according to some embodiments.
  • Interface 1100 includes two regions 1102 and 1104 as illustrated in FIG. 10. However, in the default state, the current states of the HVAC controls for both users may be graphically and/or textually displayed on interface 1100.
  • control 11 shows left user 1190A adjusting the fan speed using control 1150 according to one of the methods as illustrated in FIGS. 4A through 4L; the visual indication of the fan speed for left user 1190A's zone changes as the user 1190A manipulates the control 1150.
  • control 1150 may be changed to display a graphic (e.g., a picture, avatar, etc.) corresponding to user 1190A.
  • FIGS. 12A through 12C illustrate a multi-user interface for a multi-user system that includes physical controls, according to some embodiments.
  • Physical controls include controls such as mechanical dials, knobs, sliders, buttons, etc., as opposed to graphical controls displayed on a screen, for example as shown in FIG. 3.
  • FIG. 12A shows interface 1200 in a default neutral state. In this example, in the default state, the current states of the controls for both users may be graphically and/or textually displayed on interface 1200.
  • interface 1200 shows a current volume of 2 on a scale from 0 (mute) to 5, a current temperature of 64 degrees, and a fan speed of 4 on a scale from 0 (off) to 5 (max), for the left user, and a current volume of 4 on a scale from 0 (mute) to 5, a current temperature of 68 degrees, and a fan speed of 2 on a scale from 0 (off) to 5 (max), for the right user.
  • the multi-user system includes one or more physical controls for the settings of the controlled systems, for example a volume control dial or knob 1260 for the audio system, and an HVAC control 1262 for the HVAC system that includes a dial or knob (e.g., for adjusting temperature) and a ring around the dial or knob (e.g., for adjusting fan speed).
  • a volume control dial or knob 1260 for the audio system
  • an HVAC control 1262 for the HVAC system that includes a dial or knob (e.g., for adjusting temperature) and a ring around the dial or knob (e.g., for adjusting fan speed).
  • FIG. 12B shows interface 1200 upon detecting that left user 1290A is touching or interacting with volume control 1260.
  • the interface 1200 may visually indicate that the left user 1290A is currently interacting with the system, for example by "glowing" on the left side of the screen as shown in FIG. 12C.
  • Left user 1290A may then change the volume by physically manipulating control 1260; the visual indication of the state for volume corresponding to the left user 1290A may change as the user 1290A manipulates the control 1260.
  • the interface 1200 may change to the default neutral state as illustrated in FIG. 12 A.
  • FIG. 12C shows interface 1200 upon detecting that right user 1290B is touching or interacting with HVAC controls 1262.
  • the interface 1200 may visually indicate that the right user 1290B is currently interacting with the system, for example by "glowing" on the right side of the screen as shown in FIG. 12C.
  • Right user 1290B may then change the temperature and/or fan speed by physically manipulating control 1262; the visual indication of the state for temperature and/or fan speed corresponding to the right user 1290B may change as the user 1290B manipulates the control 1262.
  • the interface 1200 may change to the default neutral state as illustrated in FIG. 12 A.
  • FIG. 13 illustrates another type of multi-user, multi-state control element on an example multi-user interface 1300, according to some embodiments.
  • interface 1300 illustrates another type of multi-user, multi-state control element on an example multi-user interface 1300, according to some embodiments.
  • interface 1300 illustrates another type of multi-user, multi-state control element on an example multi-user interface 1300, according to some embodiments.
  • interface 1300 illustrates another type of multi-user, multi-state control element on an example multi-user interface 1300, according to some embodiments.
  • interface 1300 illustrates another type of multi-user, multi-state control element on an example multi-user interface 1300, according to some embodiments.
  • interface 1300 illustrates another type of multi-user, multi-state control element on an example multi-user interface 1300, according to some embodiments.
  • interface 1300 illustrates another type of multi-user, multi-state control element on an example multi-user interface 1300, according to some embodiments.
  • interface 1300 illustrates another type of multi
  • 1300 may include indications of the user's respective states for a setting (volume, in this example). However, instead of providing a multi-state control that is moved one way or the other by a particular user to adjust that user's state, simple plus 1354 and minus 1352 controls are provided. A user may tap or hold one of controls 1354 and 1352 to adjust the volume up or down for their zone; the system detects which user is interacting with the control and adjusts the volume for that user's zone accordingly.
  • the multi-user system may support concurrent interactions by more than one user with the multi-user interface. In these embodiments, as shown in FIG. 13, the system may detect concurrent interactions by both users 1490A and 1490B with controls 1352 and 1354, and adjust the volume for the respective users' zones accordingly.
  • FIG. 14 illustrates binary multi-state control elements of a multi-user interface, according to some embodiments.
  • a multi-user interface as illustrated in FIGS. 3 through 13 may include one or more binary multi-state control elements.
  • a binary multi-state control element may be set to indicate the current state (e.g., on or off) of the binary UI element for the users.
  • FIG. 14 uses a "heart" or “like” UI element 318 as illustrated in FIG. 3 that may be used to indicate which user(s) like a current title being played by an audio system. As shown in FIG.
  • the UI element may have a binary state that shows whether neither user has “liked” the title, whether one or the other user has “liked” the title, or whether both users have liked the title.
  • the multi-user system may detect which user interacts with a binary multi-state control element, and in response change state of the element accordingly.
  • FIG. 14 shows an example binary truth table for the states of a binary multi-state control element. As shown, (0,0) indicates that the element is "off for both users, (0,1) indicates that the element is "off for the left user and “on” for the right user, (1,0) indicates that the element is "on” for the left user and “off for the right user, and (1, 1) indicates that the element is "on” for both users. [0120] FIG. 14 also shows two examples of visual indications of the states of a binary multi- state control element. In option A, in state 00, the element 318 may be a first color (e.g., white).
  • a first color e.g., white
  • the state becomes (0, 1), and the right side of the element 318 may be may be filled or shaded with a different color, for example red.
  • the left user selects element 318 when the element is in state (0,0)
  • the state becomes (1,0)
  • the left side of the element 318 may be filled or shaded with the different color.
  • the state is (1, 1), and both sides of the element may be filled or shaded.
  • Option B shows an example in which badges are used to indicate state for element 318. In state (0,0), the element 318 is not badged.
  • the state becomes (0,1), and a badge is added to the right side of the element 318.
  • the left user selects element 318 when the element is in state (0,0)
  • the state becomes (1,0)
  • a badge is added to the left side of the element 318.
  • both users have selected element 318, the state is (1,1), and there are badges displayed on both sides of the element.
  • the badges may be customized for the different users, for example using different colors, or different graphics such as pictures, icons, or avatars.
  • FIGS. 15A through 15D illustrate controls of a multi-user interface 1500 that provide exclusive access to particular users, according to some embodiments.
  • a multi-user interface as illustrated in FIGS. 3 through 13 may include one or more exclusive controls.
  • An exclusive control is only active for one of the users; that user's state for a respective setting is associated with that control.
  • the system responds to interactions with the control by a particular user (e.g., the right or left user) by affecting the respective state for that user.
  • the state for the user associated with the control is not affected.
  • visual, haptic, and/or aural feedback may be provided to indicate to the other user that the user does not have access to that control.
  • FIGS. 15A through 15D use, as an example of an exclusive control, a "heart" or “like” UI element 1518 on a multi-user interface 1500 that may be used to indicate whether a user likes a current title being played by an audio system, and that may be selected by a particular user to change the state for that user.
  • each user is provided with an exclusive control 1518, with control 1518A exclusive to a first (e.g., left) user, and control 1518B exclusive to a second (right) user.
  • Each control 1518 may have a binary state that shows whether or not the associated user has “liked” the title (e.g., colored white if not “liked", and shaded in some other color if “liked”).
  • the multi-user system may detect when a user interacts with their exclusive control 1518, and in response change state of the control 1518 accordingly.
  • FIG. 15A shows controls 1518A and 1518B when neither user has “liked” the title.
  • FIG. 15B shows controls 1518A and 1518B when the right user has “liked” the title.
  • FIG. 15C shows controls 1518A and 1518B when the left user has “liked” the title.
  • FIG. 15D shows controls 1518A and 1518B when both users have “liked” the title.
  • FIGS. 15A through 15D also show example binary states for controls (1518A, 1518B). As shown, (0,0) indicates that the controls are “off for both users, (0,1) indicates that control 1518A is “off for the left user and control 1518B is “on” for the right user, (1,0) indicates that control 1518A is “on” for the left user and control 1518B is “off for the right user, and (1, 1) indicates that the controls are “on” for both users.
  • the above section describes user interface paradigms for a multi-user system in which the interface's UI elements, such as controls and indicators, are adapted to support multiple users.
  • This section describes alternative paradigms in which the interface model for a multi-user system is adapted to support multiple users. In these paradigms, a user may be granted exclusive access to a portion or to all of the interface.
  • the multi-user system includes detection mechanism that detects when a particular user is interacting with the interface.
  • FIG. 16 illustrates an interface 1600 for a multi-user system in which each user 1690 has exclusive access to a portion or region of the interface 1600, according to some embodiments.
  • region 1602A corresponds to a left user 1690A
  • region 1602B corresponds to a right user 1690B.
  • Both regions 1602 A and 1602B include sets of controls (e.g., audio and HVAC controls) that are exclusively accessible by the respective users; the users' states are associated with the controls in their respective regions 1602. While not shown in FIG. 16, indications of one or more of the users' states may also be displayed in their respective regions 1602.
  • controls e.g., audio and HVAC controls
  • the detection mechanism detects which user is interacting within a particular region 1602; the system allows access to the controls in the region 1602 if the detected user is associated with the region 1602, and disallows access to the controls in the region 1602 if the detected user is not associated with the region 1602. In some embodiments, if a user attempts to use a control in the other user's region 1602, the state for the user associated with the control is not affected. In some embodiments, visual, haptic, and/or aural feedback may be provided to indicate to a user that the user does not have access to a control.
  • FIGS. 17A and 17B illustrate an interface 1700 for a multi-user system in which a user 1790 is granted exclusive access to the interface 1700, according to some embodiments.
  • left user 1790A is interacting with the interface 1700.
  • left user 1790A is interacting with the interface 1700.
  • left user 1790A is interacting with the interface 1700.
  • the system may change the interface to left user mode 1702A.
  • the interface 1700 in mode 1702A may visually indicate that the left user 1790 A is currently interacting with the interface 1700, for example by "glowing" on the left side of the screen as shown in FIG. 17 A, or by being set to a different color or theme for the user 1790A.
  • left user 1790A's states are associated with the controls in the interface 1700. While not shown in FIG. 17A, indications of one or more of left user 1702A's states may also be displayed in mode 1702A.
  • the detection mechanism detects which user is interacting with the interface 1700 in mode 1702A; the system allows access to the controls in mode 1702A if the detected user is the left user 1790A, and disallows access to the controls if the detected user is the right user 1790B. In some embodiments, if right user 1790B attempts to use a control in mode 1702A, the state associated with the control is not affected. In some embodiments, visual, haptic, and/or aural feedback may be provided to indicate to right user 1790B that the user does not have access to the control.
  • the interface 1700 when user 1790A stops interacting with the interface 1700, there may be a pause of a few seconds in which the interface 1700 remain in mode 1702 A in case the user 1790 A wants to continue interacting with the interface 1700; after the pause, the interface 1700 may be reset to a default neutral mode until another interaction is detected.
  • right user 1790B is detected to be interacting with the interface 1700.
  • the system may change the interface to right user mode 1702B.
  • the interface 1700 in mode 1702B may visually indicate that the right user 1790B is currently interacting with the interface 1700, for example by "glowing" on the right side of the screen as shown in FIG. 17B, or by being set to a different color or theme for the user 1790B.
  • right user 1790B's states are associated with the controls in the interface 1700. While not shown in FIG.
  • indications of one or more of right user 1702B's states may also be displayed in mode 1702B.
  • the detection mechanism detects which user is interacting with the interface 1700 in mode 1702B; the system allows access to the controls in mode 1702B if the detected user is the right user 1790B, and disallows access to the controls if the detected user is the left user 1790A.
  • left user 1790 A attempts to use a control in mode 1702B, the state associated with the control is not affected.
  • visual, haptic, and/or aural feedback may be provided to indicate to left user 1790 A that the user does not have access to the control.
  • the interface 1700 when user 1790B stops interacting with the interface 1700, there may be a pause of a few seconds in which the interface 1700 remain in mode 1702B in case the user 1790B wants to continue interacting with the interface 1700; after the pause, the interface
  • 1700 may be reset to a default neutral mode until another interaction is detected.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Chemical & Material Sciences (AREA)
  • Combustion & Propulsion (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

L'invention concerne un système multi-utilisateur et une interface comportant un mécanisme de détection qui peut servir à détecter un utilisateur particulier qui se trouve actuellement en interaction avec le système. Les interactions de l'utilisateur avec l'interface sont ensuite appliquées par le système à un ou plusieurs états spécifiques à l'utilisateur d'un ou plusieurs systèmes commandés (par exemple, des systèmes HVAC et/ou audio). L'interface peut comprendre des commandes multi-utilisateurs, multi-états, un état actuel des commandes étant déterminé par la détection d'un utilisateur actuel qui se trouve en interaction avec l'interface. Lors de la détection d'une interaction par un utilisateur, l'interface peut être adaptée à cet utilisateur, par exemple en définissant les commandes en vue de les rendre spécifiques à l'utilisateur. Ainsi, au lieu de présenter des ensembles séparés de commandes pour chaque utilisateur, il peut être fourni un seul ensemble de commandes par l'intermédiaire duquel de multiples utilisateurs peuvent définir des états respectifs pour un ou plusieurs systèmes commandés.
PCT/US2017/052329 2016-09-21 2017-09-19 Système multi-utilisateur et interface WO2018057533A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662397480P 2016-09-21 2016-09-21
US62/397,480 2016-09-21

Publications (1)

Publication Number Publication Date
WO2018057533A1 true WO2018057533A1 (fr) 2018-03-29

Family

ID=60002043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/052329 WO2018057533A1 (fr) 2016-09-21 2017-09-19 Système multi-utilisateur et interface

Country Status (1)

Country Link
WO (1) WO2018057533A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102023105843B3 (de) 2023-03-09 2024-05-29 Audi Aktiengesellschaft Bedieneinrichtung für ein Kraftfahrzeug sowie Verfahren zum Betreiben einer Bedieneinrichtung

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080004769A1 (en) * 2006-06-30 2008-01-03 Gm Global Technology Operations, Inc. Method and apparatus for detecting and differentiating users of a device
EP1953028A2 (fr) * 2007-02-01 2008-08-06 Volkswagen Aktiengesellschaft Dispositif d'affichage et de commande d'un véhicule automobile incluant la saisie de paramètres utilisateurs
US8390584B1 (en) * 2009-10-13 2013-03-05 Intuit Inc. Digit aware touchscreen
US20130129162A1 (en) * 2011-11-22 2013-05-23 Shian-Luen Cheng Method of Executing Software Functions Using Biometric Detection and Related Electronic Device
DE102014201930A1 (de) * 2014-02-04 2015-08-06 Volkswagen Aktiengesellschaft Verfahren und Vorrichtung zum Anzeigen einer Veränderung einer Einstellung zumindest eines Parameters einer Fahrzeugfunktion

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080004769A1 (en) * 2006-06-30 2008-01-03 Gm Global Technology Operations, Inc. Method and apparatus for detecting and differentiating users of a device
EP1953028A2 (fr) * 2007-02-01 2008-08-06 Volkswagen Aktiengesellschaft Dispositif d'affichage et de commande d'un véhicule automobile incluant la saisie de paramètres utilisateurs
US8390584B1 (en) * 2009-10-13 2013-03-05 Intuit Inc. Digit aware touchscreen
US20130129162A1 (en) * 2011-11-22 2013-05-23 Shian-Luen Cheng Method of Executing Software Functions Using Biometric Detection and Related Electronic Device
DE102014201930A1 (de) * 2014-02-04 2015-08-06 Volkswagen Aktiengesellschaft Verfahren und Vorrichtung zum Anzeigen einer Veränderung einer Einstellung zumindest eines Parameters einer Fahrzeugfunktion

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102023105843B3 (de) 2023-03-09 2024-05-29 Audi Aktiengesellschaft Bedieneinrichtung für ein Kraftfahrzeug sowie Verfahren zum Betreiben einer Bedieneinrichtung

Similar Documents

Publication Publication Date Title
US8843529B2 (en) Display information controlling apparatus and method
US8386944B2 (en) Method for providing graphical user interface and electronic device using the same
US9411491B2 (en) Method for providing graphical user interface (GUI), and multimedia apparatus applying the same
EP2169525A1 (fr) Procédé pour fournir un menu utilisant le réglage de menu et dispositif multimédia l'utilisant
US20140149901A1 (en) Gesture Input to Group and Control Items
EP3537273A1 (fr) Système doté d'une interface utilisateur faisant appel à une sélection d'objets et des gestes
US20190227679A1 (en) Information processing device and information processing method
US20080163119A1 (en) Method for providing menu and multimedia device using the same
US20110265040A1 (en) Method for providing graphical user interface and mobile device adapted thereto
TW201246054A (en) Information processing apparatus, information processing method, and program
KR20080046511A (ko) 교차형 메뉴 표시 방법 및 장치
US20070146339A1 (en) Mobile apparatus for providing user interface and method and medium for executing functions using the user interface
TWI540492B (zh) 電子裝置以及電子裝置控制方法
KR20150135840A (ko) 사용자 인터페이스 제공 장치 및 방법
EP3266223B1 (fr) Panneau à interface d'utilisateur commandée à deux mains pour un lecteur multimédia destiné à un ensemble de pièces
WO2018057533A1 (fr) Système multi-utilisateur et interface
JP4526307B2 (ja) 機能選択装置
US9354808B2 (en) Display control device, display control method, and program
TWI397852B (zh) 功能選擇系統及方法，及其機器可讀取媒體
KR101352201B1 (ko) 미디어 플레이어를 제어하는 방법 및 이를 적용한 정보기기
JP2022184980A (ja) 情報表示装置
JP2007072761A (ja) 操作入力装置
US20200272325A1 (en) Input control device, input device, and input control method
KR100987512B1 (ko) 메뉴 표시 방법 및 미디어 장치
JP2019049738A (ja) 表示制御装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17778052

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17778052

Country of ref document: EP

Kind code of ref document: A1