EP3221783A1 - Interface multimodale embarquée - Google Patents

Interface multimodale embarquée

Info

Publication number
EP3221783A1
EP3221783A1 EP15801074.4A EP15801074A EP3221783A1 EP 3221783 A1 EP3221783 A1 EP 3221783A1 EP 15801074 A EP15801074 A EP 15801074A EP 3221783 A1 EP3221783 A1 EP 3221783A1
Authority
EP
European Patent Office
Prior art keywords
input
user
modality
task
console
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
EP15801074.4A
Other languages
German (de)
English (en)
Other versions
EP3221783B1 (fr
Inventor
Jason Ryan Farmer
Mike Glass
Vikram Padmakar BAPAT
Kristoffer S. SCHULZ
Oscar E. Murillo
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Technology Licensing 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 Microsoft Technology Licensing LLC filed Critical Microsoft Technology Licensing LLC
Publication of EP3221783A1 publication Critical patent/EP3221783A1/fr
Application granted granted Critical
Publication of EP3221783B1 publication Critical patent/EP3221783B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/20—Output arrangements, i.e. from vehicle to user, 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/20—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor
    • B60K35/21—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor using visual output, e.g. blinking lights or matrix displays
    • B60K35/22—Display screens
    • 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/20—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor
    • B60K35/28—Output arrangements, i.e. from vehicle to user, associated with vehicle functions or specially adapted therefor characterised by the type of the output information, e.g. video entertainment or vehicle dynamics information; characterised by the purpose of the output information, e.g. for attracting the attention of the driver
    • 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
    • B60K35/654—Instruments specially adapted for specific vehicle types or users, e.g. for left- or right-hand drive the user being the driver
    • 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/80—Arrangements for controlling instruments
    • 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/85—Arrangements for transferring vehicle- or driver-related data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/033—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
    • G06F3/0362—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor with detection of 1D translations or rotations of an operating part of the device, e.g. scroll wheels, sliders, knobs, rollers or belts
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
    • G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/16—Sound input; Sound output
    • G06F3/167—Audio in a user interface, e.g. using voice commands for navigating, audio feedback
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/60—Substation equipment, e.g. for use by subscribers including speech amplifiers
    • H04M1/6033—Substation equipment, e.g. for use by subscribers including speech amplifiers for providing handsfree use or a loudspeaker mode in telephone sets
    • H04M1/6041—Portable telephones adapted for handsfree use
    • H04M1/6075—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle
    • H04M1/6083—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle by interfacing with the vehicle audio system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/60—Substation equipment, e.g. for use by subscribers including speech amplifiers
    • H04M1/6033—Substation equipment, e.g. for use by subscribers including speech amplifiers for providing handsfree use or a loudspeaker mode in telephone sets
    • H04M1/6041—Portable telephones adapted for handsfree use
    • H04M1/6075—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle
    • H04M1/6083—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle by interfacing with the vehicle audio system
    • H04M1/6091—Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle by interfacing with the vehicle audio system including a wireless interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
    • 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
    • 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/151—Instrument output devices for configurable output
    • 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/16—Type of output information
    • B60K2360/164—Infotainment
    • 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/55—Remote control arrangements
    • B60K2360/56—Remote control arrangements using mobile devices
    • B60K2360/573—Mobile devices controlling vehicle functions
    • 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/589—Wireless data transfers
    • 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/592—Data transfer involving external databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2203/00—Indexing scheme relating to G06F3/00 - G06F3/048
    • G06F2203/038—Indexing scheme relating to G06F3/038
    • G06F2203/0381—Multimodal input, i.e. interface arrangements enabling the user to issue commands by simultaneous use of input devices of different nature, e.g. voice plus gesture on digitizer

Definitions

  • Various embodiments enable mobile devices, such as phones and the like, to integrate with an in-vehicle information/entertainment system to enable the user to control the in-vehicle information/entertainment system by way of their mobile phone.
  • Users can leverage the functionality of their mobile phone to promote an in-vehicle experience which can be contextually tailored to the user's or the vehicle's context.
  • Yet other embodiments can purvey an in-vehicle experience through a cloud based service.
  • a user can complete various tasks using multiple different modalities with smooth continuous modal handoffs between the modalities.
  • the modalities can include voice, touch, gestures, NUI gestures, gaze, and controls such as a jog dial. Smooth modal handoffs permit the user to easily change their input modality depending on their context.
  • FIG. 1 Other embodiments can tailor the voice-only experience based on drive scenarios and the user's cognitive load. Yet other embodiments can tailor the user experience for jog dial, gestures, gaze and touchscreen modalities. Further embodiments can provide an adaptive user interface including an adaptive user interface that can operate in connection with multiple different types of screens, e.g., a phone screen, a cluster screen, a console screen, and a heads up display (HUD) screen, and the like. Still further embodiments provide a universal command/control model for multiple types of physical input including button jogs, capacitive dials, hard keys, pads, and the like.
  • HUD heads up display
  • FIG. 1 illustrates an example operating environment in accordance with one or more embodiments.
  • FIG. 2 illustrates a system in accordance with one or more embodiments.
  • FIG. 3 illustrates a system in accordance with one or more embodiments.
  • FIG. 4 illustrates a system in accordance with one or more embodiments.
  • FIG. 5 illustrates a system in accordance with one or more embodiments.
  • FIG. 6 illustrates a system in accordance with one or more embodiments.
  • FIG. 7 illustrates a system in accordance with one or more embodiments.
  • FIG. 8 illustrates a system in accordance with one or more embodiments.
  • FIG. 9 illustrates a system in accordance with one or more embodiments.
  • FIG. 10 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 11 is a diagram that illustrates a verbal dialog between a user and an in-vehicle system in accordance with one or more embodiments.
  • FIG. 12 is a diagram that illustrates a verbal dialog between a user and an in-vehicle system in accordance with one or more embodiments.
  • FIG. 13 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 14 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 15 illustrates a system in accordance with one or more embodiments.
  • FIG. 15A is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 16 illustrates a system in accordance with one or more embodiments.
  • FIG. 17 illustrates aspects of a system in accordance with one or more embodiments.
  • FIG. 18 illustrates a system in accordance with one or more embodiments.
  • FIG. 19 illustrates a system in accordance with one or more embodiments.
  • FIG. 19A is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 20 illustrates a system in accordance with one or more embodiments.
  • FIG. 21 illustrates a system in accordance with one or more embodiments.
  • FIG. 22 illustrates a system in accordance with one or more embodiments.
  • FIG. 22 A is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 23 illustrates a system in accordance with one or more embodiments.
  • FIG. 24 illustrates a system in accordance with one or more embodiments.
  • FIG. 25 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 26 illustrates a system in accordance with one or more embodiments.
  • FIG. 27 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • FIG. 28 illustrates an example computing device that can be utilized to implement various embodiments described herein.
  • Various embodiments enable mobile devices, such as phones and the like, to integrate with an in- vehicle information/entertainment system to enable the user to control the in- vehicle information/entertainment system by way of their mobile phone.
  • Users can leverage the functionality of their mobile phone to promote an in-vehicle experience which can be contextually tailored to the user's or the vehicle's context.
  • Yet other embodiments can purvey an in-vehicle experience through a cloud based service.
  • a user can complete various tasks using multiple different modalities with smooth continuous modal handoffs between the modalities.
  • the modalities can include voice, touch, gestures, NUI gestures, gaze and controls such as a jog dial. Smooth modal handoffs permit the user to easily change their input modality depending on their context.
  • FIG. 10 Other embodiments can tailor the voice-only experience based on drive scenarios and the user's cognitive load. Yet other embodiments can tailor the user experience for jog dial and touchscreen modalities. Further embodiments can provide an adaptive user interface including an adaptive user interface that can operate in connection with multiple different types of screens, e.g., a phone screen, a cluster screen, a console screen, and a heads-up display (HUD) screen. Still further embodiments provide a universal command/control model for multiple types of physical input including button jogs, capacitive dials, hard keys, pads, and the like.
  • HUD heads-up display
  • FIG. 1 illustrates an example environment 100 in an example implementation that is operable to employ the techniques described herein.
  • the illustrated environment 100 includes a vehicle 102, a mobile computing device in the form of a phone 104, and a vehicle console 106 having a display device 108.
  • the console 106 is shown removed from vehicle 102 for the purpose of the description that follows.
  • the console 106 typically resides on or slightly below the dashboard between the driver's seat and the front passenger's seat.
  • the console's display device 108 is or can be touch- enabled so that it can receive touch input to, for example, enable a user to make content selections.
  • Beneath console 106 a number of buttons are provided and are shown generally at 110.
  • vehicle 102 can include a jog dial 112 that can serve as an input device for console 106.
  • the jog dial 112 can be used to navigate and make content selections for content that is displayed on display device 108.
  • the jog dial can be rotated in a clockwise direction and a counterclockwise direction into and out of the plane of page upon which the jog dial appears, as indicated by the two arced arrows. Rotating the jog dial in this manner permits the user to navigate content displayed on display device 108.
  • the jog dial also includes a mechanism that can be pressed downward in the direction of the downward-pointing arrow, to make a selection.
  • rotating the jog dial allows for navigation of the displayed content and pressing the jog dial downward selects a particular piece of content. So, for example, if display device 108 displays a playlist having a number of different songs, the user can navigate the songs using the jog dial and, when a particular song of interest is located, by depressing the jog dial the user can select a song to play.
  • phone 104 can connect with console 106 to enable the user to interact with content by way of the console. Any suitable type of connection can be used.
  • phone 104 can connect with the console 106 through a wireless connection such as a Wi-Fi or Bluetooth connection. Alternately or additionally, the phone 104 can connect with the console 106 through a USB connection, as indicated in the figure.
  • the mobile phone When connected with the console 106, the mobile phone can integrate with the vehicle's information/entertainment system to enable the user to control the in- vehicle information/entertainment system by way of their mobile phone. Users can leverage the functionality of their mobile phone to promote an in-vehicle experience which can be contextually tailored to the user's or the vehicle's context, as will become apparent below.
  • FIG. 2 illustrates phone 104 in a computing environment 200 that can include the vehicle 102 (not shown) and its associated console 106.
  • the computing environment 200 also includes one or more servers 202 and a network 204 (illustrated as the "cloud") through which the phone 104, console 106 and the servers 202 can communicate.
  • the network can facilitate communication with various entities such as companies hosting content provision services, OEMs, and any other entities that are connected by way of the Internet.
  • phone 104 includes, among other components, one or more processors 206, one or more computer readable storage media 208, an interaction module 210, various applications 212, and a display driver module 214.
  • interaction module 210 includes functionality that enables voice recognition and audio voice prompting of the user.
  • the interaction module provides a personal assistant to assist the user in accomplishing tasks. So, for example, the interaction module 210 can recognize words that are spoken by the user such as commands, queries, and the like.
  • interaction module 210 includes functionality that enables actions to be taken with respect to items of communication that it receives. For example, a user may prompt their phone by asking "Please tell me if I have any meetings scheduled for today.” Responsive to receiving this request, the interaction module 210, in cooperation with, for example, a calendar application, can ascertain whether there are any meetings scheduled for today and respond verbally to the user "You have no meetings scheduled for today.”
  • Applications 212 can comprise any suitable type of application that can reside on phone 104. Such applications include, by way of example and not limitation, social networking applications, e-mail applications, text applications, calendar applications, media player applications, news, sports, and weather applications, and the like.
  • Display driver module 214 includes functionality that enables a display to be rendered on phone 104, as well as on the console's display device 108. In operation, the display driver module 214 can ascertain properties associated with the console's display device 108 (e.g. display device dimensions) and make rendering decisions based on the ascertained properties, as will become apparent below.
  • properties associated with the console's display device 108 e.g. display device dimensions
  • Servers 202 are illustrated as including a platform 216 for web services 218.
  • Web services 218 can include any suitable type of web service.
  • the servers 202 and their associated Web services 218 can generate communications that are provided to phone 104 by way of network 204. When the communications are received, the communications are processed by the phone 104 and/or an associated application executing on the phone, and the user can be notified of the communication.
  • the platform 216 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud and thus may act as a "cloud operating system.” For example, the platform 216 may abstract resources to enable communication between various computing devices. The platform 216 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the web services 218 that are implemented via the platform 216. A variety of other examples are also contemplated, such as load balancing of servers in a server farm, protection against malicious parties (e.g., spam, viruses, and other malware), and so on.
  • load balancing of servers in a server farm protection against malicious parties (e.g., spam, viruses, and other malware), and so on.
  • the cloud is included as a part of the strategy that pertains to software and hardware resources that are made available to the computing devices via the Internet or other networks.
  • any of the functions described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations.
  • the terms “module,” “functionality,” and “logic” as used herein generally represent software, firmware, hardware, or a combination thereof.
  • the module, functionality, or logic represents program code that performs specified tasks when executed on or by a processor (e.g., CPU or CPUs).
  • the program code can be stored in one or more computer readable memory devices.
  • the phone may also include an entity (e.g., software) that causes hardware or virtual machines of the computing device to perform operations, e.g., processors, functional blocks, and so on.
  • the computing device may include a computer-readable medium that may be configured to maintain instructions that cause the computing device, and more particularly the operating system and associated hardware of the computing device to perform operations.
  • the instructions function to configure the operating system and associated hardware to perform the operations and in this way result in transformation of the operating system and associated hardware to perform functions.
  • the instructions may be provided by the computer-readable medium to the computing device through a variety of different configurations.
  • One such configuration of a computer-readable medium is a signal bearing medium and thus is configured to transmit the instructions (e.g., as a carrier wave) to the computing device, such as via a network.
  • the computer-readable medium may also be configured as a computer-readable storage medium and thus is not a signal bearing medium. Examples of a computer-readable storage medium include a random-access memory (RAM), read-only memory (ROM), an optical disc, flash memory, hard disk memory, and other memory devices that may use magnetic, optical, and other techniques to store instructions and other data.
  • a section entitled “Completing a Task through Multi-Modal Input” describes how tasks can be smoothly accomplished using different types of modal input in accordance with one or more embodiments.
  • a section entitled “Tailoring Voice-Only Experiences” describes how voice only experiences can be provided in accordance with one or more embodiments.
  • a section entitled “Tailoring the User Experience for Jog Dial and Touchscreen” describes how the user experience can be tailored or otherwise adapted for different types of modal inputs.
  • a section entitled “Adaptive User Interface” describes an adaptive user interface in accordance with one or more embodiments.
  • Adaptive User Interface Using Multiple Screens describes how a user interfaces can be adapted in accordance with multiple screens.
  • a section entitled “Universal Command/Control Model” describes a model that utilizes universal commands and controls in accordance with one or more embodiments.
  • Example Device describes aspects of an example device that can be utilized to implement one or more embodiments.
  • a user can complete various tasks using multiple different modalities with smooth continuous modal handoffs between the modalities.
  • the modalities can include voice, touch, gestures, NUI gestures, gaze and controls such as a jog dial.
  • Smooth modal handoffs permit the user to easily change their input modality depending on their context. That is, the user is able to naturally move between these different input modalities in any suitable combination. For example, the user can smoothly move between (1) voice and touch, (2) voice and jog dial, (3) voice, touch, and jog dial or any combination of these and other modalities.
  • actions associated with a particular task can be performed using different modalities depending on a user's context.
  • one task may involve a certain action.
  • This action might be performed using a voice modality, for example, "Play the next music track.”
  • this action might be performed using touch input as by a user touch-selecting the next music track displayed on the console's display device.
  • this action might be performed by a user navigating to the next music track with the jog dial and then depressing the jog dial to select the next music track.
  • the user is free to choose which modality to use.
  • the user may simply make their selection using the voice modality.
  • they may choose to use touch input or the jog dial to make or perform the same action.
  • FIG. 3 in which like numerals have been utilized to depict like components.
  • the user has entered their car and connected their phone 104 to console 106 by way of a USB connection.
  • a so-called "drive mode" instrumentality 300 appears in the form of a circle.
  • the drive mode instrumentality enables the user to touch-select the console's display device to interact with drive mode functionality.
  • a start screen also appears on the console's display device and includes a number of objects which, in this example, comprise tiles. It is to be appreciated and understood that any suitable type of objects can be displayed on the console's display device. As such, tiles constitute but one example of such an object.
  • the user uses their voice to say “Call Mike Johnson”.
  • This audio input is received by the interaction module 210 (FIG. 2) on phone 104. Consequently, the interaction module interacts with the "Contacts” application on phone 104 to retrieve Mike Johnson's contact information. While doing so, the interaction module notices that there are two Mike Johnson entries in the user's Contacts.
  • the interaction module 210 then prompts the user by saying "There are two Mike Johnsons— which one would you like to call?"
  • the display driver module 214 of phone 104 can cause a user interface to be displayed on the console's device display to permit the user to select the desired callee. As an example, consider FIG.
  • a display portion 400 which illustrates a user interface that includes a "People” category with a number of touch-selectable choices including “recent”, “inner circle”, “friends”, “work”, and “all”.
  • a display portion 400 lists the two selectable “Mike Johnson” entries. Accordingly, the user can touch select the correct Mike Johnson to initiate the call experience. This can include subsequent presentation of a user interface to enable the user to touch select to either call a mobile phone, work phone, voice over IP (VoIP) number.
  • VoIP voice over IP
  • the user has used voice input to cause a search to be conducted by their phone 104.
  • the search of the user's contacts on the phone resulted in an ambiguity.
  • the phone 104 then caused a user interface to be displayed on the console's display device to enable the user to disambiguate the ambiguity through touch input.
  • different input modalities have been utilized together to complete a task.
  • the user uses their voice to say “Call Mike Johnson”.
  • This audio input is received by the interaction module 210 (FIG. 2) on phone 104. Consequently, the interaction module interacts with the "Contacts” application on phone 104 to retrieve Mike Johnson's contact information. While doing so, the interaction module notices that there are two Mike Johnson entries in the user's Contacts.
  • the interaction module 210 then prompts the user by saying "There are two Mike Johnsons— which one would you like to call?"
  • the display driver module 214 of phone 104 can cause a user interface to be displayed on the console's device display to permit the user to select the desired callee as shown in FIG. 5.
  • the first "Mike Johnson” that appears in the list is framed with a user interface instrumentality— here, a rectangle— indicating that it can be selected.
  • a user interface instrumentality here, a rectangle— indicating that it can be selected.
  • the user By rotating the jog dial, the user has navigated the user interface instrumentality from the first-listed “Mike Johnson” (indicated by the dashed rectangle) to the second-listed “Mike Johnson” (indicated by the solid rectangle).
  • the user can simply select the second- listed "Mike Johnson” by depressing the jog dial in the direction of the downward arrow. This can initiate a call to the intended callee.
  • a subsequent user experience can be provided that can include subsequent presentation of a user interface to enable the user to touch select to either call a mobile phone, work phone, voice over IP (VoIP) number.
  • VoIP voice over IP
  • the user has used voice input to cause a search to be conducted by their phone 104.
  • the search of the user's contacts on the phone resulted in an ambiguity.
  • the phone 104 then caused a user interface to be displayed on the console's display device to enable the user to disambiguate the ambiguity through the use of the jog dial.
  • different input modalities have been utilized together to complete a task.
  • the user may move freely between input modalities that include voice, touch, and the jog dial.
  • input modalities that include voice, touch, and the jog dial.
  • FIG. 6 where the user has touch-selected the drive mode user instrumentality 300 to enter drive mode.
  • the user Upon entering drive mode, the user is verbally prompted by the system, "How may I help you?" as shown in FIG. 7.
  • the driver responds "Play some music like Coldplay.”
  • the interaction module 210 receives this input and, in cooperation with a media playing application on phone 104, identifies several songs that were returned in an associated query. As an example, consider FIG. 8.
  • the system verbally prompts the user and provides a user instrumentality that can be selected by the user.
  • the user has touch-selected the "Reroute” selection so that they can be rerouted around the accident.
  • the user can then receive both audible directions as well as visible directions that are provided on a map displayed on the console's display device. In this manner, actions associated with one particular task can be interrupted when a user's context indicates that performable actions associated with a different task are available for performance.
  • the user has used three different input modalities to engage their vehicle information/entertainment system by way of their phone.
  • FIG. 10 is a flow diagram that describes steps in a method in accordance with one or more embodiments. The method can be performed in any suitable hardware, software, firmware, or combination thereof.
  • the flow diagram there are two columns - - one designated "Mobile Device” and the other designated "In-Vehicle Information/Entertainment System". This is to indicate that some of the actions are performed by a mobile device, and other actions are performed by a vehicle's entertainment system.
  • Step 1000 establishes a connection between a mobile device and an in- vehicle information/entertainment system.
  • Any suitable mobile device can be utilized including, by way of example and not limitation, a mobile phone.
  • any suitable type of connection can be established between the mobile device and the entertainment system.
  • aspects of this step can be performed by both the mobile device and the entertainment system.
  • the device and the system can, through a suitable handshake, become operably coupled together.
  • a USB connection was utilized to establish communication between the mobile device and the entertainment system.
  • Step 1002 receives input of a first modality type.
  • the input is associated with a particular task and that a user wishes to accomplish.
  • a particular task may have multiple different actions that are to be performed to accomplish the task.
  • Any suitable modality type can be received including, by way of example and not limitation, voice, touch, and/or input received through control such as a jog dial.
  • input that initiates the user experience comprises voice input.
  • step 1004 communicates with the entertainment system. Any suitable type of communication can be performed.
  • the first input can cause the mobile device and, more particularly, one or more modules executing on the mobile device, to coordinate with one or more applications that reside on the mobile device.
  • the applications can comprise any suitable type of application. For example, as in the example above, if a user wishes to communicate with a particular party, a module executing on the mobile device can ascertain, from the device's contacts application, information associated with the intended callee. This information can then be communicated to the entertainment system along with information and data to enable a user interface to be rendered that can then enable the user to establish the call.
  • Step 1006 receives the communication from the mobile device.
  • the communication can include information and data to enable a user interface to be rendered on a visual console or display device of the entertainment system.
  • Step 1008 performs one or more actions associated with the communication and performance of the task. Any suitable actions can be performed including, by way of example and not limitation, processing the data and information provided by the mobile device to render a user interface to permit the user to interact with the entertainment system using one or more different modality types.
  • Step 1010 receives input of a second modality type associated with performing the task.
  • the second modality type is different from the first modality type.
  • Any suitable modality type can be utilized, examples of which are provided above.
  • step 1012 Responsive to receiving the input of the second modality type, step 1012 performs one or more actions associated with the received input. Any suitable actions can be performed. In the illustrated and described example, these actions can be associated with a task that was initiated by the actions performed in step 1008. Alternately or additionally, the actions performed by step 1012 can be associated with a task that is different from the task associated with the actions performed in step 1008.
  • Step 1016 receives input of a third modality type.
  • the third modality type is different from both the first modality type and the second modality type.
  • Any suitable modality type can be utilized, examples of which are provided above.
  • step 1018 Responsive to receiving the input of the third modality type, step 1018 performs one or more actions associated with the received input. Any suitable types of actions can be performed. In the illustrated and described example, these actions can be associated with a task that was initiated by the actions that were performed by step 1008 and the actions that were performed by step 1012. Alternately or additionally, these actions can be associated with a task that is different from the tasks associated with the actions performed by steps 1008 and/or 1012. The method can then continue to receive inputs of the first, second, and/or third modality types and perform additional actions associated with the same or different tasks.
  • a user can complete a single task or various tasks using multiple different modalities with smooth continuous modal handoffs between the modalities.
  • the modalities can include voice, touch, and controls such as a jog dial.
  • Smooth modal handoffs permit the user to easily change their input modality depending on their context. So, for example, if a user initiates a task using a voice modality and finds themselves in heavy traffic, they may continue to perform the task using the voice modality until they are less busy driving, e.g., at a stoplight or in light traffic. That is, the user is able to naturally move between these different input modalities in any suitable combination. For example, the user can smoothly move between (1) voice and touch, (2) voice and jog dial, (3) voice, touch, and jog dial or any combination thereof.
  • voice-only experiences can be tailored based on a user's context.
  • the user's context can include, by way of example and not limitation, the user's drive scenario, cognitive load, and the like.
  • the voice experience can be dynamically adapted to accommodate the user's context in a manner that promotes driving safety.
  • the user can be prompted to utilize a particular response type. In this manner, the user is free to choose a response type that is best suited for their current context.
  • FIG. 11 illustrates a user driving their car and engaging in a dialogue with their interaction module or personal assistant.
  • the user has entered the car and connected their mobile device with their vehicle's entertainment system. Accordingly, the mobile device knows that the user is driving.
  • the interaction module is represented by the concentric circles icon and the user is represented by the user icon.
  • the user engages the interaction module which, in turn responds "How can I help?"
  • the user responds "What's my day like?”
  • the interaction module ascertains, from the user's calendar application, whether the user has any appointments and responds "You have a meeting at 10 with your banker. Hear more?" The user next responds "No thanks.”
  • the interaction module notifies the user by saying "You have a text from your brother. Do you want to hear it?" By asking the user if they want to hear the text message, and because the mobile device knows that the user is driving, the interaction module is providing an opportunity for a safer modality than displaying a message on either the mobile device's screen or the console's display device. The user responds "No.”
  • the interaction module Sometime later the user receives a call and the interaction module notifies the user by saying "Incoming call from your wife. Answer it?" The user responds "Yes” and has a short conversation with his wife. During the course of the conversation, the user learns that his brother has been trying to reach him. The user then engages the interaction module which responds "How can I help?" The user tells the interaction module to "Read the latest message from my brother.” The interaction module responds '"Hey Bro— let's have dinner tonight.' Reply, callback, or are you done?” In this particular instance, the interaction module prompts the user as to whether the user wishes to use a particular response type, i.e., a text reply or a telephone call.
  • a particular response type i.e., a text reply or a telephone call.
  • the interaction module provides the user with an opportunity to select a communication medium that is most convenient given their particular driving context. Responsive to this prompt, the user states “Reply.” The interaction module that asks the user "What's your reply?" To which the user responds "Sure. Eight o'clock. I'll make reservations and let you know.” [0086] After confirming the content of the reply, the interaction module asks
  • the interaction module responds "How can I help?"
  • the user replies “Remind me to make a dinner reservation when I get to work.”
  • the interaction module replies “okay. I'll remind you to make a dinner reservation when you get to work. Is that right?”
  • the user responds "Yes.” to which the interaction module responds "Great. I added the reminder.”
  • FIG. 12 illustrates a user driving their car and engaging in a dialogue with their interaction module or personal assistant.
  • the user has activated their personal assistant or interaction module.
  • the interaction module responds "How can I help?"
  • the user responds "Play some music like Coldplay.”
  • the interaction module responds "Okay. I'll play your Coldplay music on Xbox music.”
  • the interaction module responds "In two miles take a right turn on Mercer Street.” Sometime later the interaction module is again activated and responds "How can I help?" The user says “Next track” in order to change to the next song. The interaction module responds "Okay. Next track.”
  • the interaction module offers up proactive assistance to the user. Specifically, by notifying the user that there is an accident on the driving route, the interaction module proactively enables a user to make a decision with respect to their driving route. In addition, the interaction module proactively determines a detour to recommend to the user.
  • This example also illustrates mobile device's contextual awareness of the user's driving situation. That is, by being contextually aware, the interaction module is able to provide intelligent suggestions and prompts to improve the user's experience. Moreover, this example illustrates the system's ability to maintain an understanding of the context of the user's experience so that subsequent input with respect to the user's experience can be accurately acted upon.
  • the user initiates the experience by playing music and is subsequently interrupted by the system with the notification pertaining to an accident.
  • the user engages the system to change to the next track.
  • the system maintains an understanding of the context of the user's experience and is able to resume the user's music experience where it left off.
  • the system enables interruption of a first task associated with a first application (e.g., playing music using a media player application) by a second different task associated with a second different application (e.g., being redirected by a map application).
  • the user may engage with the application using multiple different modalities and may seamless shift between a current task and a subsequent task and back.
  • the interaction module can make decisions regarding how to present the user experience. So, for example, if the user receives a text message, the interaction module can elect to delay the notification to the user until a later time when the user is not driving in rush hour traffic. The same can be said for notifications or prompts of any type.
  • This example also illustrates how the personal assistant experience can be adapted as between mobile and non-mobile scenarios. Specifically, in non-mobile scenarios, notifications can be provided as soon as an event occurs, e.g., receiving a text message. In mobile scenarios, however, such notifications might be modified in terms of the timing.
  • the interaction module might suggest “You should get gas as soon as possible. There is a Shell station at the next exit.” In this manner, the interaction module is able to work in cooperation with other applications executing on the user's mobile phone and/or applications executing remotely, e.g., in the "cloud”, and make contextually-appropriate suggestions based on information gleaned from these other applications.
  • the system may note that the user enjoys alternative music. When the user drives through Southern California, the system might notify the user that "Hey, you're into alternative music and driving through Southern California. There are some great local bands you may want to learn about. Would you like to hear about them?"
  • FIG. 13 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • the method can be performed in any suitable hardware, software, firmware, or combination thereof.
  • the method is performed by a suitably-configured mobile device such as a mobile phone.
  • Step 1300 ascertains that a mobile phone is traveling in a vehicle.
  • the step can be performed in any suitable way.
  • the step can be performed when an operative connection is established between the mobile phone and the vehicle's entertainment system.
  • step 1302 modifies a personal assistant experience associated with the mobile phone. This can be done in any suitable way.
  • this step can be performed by using a voice modality for notifications rather than other modalities such as the phone's display screen.
  • notifications may be provided by simply displaying a notification on the phone's display screen, or perhaps by using a badge or icon.
  • voice notifications might be used in place of or in addition to displaying notifications in order to promote driving safety.
  • the user need not look at the phone screen in order to receive the notification.
  • This step can also be performed by suggesting response types that lend themselves more safely to the driving scenario. For example, responsive to receiving a text message and notifying the user, the personal assistant might suggest response types that do not require the user to look away from the road, e.g., text reply, telephone call, voice over IP call, and the like.
  • the step can be performed by adjusting the timing of notifications. Specifically, as in the example above, if a user is in rush hour traffic, a notification might be delayed until such time when the user is not in the rush-hour traffic. [0098) FIG.
  • FIG. 14 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • the method can be performed in any suitable hardware, software, firmware, or combination thereof.
  • the method is performed by a suitably-configured mobile device such as a mobile phone.
  • Step 1400 ascertains that a mobile phone is traveling in a vehicle. Examples of how this can be done are provided above.
  • Step 1402 ascertains a current driving context.
  • This step can be performed in any suitable way.
  • the mobile phone can ascertain a current driving context (e.g., current location, traffic conditions, weather conditions, road construction, and the like) based on communication with a remote source such as a web service.
  • a remote source such as a web service.
  • step 1404 provides proactive notification associated with the current driving context. So, for example, based on a current location and traffic conditions, the phone device's personal assistant may recommend alternate routes.
  • the personal assistant may issue weather-related warnings, e.g., "There is a tornado warning for your current location. Please consider finding a safe place, such as an overpass, to pull off the road.” 100100] Having considered various embodiments associated with tailoring the voice-only experience, consider now a discussion of how the user interface can be tailored for jog dial and touchscreen.
  • targets include objects that can be tabbed through for jog dial input, and sized to accommodate touch input. Any suitable type of objects can be utilized, examples of which include tiles or icons.
  • FIG. 15 illustrates the console 106 from FIG. 3 with like numerals being used to depict like components.
  • individual tiles are shown being displayed by the console 106.
  • the tiles are sized to be easily touch- selected by a user.
  • navigation through the tiles can be facilitated with the jog dial 112 in a tabbed-through manner. Specifically, navigation can begin with a tile at the upper left and, by rotating the jog dial in the clockwise direction, the next rightmost tile in line can be navigated to. This can continue until the end of the first row is reached (i.e.
  • input to complete a particular task can be switched between jog dial and touch in a predictable, seamless fashion.
  • a user has touch-selected a map to facilitate their navigation. They wish to zoom in on the map to get a more granular visual of their current location.
  • a user interface instrumentality on the map can permit the user to execute multiple touch inputs to zoom the map, as an alternative the jog dial can be used. This alleviates the user from having to remove their eyes from the road each time they selected a touch-zoom. Specifically, once the map has been selected, the user can simply turn the jog dial clockwise to zoom in, or counterclockwise to zoom out. In this manner the user does not have to avert their eyes from the road in order to zoom the map.
  • zoom input can be locked to the jog dial to ensure that, in the event the user wishes to execute a zoom operation, they do so using the safest modality, i.e., one which does not require them to avert their eyes from the road.
  • the safest modality i.e., one which does not require them to avert their eyes from the road.
  • one of the input modalities can be locked out in favor of the other, based upon the context of the user's interaction with the displayed content, e.g., the objects displayed on the console.
  • the user may have selected zoomable content using the jog dial, as by pressing down on the jog dial in the presence of displayed content.
  • the content can be zoomed using touch input such as, a two finger pinch gesture.
  • the jog dial can be utilized to toggle across the displayed controls to select the zoom modality, press on it, and then perhaps have a slider control displayed that can be adjusted by touch or the jog dial.
  • Methods in accordance with the embodiment described just above can be performed in a manner similar to that described in connection with FIG. 10. That is, input can be received by way of modalities other than the jog dial in order to initiate a task or perform actions within a task. The user can then switch to the jog dial to provide input as appropriate. For example, in some instances, input may be locked such that at some particular points during performance of the task, input can only be provided by way of the jog dial. Alternately or additionally, the jog dial can be utilized in performance of the task to navigate various controls whereupon input by way of other input modalities can be utilized to further perform actions within the task.
  • FIG. 15A is in is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • the method can be performed in any suitable hardware, software, firmware, or combination thereof.
  • the method is performed by a system that includes a suitably-configured mobile device such as a mobile phone, and an in- vehicle information/entertainment system.
  • Step 1500 displays an array of objects on a console of an in- vehicle information/entertainment system.
  • the step can be performed in any suitable way using any suitable type of objects.
  • the console's display can be driven by content and applications that reside on the mobile phone.
  • the objects that can be displayed can comprise any suitable types of objects examples of which include tiles, icons, and the like.
  • the array of objects comprises a collection of tiles that are displayed in rows and columns.
  • Step 1502 enables interaction with the array of objects by way of a jog dial or touch input. In this manner, a user is free to engage the array of objects using either modality.
  • Step 1504 receives input to accomplish a task with one of the jog dial or touch.
  • tasks can include navigating through the array of objects to eventually make a selection.
  • Step 1506 performs at least one action associated with the received input.
  • such action can include visually navigating through the objects to enable the user to make a selection.
  • Step 1508 receives input to accomplish the task with the other of the jog dial or touch.
  • the user can seamlessly switch modalities in order to accomplish the same task. For example, if the first received input was by way of the jog dial, a navigation would be performed to navigate through the individual objects of the array. Upon reaching an object of interest, the user may then touch the object to select it.
  • Step 1510 performs at least one additional action associated with the other received input. This can include, for example, launching content associated with a selected object.
  • the user interface displayed on the console can be adapted to facilitate navigation and content consumption using the jog dial and the touch screen.
  • FIG. 16 which displays a portion of a user's contact list.
  • the contact list has many entries and if a user wishes to call a particular contact while driving, they are faced with a problem of navigating the many entries of the contact list to find the particular contact of interest.
  • the list is configured to include an affordance that enables the user to jump by letter.
  • the jump-by-letter feature is accessed by selecting a particular letter as shown in the figure. There, the user has touch-selected the letter "a".
  • a grid of selectable letters is provided to enable the user to jump to a particular letter.
  • the letter grid is shown separate from the console.
  • the user has touch selected the letter "m”.
  • the contacts starting with the letter "m” occurs, such as that shown in FIG. 18.
  • the user can select a particular contact— here, "Mandrake Short” with whom to communicate. Once the contact is selected, the user can be presented with several communication options, such as those shown in FIG. 19.
  • FIG. 19A is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • the method can be performed in any suitable hardware, software, firmware, or combination thereof.
  • the method is performed by a suitably-configured mobile device such as a mobile phone and in-vehicle entertainment/information system.
  • Step 1900 displays a portion of a traversable list.
  • the traversable list can include content from the mobile phone.
  • the mobile phone is operably coupled to the in-vehicle entertainment/information system as described above. In this manner, the mobile phone's content can be displayed on the vehicle's console.
  • Any suitable type of traversable list can be provided, an example of which is a user's contact list as described above.
  • Step 1902 receives selection of a list object.
  • Any suitable type of list object can be the subject of the received selection.
  • the selection was received with respect to a particularly-displayed letter.
  • the traversable list can include list objects that enable navigation to other locations within the list, and list objects that include content of the list.
  • list objects that enable navigation to other locations include displayed letters, while objects that include content of the list include individual contacts of the user.
  • step 1904 navigates or enables navigation to a different portion of the traversable list. This step can be performed in any suitable way.
  • the step can be performed by displaying an array or grid of objects that enable navigation to different portions of the traversable list.
  • the array or grid of objects that enable navigation two different portions of the list include individual letters that may be selected.
  • step 1904 completes its navigation to a portion of the list corresponding to the selected letter.
  • Step 1906 receives selection of a list object.
  • This step can be performed by receiving selection of a list object that includes content of the list.
  • this step can be performed by receiving selection of an individual contact that appears within the list.
  • step 1908 performs functionality associated with the list. Any suitable type of functionality can be performed. In the contact list example above, such functionality can include presenting several different communication options that can be selected by a user for communicating with a selected contact.
  • FIG. 20 There, a large letter "e” is displayed. By spinning the jog dial quickly, the letters can be quickly navigated to arrive at a desired letter such as, for example, the letter "h” as shown in FIG. 21. Now, by pressing the jog dial, the user is returned to the place in the list corresponding to the selected letter such as shown in FIG. 22.
  • FIG. 22A is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • the method can be performed in any suitable hardware, software, firmware, or combination thereof.
  • the method is performed by a suitably-configured mobile device such as a mobile phone and in-vehicle entertainment/information system.
  • Step 2200 displays, on a vehicle console, one or more letters.
  • This step can be performed in any suitable way. For example, in at least some embodiments, a single letter can be displayed. Alternately or additionally, in at least some embodiments, multiple letters can be displayed such as a series of three or four letters.
  • Step 2202 receives user input via a jog dial. This input can be received as a result of the user spinning the jog dial in a particular direction, e.g., clockwise or counterclockwise.
  • Step 2204 cycles through letters as a function of the jog dial spin speed. In the illustrated and described example, cycling through the letters can include displaying, for a brief instant, individual letters in a serial fashion until arriving at a destination letter.
  • Step 2206 receives a letter selection via the jog dial.
  • This step can be performed, for example, by receiving user input that depresses the jog dial or otherwise engages the jog dial in a manner indicating a desire to select a letter.
  • step 2208 displays a list portion starting with entries corresponding to the selected letter. For example, as in the FIG. 22 example, entries starting with the selected letter "FT can be displayed.
  • the jog dial may be used to navigate the list portion, forwards and backwards, to arrive at a desired entry. Once the desired entry is selected, functionality including communication-five functionality can be exposed to the user to enable them to communicate with a selected entry.
  • the user interface experience as between the two can be different. This can be for number of reasons not the least of which is safety. Similarly, if a user is engaged with their mobile device outside the context of the vehicle, one assumes that the user's full attention is being paid to their user interface experience with the mobile device. On the other hand, when the user is in their car using their mobile device to interface with the vehicle's console, less than the user's full attention is being paid to the user interface experience with the console.
  • FIG. 23 shows a side -by-side comparison of the user interface experience of a mobile device versus the user interface experience of the console's display device.
  • pivot control on the mobile device, shown generally at 2300.
  • the pivot control resides in the form of a horizontally scrollable list of pivot items, e.g., "playlists”, “genres”, and the like.
  • playlists e.g., "playlists”
  • genres e.g., "genres”
  • the pivot control can be adapted to present content in a fashion more suitable for an environment in which the user is able to provide less than all their attention to the user interface experience.
  • a first of the adaptations is that the pivot control is presented as a vertical list of tabs that are laid out with all views visible in one glance. This is different from the pivot control in the mobile device because in this particular instance, the user does not have to provide input by way of any input modality in order to see all of the pivot items.
  • the pivot items are also presented with a larger text size than that utilized in the mobile device. This promotes at- a-glance consumption by the user.
  • larger touch targets are presented such as that shown at 2304.
  • the list control displays a sufficient number of list items to fill the mobile device's display. In this particular instance, depending on the size of the text, this could include displaying eight, nine, or 10 or more items.
  • the list control is scrollable, as by being vertically scrollable to access items that are not displayed that appear further down the list.
  • list control adaptations are made.
  • the list control 2308 For example, consider the list control 2308.
  • Various embodiments display a predefined number of list items that is less than the number of list items that are displayed on the mobile device. So, for example, if the mobile device displays 10 items, the console's display device may display only six items in order to promote glanceability and easy consumption.
  • the list control displayed on the console is not continuously scrollable, but rather uses a paging model in order for the user to page through multiple list items at a time.
  • other adaptations can include utilizing larger text sizes and larger target sizes for items appearing in the console's list.
  • visible focus is provided for jog dial input. As an example, the "playlist" item can be highlighted such that the user can easily visually ascertain the location in the pivot control and can provide jog dial input to move up and down items in the pivot control.
  • FIG. 24 illustrates a media element control 2400 on the mobile device, and a media element control 2402 on the console's display device.
  • the media element control can enable the user to play both audio and video content.
  • the media element control on the console can be configured to enable only audio to be played and not video content.
  • larger touch targets such as play and pause buttons and visible focus for the jog dial input are provided.
  • a panorama control can be provided on the phone to enable user to pan through content or items.
  • any such time where the user interface experience on the mobile device would enable a panorama control the panorama control is disallowed on the console and instead, is replaced with a pivot control.
  • One reason for replacing the panorama control with a pivot control is that panorama controls tend to rely heavily on the use of swipe gestures and animation. By replacing the panorama control with a pivot control, the user can devote less attention to content that appears in the pivot control in order to make selections or navigations.
  • Grid controls tend to work well in the context of mobile devices, when the user can devote their attention to the navigation experience.
  • Grid control navigation experiences can tend to be somewhat free, unpredictable, and dynamic. For example, a user can typically, through various types of swipe gestures, traverse through a grid in a seemingly unpredictable way in order to access the grid's content.
  • the grid control user experience of the mobile device can be replaced with a list type experience such as that shown in FIG. 23.
  • the list experience in the context of the console's display device, can promote a more predictable and consistent traversal experience, particularly with respect to jog dial input.
  • FIG. 25 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • the steps can be implemented in connection with any suitable hardware, software, firmware, or combination thereof.
  • the method can be implemented by a suitably configured system such as a mobile device and an in- vehicle information/entertainment system.
  • Step 2500 couples a mobile device with an in-vehicle information/entertainment system.
  • Step 2502 adapts a user interface experience associated with the mobile device to a user interface experience associated with the in- vehicle information/entertainment system.
  • Adaptations can take place in any suitable way.
  • a pivot control on the mobile device can be adapted from using a scrollable list of pivot items to using a list-type visualization in which all views are visible at the same time.
  • list controls on the mobile device can be adapted from using a scrollable list to using a paging model in order for the user to page through multiple items at a time.
  • Further adaptations can include, by way of example and not limitation, restricting media element controls from enabling both audio and video on the mobile device to enabling only audio to be played on the console of the in-vehicle information/entertainment system.
  • various grid control adaptations can be made to adapt the grid control navigation experience from a somewhat free and unpredictable experience on the mobile device, to a more linear, serialized and predictable navigation experience as noted above.
  • the mobile device is able to render to multiple different screen types that might be part of a vehicle's hardware.
  • various screen types can include, by way of example and not limitation, screen types associated with a console such as that described above, a so-called cluster which may include one or more sub-screens, a head's up display (HUD) in which content is rendered on the vehicle's windshield and the like.
  • HUD head's up display
  • System 2600 includes a mobile device 2602 that includes, among other components, one or more applications 2604, a rules engine 2606, a display driver module 2608 and various different screen types including, by way of example and not limitation, a console 2610, a cluster 2612 (typically in the driver's dashboard and including a speedometer and other gauges), a sub screen 2614 within cluster 2612, and a heads-up display 2616.
  • a console 2610 typically in the driver's dashboard and including a speedometer and other gauges
  • sub screen 2614 within cluster 2612 typically in the driver's dashboard and including a speedometer and other gauges
  • heads-up display 2616 a heads-up display 2616.
  • applications 2604 can be written to be screen-type agnostic. By this is meant that application developers can write their applications to perform various types of functionality that results in renderable content being produced.
  • the renderable content can be rendered to multiple different types of screens in accordance with properties and characteristics associated with the screens.
  • rules engine 2606 provides a container that includes various rules associated with the screen types that are present within a particular vehicle.
  • Individual rules can specify properties and characteristics associated with content that is to be rendered on any one particular type of screen. This can include, by way of example and not limitation, content formatting rules, aesthetic rules, visual design rules, culturally relevant rules, geographically relevant rules, language specific rules, reading direction rules (e.g., right-to-left rules, left-to-right rules), driver seat configuration rules (e.g., left side/right side driver seat), voice interaction rules, and the like.
  • an application such as a media player application, is connected to the in- vehicle information/entertainment system, it produces renderable content that can be rendered to the multiple different types of screens.
  • the rules engine 2606 can provide a set of rules that the application can use to format content for rendering on multiple different screen types.
  • the display driver module 2608 receives data and information from the application and works in concert with the rules engine 2606 to drive the display on one or more of the particular screen types.
  • media content can be displayed on the display device of the console 2610, while notifications, alerts, and prompts can be provided to, and displayed by cluster 2612.
  • the rules engine 2606 contains the rules for each particular screen type and, accordingly, can cause the application or display driver module 2608 to format data in an appropriate manner to be displayed on the different types of screens. In this manner, application developers can write applications to simply produce renderable content without regard for the type of screen on which the content is to be rendered.
  • the rules engine 2606 and the application or display driver module 2608 work in concert to ensure that the content produced by any one particular application can be appropriately rendered to the various screens in a format that is appropriate for that screen type.
  • an adaptive user interface was described in connection with renderable content.
  • the adaptive user interface can be further extended to the notion of so-called universal controls. That is, using the adaptive user interface model, application developers can develop their applications in a manner that is agnostic with respect to how controls are rendered. That is, controls can include both hard controls and soft controls. Such controls can include lists, selections, menus, buttons, pads, dials, and the like.
  • rules from rules engine 2806 indicate to the application constraints, properties, and characteristics of controls that are to be rendered on the various screen types.
  • the rules may indicate how many controls are to be rendered, control sizes, font sizes, and the like.
  • the application is then able to adapt its controls to fit within the screen sizes as defined by the rules that it receives. This means that the application need not be custom written and, as in the above example, greatly facilitates an application developer's job in writing applications. That is, the applications can be written for universal screen sizes that are part of the phone and the vehicle's system.
  • a good example of the adaptability of controls appears in Figures 23 and 24 and the related discussion above.
  • Use of the rules engine in this regard also promotes flexibility in adapting user interface elements, such as controls, in the face of changes to regulations governing vehicle user interfaces. For example, if a regulatory change takes place which modifies the requirements of vehicle user interfaces, a simple change to the rules that appear in the rules engine 2606 can take place without requiring any applications to be rewritten. That is, application developers can now write their applications to a "universal control" rather than to particular applicable regulations.
  • FIG. 27 is a flow diagram that describes steps in a method in accordance with one or more embodiments.
  • the steps can be implemented in connection with any suitable hardware, software, firmware, or combination thereof.
  • the method can be implemented by a suitably configured system such as a mobile device and an in- vehicle information/entertainment system.
  • Step 2700 couples a mobile device with an in- vehicle information/entertainment system of a vehicle.
  • Step 2702 launches an application on the mobile device.
  • Step 2704 ascertains one or more rules associated with rendering content and/or controls on one or more screen types associated with the vehicle.
  • This step can be performed in any suitable way.
  • the step can be performed by an application executing on the mobile device.
  • this step can be performed by a display driver module that works in concert with the application to provide content and controls that are to be rendered on the screen types.
  • Step 2706 uses the rules to adapt the content and/or controls that are to be rendered on screen types.
  • Step 2908 causes the adapted content and/or controls to be rendered on the screen types.
  • Example Device can be utilized to implement the embodiments described above.
  • Various elements about to be described can be used to implement both the mobile device and aspects of the in-vehicle information/entertainment device.
  • FIG. 28 illustrates various components of an example device 2800 that can be implemented as any type of computing device that can be used in connection with embodiments described above.
  • Device 2800 includes communication devices 2802 that enable wired and/or wireless communication of device data 2804 (e.g., received data, data that is being received, data scheduled for broadcast, data packets of the data, etc.).
  • the device data 2804 or other device content can include configuration settings of the device, media content stored on the device, and/or information associated with a user of the device.
  • Media content stored on device 2800 can include any type of audio, video, and/or image data.
  • Device 2800 includes one or more data inputs 2806 via which any type of data, media content, and/or inputs can be received, such as user-selectable inputs, messages, music, television media content, recorded video content, and any other type of audio, video, and/or image data received from any content and/or data source.
  • any type of data, media content, and/or inputs can be received, such as user-selectable inputs, messages, music, television media content, recorded video content, and any other type of audio, video, and/or image data received from any content and/or data source.
  • Device 2800 also includes communication interfaces 2808 that can be implemented as any one or more of a serial and/or parallel interface, a wireless interface, any type of network interface, a modem, and as any other type of communication interface.
  • the communication interfaces and 2808 provide a connection and/or communication links between device 2800 and a communication network by which other electronic, computing, and communication devices communicate data with device 2800.
  • Device 2800 includes one or more processors 2810 (e.g., any of microprocessors, controllers, and the like) which process various computer-executable instructions to control the operation of device 2800 and to implement embodiments of the techniques described herein.
  • processors 2810 e.g., any of microprocessors, controllers, and the like
  • device 2800 can be implemented with any one or combination of hardware, firmware, or fixed logic circuitry that is implemented in connection with processing and control circuits which are generally identified at 2812.
  • device 2800 can include a system bus or data transfer system that couples the various components within the device.
  • a system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures.
  • Device 2800 also includes computer-readable media 2814, such as one or more memory components, examples of which include random access memory (RAM), non- volatile memory (e.g., any one or more of a read-only memory (ROM), flash memory, EPROM, EEPROM, etc.), and a disk storage device.
  • RAM random access memory
  • non- volatile memory e.g., any one or more of a read-only memory (ROM), flash memory, EPROM, EEPROM, etc.
  • a disk storage device may be implemented as any type of magnetic or optical storage device, such as a hard disk drive, a recordable and/or rewriteable compact disc (CD), any type of a digital versatile disc (DVD), and the like.
  • Device 2800 and can also include a mass storage media device 2816.
  • Computer-readable media 2814 provides data storage mechanisms to store the device data 2804, as well as various device applications 2818 and any other types of information and/or data related to operational aspects of device 2800.
  • an operating system 2820 can be maintained as a computer application with the computer- readable media 2814 and executed on processors 2810.
  • the device applications 2818 can include a device manager (e.g., a control application, software application, signal processing and control module, code that is native to a particular device, a hardware abstraction layer for a particular device, etc.).
  • the device applications 2818 also include any system components or modules to implement embodiments of the techniques described herein.
  • the device applications 2818 include an interface application 2822 and a gesture capture driver 2824 that are shown as software modules and/or computer applications.
  • the gesture capture driver 2824 is representative of software that is used to provide an interface with a device configured to capture a gesture, such as a touchscreen, track pad, camera, and so on.
  • the interface application 2822 and the gesture capture driver 2824 can be implemented as hardware, software, firmware, or any combination thereof.
  • computer readable media 2814 can include a web platform 2825 that provides browser functionality.
  • Device 2800 also includes an audio and/or video input-output system 2826 that provides audio data to an audio system 2828 and/or provides video data to a display system 2830.
  • the audio system 2828 and/or the display system 2830 can include any devices that process, display, and/or otherwise render audio, video, and image data.
  • Video signals and audio signals can be communicated from device 2800 to an audio device and/or to a display device via an RF (radio frequency) link, S-video link, composite video link, component video link, DVI (digital video interface), analog audio connection, or other similar communication link.
  • the audio system 2828 and/or the display system 2830 are implemented as external components to device 2800.
  • the audio system 2828 and/or the display system 2830 are implemented as integrated components of example device 2800.
  • Various embodiments enable mobile devices, such as phones and the like, to integrate with an in- vehicle information/entertainment system to enable the user to control the in- vehicle information/entertainment system by way of their mobile phone. Users can leverage the functionality of their mobile phone to promote an in-vehicle experience which can be contextually tailored to the user's or the vehicle's context.
  • a user can complete various tasks using multiple different modalities with smooth continuous modal handoffs between the modalities.
  • the modalities can include voice, touch, and controls such as a jog dial. Smooth modal handoffs permit the user to easily change their input modality depending on their context.
  • FIG. 1 Other embodiments can tailor the voice-only experience based on drive scenarios and the user's cognitive load. Yet other embodiments can tailor the user experience for jog dial and touchscreen modalities. Further embodiments can provide an adaptive user interface including an adaptive user interface that can operate in connection with multiple different types of screens, e.g., a phone screen, a cluster screen, a console screen, and a heads up display (HUD) screen, and the like. Still further embodiments provide a universal command/control model for multiple types of physical input including button jogs, capacitive dials, hard keys, pads, and the like.
  • HUD heads up display

Landscapes

  • Engineering & Computer Science (AREA)
  • Combustion & Propulsion (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Chemical & Material Sciences (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Multimedia (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computing Systems (AREA)
  • Medical Informatics (AREA)
  • User Interface Of Digital Computer (AREA)
  • Navigation (AREA)
  • Telephone Function (AREA)
  • Position Input By Displaying (AREA)

Abstract

Divers modes de réalisation permettent à des dispositifs mobiles, tels que des téléphones et analogues, d'être intégrés à un système d'informations/divertissement véhiculaire afin de permettre à l'utilisateur de commander le système d'informations/divertissement véhiculaire au moyen de son téléphone mobile. Les utilisateurs peuvent tirer profit de la fonctionnalité de leur téléphone mobile de façon à favoriser une expérience véhiculaire pouvant être personnalisée de manière contextuelle en fonction du contexte de l'utilisateur ou du véhicule. Encore d'autres modes de réalisation permettent de fournir une expérience véhiculaire par l'intermédiaire d'un service en nuage.
EP15801074.4A 2014-11-20 2015-11-16 Interface multimodale embarquée Active EP3221783B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/549,496 US10116748B2 (en) 2014-11-20 2014-11-20 Vehicle-based multi-modal interface
PCT/US2015/060775 WO2016081326A1 (fr) 2014-11-20 2015-11-16 Interface multimodale embarquée

Publications (2)

Publication Number Publication Date
EP3221783A1 true EP3221783A1 (fr) 2017-09-27
EP3221783B1 EP3221783B1 (fr) 2021-09-01

Family

ID=54704132

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15801074.4A Active EP3221783B1 (fr) 2014-11-20 2015-11-16 Interface multimodale embarquée

Country Status (11)

Country Link
US (1) US10116748B2 (fr)
EP (1) EP3221783B1 (fr)
JP (1) JP7093181B2 (fr)
KR (1) KR102416405B1 (fr)
CN (1) CN107077317A (fr)
AU (1) AU2015350267B2 (fr)
BR (1) BR112017008421A2 (fr)
CA (1) CA2965703C (fr)
MX (1) MX2017006086A (fr)
RU (1) RU2707410C2 (fr)
WO (1) WO2016081326A1 (fr)

Families Citing this family (155)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9318108B2 (en) 2010-01-18 2016-04-19 Apple Inc. Intelligent automated assistant
US8977255B2 (en) 2007-04-03 2015-03-10 Apple Inc. Method and system for operating a multi-function portable electronic device using voice-activation
US8676904B2 (en) 2008-10-02 2014-03-18 Apple Inc. Electronic devices with voice command and contextual data processing capabilities
US10706373B2 (en) 2011-06-03 2020-07-07 Apple Inc. Performing actions associated with task items that represent tasks to perform
US10276170B2 (en) 2010-01-18 2019-04-30 Apple Inc. Intelligent automated assistant
US10417037B2 (en) 2012-05-15 2019-09-17 Apple Inc. Systems and methods for integrating third party services with a digital assistant
KR20240132105A (ko) 2013-02-07 2024-09-02 애플 인크. 디지털 어시스턴트를 위한 음성 트리거
US10652394B2 (en) 2013-03-14 2020-05-12 Apple Inc. System and method for processing voicemail
US10748529B1 (en) 2013-03-15 2020-08-18 Apple Inc. Voice activated device for use with a voice-based digital assistant
KR101772152B1 (ko) 2013-06-09 2017-08-28 애플 인크. 디지털 어시스턴트의 둘 이상의 인스턴스들에 걸친 대화 지속성을 가능하게 하기 위한 디바이스, 방법 및 그래픽 사용자 인터페이스
US10176167B2 (en) 2013-06-09 2019-01-08 Apple Inc. System and method for inferring user intent from speech inputs
DE112014003653B4 (de) 2013-08-06 2024-04-18 Apple Inc. Automatisch aktivierende intelligente Antworten auf der Grundlage von Aktivitäten von entfernt angeordneten Vorrichtungen
US9715875B2 (en) 2014-05-30 2017-07-25 Apple Inc. Reducing the need for manual start/end-pointing and trigger phrases
CN110797019B (zh) 2014-05-30 2023-08-29 苹果公司 多命令单一话语输入方法
US10170123B2 (en) 2014-05-30 2019-01-01 Apple Inc. Intelligent assistant for home automation
US9338493B2 (en) 2014-06-30 2016-05-10 Apple Inc. Intelligent automated assistant for TV user interactions
US10073599B2 (en) 2015-01-07 2018-09-11 Microsoft Technology Licensing, Llc Automatic home screen determination based on display device
US9886953B2 (en) 2015-03-08 2018-02-06 Apple Inc. Virtual assistant activation
DE102015204336B4 (de) * 2015-03-11 2019-01-31 Volkswagen Aktiengesellschaft Verfahren und Vorrichtung zur Integration von Fahrzeug-Applikationen
US10460227B2 (en) 2015-05-15 2019-10-29 Apple Inc. Virtual assistant in a communication session
US10200824B2 (en) 2015-05-27 2019-02-05 Apple Inc. Systems and methods for proactively identifying and surfacing relevant content on a touch-sensitive device
WO2016210004A1 (fr) * 2015-06-25 2016-12-29 Airbiquity Inc. Élément de véhicule automobile pour utiliser une ressource de police de caractères ou de caractère d'un dispositif électronique séparé
US20160378747A1 (en) * 2015-06-29 2016-12-29 Apple Inc. Virtual assistant for media playback
US9699298B2 (en) * 2015-08-10 2017-07-04 Microsoft Technology Licensing, Llc Smart automatic composition of short messaging responses
US10747498B2 (en) 2015-09-08 2020-08-18 Apple Inc. Zero latency digital assistant
US10740384B2 (en) 2015-09-08 2020-08-11 Apple Inc. Intelligent automated assistant for media search and playback
US10331312B2 (en) 2015-09-08 2019-06-25 Apple Inc. Intelligent automated assistant in a media environment
US10671428B2 (en) 2015-09-08 2020-06-02 Apple Inc. Distributed personal assistant
US11587559B2 (en) 2015-09-30 2023-02-21 Apple Inc. Intelligent device identification
KR20170045662A (ko) * 2015-10-19 2017-04-27 삼성전자주식회사 전자 장치 및 알림 제어 방법
US10691473B2 (en) 2015-11-06 2020-06-23 Apple Inc. Intelligent automated assistant in a messaging environment
US10956666B2 (en) 2015-11-09 2021-03-23 Apple Inc. Unconventional virtual assistant interactions
US10223066B2 (en) 2015-12-23 2019-03-05 Apple Inc. Proactive assistance based on dialog communication between devices
US10097919B2 (en) 2016-02-22 2018-10-09 Sonos, Inc. Music service selection
US9947316B2 (en) 2016-02-22 2018-04-17 Sonos, Inc. Voice control of a media playback system
US9965247B2 (en) 2016-02-22 2018-05-08 Sonos, Inc. Voice controlled media playback system based on user profile
US10095470B2 (en) 2016-02-22 2018-10-09 Sonos, Inc. Audio response playback
US9811314B2 (en) 2016-02-22 2017-11-07 Sonos, Inc. Metadata exchange involving a networked playback system and a networked microphone system
US10264030B2 (en) 2016-02-22 2019-04-16 Sonos, Inc. Networked microphone device control
US10423292B2 (en) * 2016-05-17 2019-09-24 Google Llc Managing messages in vehicles
US9978390B2 (en) 2016-06-09 2018-05-22 Sonos, Inc. Dynamic player selection for audio signal processing
US10586535B2 (en) 2016-06-10 2020-03-10 Apple Inc. Intelligent digital assistant in a multi-tasking environment
DK201670540A1 (en) 2016-06-11 2018-01-08 Apple Inc Application integration with a digital assistant
DK179415B1 (en) 2016-06-11 2018-06-14 Apple Inc Intelligent device arbitration and control
US10474946B2 (en) 2016-06-24 2019-11-12 Microsoft Technology Licensing, Llc Situation aware personal assistant
US10152969B2 (en) 2016-07-15 2018-12-11 Sonos, Inc. Voice detection by multiple devices
US10134399B2 (en) 2016-07-15 2018-11-20 Sonos, Inc. Contextualization of voice inputs
US10115400B2 (en) 2016-08-05 2018-10-30 Sonos, Inc. Multiple voice services
US9942678B1 (en) 2016-09-27 2018-04-10 Sonos, Inc. Audio playback settings for voice interaction
US9743204B1 (en) 2016-09-30 2017-08-22 Sonos, Inc. Multi-orientation playback device microphones
US10181323B2 (en) 2016-10-19 2019-01-15 Sonos, Inc. Arbitration-based voice recognition
US10203216B2 (en) 2016-12-31 2019-02-12 Spotify Ab Duration-based customized media program
US11204787B2 (en) 2017-01-09 2021-12-21 Apple Inc. Application integration with a digital assistant
JP6824047B2 (ja) * 2017-01-20 2021-02-03 株式会社クボタ 作業車
US11183181B2 (en) 2017-03-27 2021-11-23 Sonos, Inc. Systems and methods of multiple voice services
US10726832B2 (en) 2017-05-11 2020-07-28 Apple Inc. Maintaining privacy of personal information
DK180048B1 (en) 2017-05-11 2020-02-04 Apple Inc. MAINTAINING THE DATA PROTECTION OF PERSONAL INFORMATION
DK179745B1 (en) 2017-05-12 2019-05-01 Apple Inc. SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT
DK201770428A1 (en) 2017-05-12 2019-02-18 Apple Inc. LOW-LATENCY INTELLIGENT AUTOMATED ASSISTANT
DK179496B1 (en) 2017-05-12 2019-01-15 Apple Inc. USER-SPECIFIC Acoustic Models
DK201770411A1 (en) 2017-05-15 2018-12-20 Apple Inc. MULTI-MODAL INTERFACES
US20180336892A1 (en) 2017-05-16 2018-11-22 Apple Inc. Detecting a trigger of a digital assistant
US20180336275A1 (en) 2017-05-16 2018-11-22 Apple Inc. Intelligent automated assistant for media exploration
US10475449B2 (en) 2017-08-07 2019-11-12 Sonos, Inc. Wake-word detection suppression
US10048930B1 (en) 2017-09-08 2018-08-14 Sonos, Inc. Dynamic computation of system response volume
US10672379B1 (en) * 2017-09-25 2020-06-02 Amazon Technologies, Inc. Systems and methods for selecting a recipient device for communications
US10446165B2 (en) 2017-09-27 2019-10-15 Sonos, Inc. Robust short-time fourier transform acoustic echo cancellation during audio playback
US10621981B2 (en) 2017-09-28 2020-04-14 Sonos, Inc. Tone interference cancellation
US10482868B2 (en) 2017-09-28 2019-11-19 Sonos, Inc. Multi-channel acoustic echo cancellation
US10051366B1 (en) 2017-09-28 2018-08-14 Sonos, Inc. Three-dimensional beam forming with a microphone array
US10466962B2 (en) 2017-09-29 2019-11-05 Sonos, Inc. Media playback system with voice assistance
US10880650B2 (en) 2017-12-10 2020-12-29 Sonos, Inc. Network microphone devices with automatic do not disturb actuation capabilities
US10818290B2 (en) 2017-12-11 2020-10-27 Sonos, Inc. Home graph
US20190053022A1 (en) * 2017-12-27 2019-02-14 Intel Corporation Provision of in-vehicle service to a mobile device
US11343614B2 (en) 2018-01-31 2022-05-24 Sonos, Inc. Device designation of playback and network microphone device arrangements
US10818288B2 (en) 2018-03-26 2020-10-27 Apple Inc. Natural assistant interaction
US10928918B2 (en) 2018-05-07 2021-02-23 Apple Inc. Raise to speak
US11145294B2 (en) 2018-05-07 2021-10-12 Apple Inc. Intelligent automated assistant for delivering content from user experiences
US11175880B2 (en) 2018-05-10 2021-11-16 Sonos, Inc. Systems and methods for voice-assisted media content selection
US10847178B2 (en) 2018-05-18 2020-11-24 Sonos, Inc. Linear filtering for noise-suppressed speech detection
CN108944450A (zh) * 2018-05-23 2018-12-07 重庆普斯德电子有限公司 双模式汽车仪表显示系统
US10959029B2 (en) 2018-05-25 2021-03-23 Sonos, Inc. Determining and adapting to changes in microphone performance of playback devices
DK179822B1 (da) 2018-06-01 2019-07-12 Apple Inc. Voice interaction at a primary device to access call functionality of a companion device
DK201870355A1 (en) 2018-06-01 2019-12-16 Apple Inc. VIRTUAL ASSISTANT OPERATION IN MULTI-DEVICE ENVIRONMENTS
DK180639B1 (en) 2018-06-01 2021-11-04 Apple Inc DISABILITY OF ATTENTION-ATTENTIVE VIRTUAL ASSISTANT
US10892996B2 (en) 2018-06-01 2021-01-12 Apple Inc. Variable latency device coordination
CN108766474A (zh) * 2018-06-04 2018-11-06 深圳市沃特沃德股份有限公司 车载音乐播放方法及车载设备
US10681460B2 (en) 2018-06-28 2020-06-09 Sonos, Inc. Systems and methods for associating playback devices with voice assistant services
US11076035B2 (en) 2018-08-28 2021-07-27 Sonos, Inc. Do not disturb feature for audio notifications
US10461710B1 (en) 2018-08-28 2019-10-29 Sonos, Inc. Media playback system with maximum volume setting
CN110874202B (zh) 2018-08-29 2024-04-19 斑马智行网络(香港)有限公司 交互方法、设备、介质和操作系统
US10878811B2 (en) 2018-09-14 2020-12-29 Sonos, Inc. Networked devices, systems, and methods for intelligently deactivating wake-word engines
US10587430B1 (en) 2018-09-14 2020-03-10 Sonos, Inc. Networked devices, systems, and methods for associating playback devices based on sound codes
US11024331B2 (en) 2018-09-21 2021-06-01 Sonos, Inc. Voice detection optimization using sound metadata
US10811015B2 (en) 2018-09-25 2020-10-20 Sonos, Inc. Voice detection optimization based on selected voice assistant service
US11100923B2 (en) 2018-09-28 2021-08-24 Sonos, Inc. Systems and methods for selective wake word detection using neural network models
US11462215B2 (en) 2018-09-28 2022-10-04 Apple Inc. Multi-modal inputs for voice commands
US10692518B2 (en) 2018-09-29 2020-06-23 Sonos, Inc. Linear filtering for noise-suppressed speech detection via multiple network microphone devices
US11899519B2 (en) 2018-10-23 2024-02-13 Sonos, Inc. Multiple stage network microphone device with reduced power consumption and processing load
US11475898B2 (en) 2018-10-26 2022-10-18 Apple Inc. Low-latency multi-speaker speech recognition
JP6993314B2 (ja) * 2018-11-09 2022-01-13 株式会社日立製作所 対話システム、装置、及びプログラム
EP3654249A1 (fr) 2018-11-15 2020-05-20 Snips Convolutions dilatées et déclenchement efficace de mot-clé
US11183183B2 (en) * 2018-12-07 2021-11-23 Sonos, Inc. Systems and methods of operating media playback systems having multiple voice assistant services
US11132989B2 (en) 2018-12-13 2021-09-28 Sonos, Inc. Networked microphone devices, systems, and methods of localized arbitration
US10602268B1 (en) 2018-12-20 2020-03-24 Sonos, Inc. Optimization of network microphone devices using noise classification
US11315556B2 (en) 2019-02-08 2022-04-26 Sonos, Inc. Devices, systems, and methods for distributed voice processing by transmitting sound data associated with a wake word to an appropriate device for identification
US10867604B2 (en) 2019-02-08 2020-12-15 Sonos, Inc. Devices, systems, and methods for distributed voice processing
US11348573B2 (en) 2019-03-18 2022-05-31 Apple Inc. Multimodality in digital assistant systems
US20220177067A1 (en) * 2019-03-27 2022-06-09 Tvs Motor Company Limited Smart connect instrument cluster
US11120794B2 (en) 2019-05-03 2021-09-14 Sonos, Inc. Voice assistant persistence across multiple network microphone devices
US11307752B2 (en) 2019-05-06 2022-04-19 Apple Inc. User configurable task triggers
US11423908B2 (en) 2019-05-06 2022-08-23 Apple Inc. Interpreting spoken requests
US11475884B2 (en) 2019-05-06 2022-10-18 Apple Inc. Reducing digital assistant latency when a language is incorrectly determined
DK201970509A1 (en) 2019-05-06 2021-01-15 Apple Inc Spoken notifications
KR20240129085A (ko) * 2019-05-09 2024-08-27 구글 엘엘씨 제한된 아키텍처를 사용하는 서드파티 차량 컴퓨팅 디바이스에 대한 자동화된 어시스턴트 제안
US11140099B2 (en) 2019-05-21 2021-10-05 Apple Inc. Providing message response suggestions
US11289073B2 (en) 2019-05-31 2022-03-29 Apple Inc. Device text to speech
US11496600B2 (en) 2019-05-31 2022-11-08 Apple Inc. Remote execution of machine-learned models
DK180129B1 (en) 2019-05-31 2020-06-02 Apple Inc. USER ACTIVITY SHORTCUT SUGGESTIONS
DK201970511A1 (en) 2019-05-31 2021-02-15 Apple Inc Voice identification in digital assistant systems
US11360641B2 (en) 2019-06-01 2022-06-14 Apple Inc. Increasing the relevance of new available information
US11227599B2 (en) 2019-06-01 2022-01-18 Apple Inc. Methods and user interfaces for voice-based control of electronic devices
US10586540B1 (en) 2019-06-12 2020-03-10 Sonos, Inc. Network microphone device with command keyword conditioning
US11361756B2 (en) 2019-06-12 2022-06-14 Sonos, Inc. Conditional wake word eventing based on environment
US11200894B2 (en) 2019-06-12 2021-12-14 Sonos, Inc. Network microphone device with command keyword eventing
US10871943B1 (en) 2019-07-31 2020-12-22 Sonos, Inc. Noise classification for event detection
US11138969B2 (en) 2019-07-31 2021-10-05 Sonos, Inc. Locally distributed keyword detection
US11138975B2 (en) 2019-07-31 2021-10-05 Sonos, Inc. Locally distributed keyword detection
WO2021056255A1 (fr) 2019-09-25 2021-04-01 Apple Inc. Détection de texte à l'aide d'estimateurs de géométrie globale
US11189286B2 (en) 2019-10-22 2021-11-30 Sonos, Inc. VAS toggle based on device orientation
CN111124332B (zh) * 2019-11-18 2024-03-01 北京小米移动软件有限公司 设备呈现内容的控制方法、控制装置及存储介质
RU2731670C1 (ru) * 2019-12-13 2020-09-07 Сергей Анатольевич Киселев Программно-аппаратный комплекс
US11200900B2 (en) 2019-12-20 2021-12-14 Sonos, Inc. Offline voice control
US11562740B2 (en) 2020-01-07 2023-01-24 Sonos, Inc. Voice verification for media playback
US11556307B2 (en) 2020-01-31 2023-01-17 Sonos, Inc. Local voice data processing
US11308958B2 (en) 2020-02-07 2022-04-19 Sonos, Inc. Localized wakeword verification
US11038934B1 (en) 2020-05-11 2021-06-15 Apple Inc. Digital assistant hardware abstraction
US11061543B1 (en) 2020-05-11 2021-07-13 Apple Inc. Providing relevant data items based on context
US11755276B2 (en) 2020-05-12 2023-09-12 Apple Inc. Reducing description length based on confidence
US11482224B2 (en) 2020-05-20 2022-10-25 Sonos, Inc. Command keywords with input detection windowing
US11727919B2 (en) 2020-05-20 2023-08-15 Sonos, Inc. Memory allocation for keyword spotting engines
US11308962B2 (en) 2020-05-20 2022-04-19 Sonos, Inc. Input detection windowing
KR20210156126A (ko) * 2020-06-17 2021-12-24 현대모비스 주식회사 노브를 이용한 디스플레이 제어 시스템
US11490204B2 (en) 2020-07-20 2022-11-01 Apple Inc. Multi-device audio adjustment coordination
US11438683B2 (en) 2020-07-21 2022-09-06 Apple Inc. User identification using headphones
US11698771B2 (en) 2020-08-25 2023-07-11 Sonos, Inc. Vocal guidance engines for playback devices
US11984123B2 (en) 2020-11-12 2024-05-14 Sonos, Inc. Network device interaction by range
US11523166B1 (en) * 2020-11-30 2022-12-06 Amazon Technologies, Inc. Controlling interface of a multi-input modality device
CN114816158A (zh) * 2021-01-11 2022-07-29 华为技术有限公司 界面的控制方法、装置、电子设备和可读存储介质
US11551700B2 (en) 2021-01-25 2023-01-10 Sonos, Inc. Systems and methods for power-efficient keyword detection
US20230009427A1 (en) * 2021-07-08 2023-01-12 Hyundai Mobis Co., Ltd. Display control system using knobs
US20230035531A1 (en) * 2021-07-27 2023-02-02 Qualcomm Incorporated Audio event data processing
USD985590S1 (en) 2021-08-23 2023-05-09 Waymo Llc Display screen or portion thereof with graphical user interface
EP4428674A3 (fr) * 2021-08-24 2024-10-16 Google LLC Activation proactive de modes de conduite d'assistant automatisé pour différents degrés de confiance de détection de déplacement
CN114179613B (zh) * 2021-12-10 2024-03-05 常州星宇车灯股份有限公司 一种用于副驾驶控制面板上的影音触控交互控制方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120166076A1 (en) * 2010-12-23 2012-06-28 Rody Hardy Predictive Traffic Warning And Suggestive Rerouting System And Method
EP2793116A2 (fr) * 2013-03-26 2014-10-22 Samsung Electronics Co., Ltd. Appareil de terminal pouvant être monté dans un véhicule, dispositif mobile pour travailler avec l'appareil de terminal et procédés de fourniture de service de celui-ci

Family Cites Families (60)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8903737B2 (en) 2000-04-25 2014-12-02 Accenture Global Service Limited Method and system for a wireless universal mobile product interface
JP2002022464A (ja) * 2000-07-05 2002-01-23 Mazda Motor Corp 移動体用情報処理装置、移動体用情報処理方法、及び移動体用情報処理プログラムが記憶された記憶媒体
US7636079B2 (en) 2000-11-29 2009-12-22 Palm Inc. Application access and activation system and method
US20020173344A1 (en) 2001-03-16 2002-11-21 Cupps Bryan T. Novel personal electronics device
US20030153354A1 (en) 2001-03-16 2003-08-14 Cupps Bryan T. Novel personal electronics device with keypad application
FI111494B (fi) 2001-06-29 2003-07-31 Nokia Corp Langaton käyttöliittymän laajennus
JP4013630B2 (ja) 2002-04-25 2007-11-28 アイシン・エィ・ダブリュ株式会社 事故多発位置報知装置、事故多発位置報知システム及び事故多発位置報知方法
US7046134B2 (en) 2002-06-27 2006-05-16 Axeda Corporation Screen sharing
US7231229B1 (en) 2003-03-16 2007-06-12 Palm, Inc. Communication device interface
JP2005049138A (ja) * 2003-07-30 2005-02-24 Pioneer Electronic Corp 交通状況報知装置、そのシステム、その方法、そのプログラム、および、そのプログラムを記録した記録媒体
JP4452474B2 (ja) * 2003-09-30 2010-04-21 パイオニア株式会社 案内誘導システム、その方法、そのプログラム、および、そのプログラムを記録した記録媒体
US7814419B2 (en) 2003-11-26 2010-10-12 Nokia Corporation Changing an orientation of a user interface via a course of motion
JP2005332319A (ja) 2004-05-21 2005-12-02 Nissan Motor Co Ltd 入力装置
KR100814430B1 (ko) 2004-06-09 2008-03-18 삼성전자주식회사 드라이버 프로그램을 기록한 기록매체
US7554522B2 (en) 2004-12-23 2009-06-30 Microsoft Corporation Personalization of user accessibility options
US7835505B2 (en) 2005-05-13 2010-11-16 Microsoft Corporation Phone-to-monitor connection device
US7933955B2 (en) 2006-07-11 2011-04-26 Igor Khalatian One-click universal screen sharing
US9318108B2 (en) 2010-01-18 2016-04-19 Apple Inc. Intelligent automated assistant
DE102008051756A1 (de) * 2007-11-12 2009-05-14 Volkswagen Ag Multimodale Benutzerschnittstelle eines Fahrerassistenzsystems zur Eingabe und Präsentation von Informationen
US8015005B2 (en) * 2008-02-15 2011-09-06 Motorola Mobility, Inc. Method and apparatus for voice searching for stored content using uniterm discovery
US20130275899A1 (en) * 2010-01-18 2013-10-17 Apple Inc. Application Gateway for Providing Different User Interfaces for Limited Distraction and Non-Limited Distraction Contexts
US20100138780A1 (en) 2008-05-20 2010-06-03 Adam Marano Methods and systems for using external display devices with a mobile computing device
JP2009300537A (ja) 2008-06-10 2009-12-24 Fujitsu Ten Ltd 音声作動システム、音声作動方法および車載装置
KR20100035924A (ko) 2008-09-29 2010-04-07 삼성전자주식회사 디스플레이장치 및 외부입력장치를 가지는 디스플레이 시스템과 그 제어 방법
KR100946460B1 (ko) 2008-09-30 2010-03-10 현대자동차주식회사 차량의 입력 장치
US20110165551A1 (en) * 2008-10-20 2011-07-07 Wataru Yamazaki Device and system for assisting in using equipment
JP2012507091A (ja) 2008-10-27 2012-03-22 ソーシャル・ゲーミング・ネットワーク インターラクティブなプロキシミティディスプレイのテザーのための装置、方法およびシステム
US8893040B2 (en) * 2008-12-23 2014-11-18 At&T Mobility Ii Llc Systems, devices, or methods for accessing information employing a tumbler-style graphical user interface
US8554831B2 (en) * 2009-06-02 2013-10-08 Ford Global Technologies, Llc System and method for executing hands-free operation of an electronic calendar application within a vehicle
US9858925B2 (en) * 2009-06-05 2018-01-02 Apple Inc. Using context information to facilitate processing of commands in a virtual assistant
US9310880B2 (en) 2009-09-29 2016-04-12 Ncr Corporation Self-service computer with dynamic interface
US10705794B2 (en) * 2010-01-18 2020-07-07 Apple Inc. Automatically adapting user interfaces for hands-free interaction
US9413869B2 (en) * 2010-02-10 2016-08-09 Qualcomm Incorporated Mobile device having plurality of input modes
US8570189B1 (en) * 2010-05-10 2013-10-29 Eric Casebolt Multifunction traffic control and information system
US8731814B2 (en) 2010-07-02 2014-05-20 Ford Global Technologies, Llc Multi-modal navigation system and method
US20120050183A1 (en) 2010-08-27 2012-03-01 Google Inc. Switching display modes based on connection state
WO2012046890A1 (fr) 2010-10-06 2012-04-12 엘지전자 주식회사 Terminal mobile, dispositif afficheur, et procédé de commande correspondant
CN102006373B (zh) * 2010-11-24 2015-01-28 深圳市车音网科技有限公司 基于语音命令控制的车载服务系统及方法
US8669970B2 (en) 2011-01-27 2014-03-11 Apple Inc. Master synchronization for multiple displays
JP5889542B2 (ja) 2011-04-07 2016-03-22 クラリオン株式会社 無線通信端末及び操作システム
US20120268294A1 (en) * 2011-04-20 2012-10-25 S1Nn Gmbh & Co. Kg Human machine interface unit for a communication device in a vehicle and i/o method using said human machine interface unit
US20120303263A1 (en) 2011-05-23 2012-11-29 Microsoft Corporation Optimization of navigation tools using spatial sorting
US9761083B2 (en) * 2011-09-16 2017-09-12 Elottery, Inc. Location, age and identity verification for mobile gaming
WO2013067526A1 (fr) 2011-11-04 2013-05-10 Remote TelePointer, LLC Procédé et système pour une interface utilisateur pour des dispositifs interactifs utilisant un dispositif mobile
US20130155237A1 (en) 2011-12-16 2013-06-20 Microsoft Corporation Interacting with a mobile device within a vehicle using gestures
KR101901720B1 (ko) 2012-04-02 2018-11-13 삼성전자주식회사 더미 장치와의 연동 방법 및 그 전자 장치
KR101952682B1 (ko) 2012-04-23 2019-02-27 엘지전자 주식회사 이동 단말기 및 그 제어방법
CN202565359U (zh) 2012-05-11 2012-11-28 广东欧珀移动通信有限公司 一种微投互动手机
US20140118222A1 (en) 2012-10-30 2014-05-01 Cloudcar, Inc. Projection of content to external display devices
US20140129695A1 (en) 2012-11-02 2014-05-08 Gface Gmbh Connected devices
US9218805B2 (en) * 2013-01-18 2015-12-22 Ford Global Technologies, Llc Method and apparatus for incoming audio processing
US9137476B2 (en) 2013-02-14 2015-09-15 Sony Corporation User-defined home screen for ultra high definition (UHD) TV
US8744645B1 (en) * 2013-02-26 2014-06-03 Honda Motor Co., Ltd. System and method for incorporating gesture and voice recognition into a single system
US20140267035A1 (en) 2013-03-15 2014-09-18 Sirius Xm Connected Vehicle Services Inc. Multimodal User Interface Design
KR20140094407A (ko) 2013-04-10 2014-07-30 (주)브라이니클 이동 단말기를 이용한 쇼핑정보 제공방법 및 이동 단말기를 이용하여 쇼핑정보를 제공하는 사용자 인터페이스
CN103347162B (zh) * 2013-06-28 2017-07-18 深圳市掌讯通讯设备有限公司 一种车载装置与智能手机互动控制系统及其方法
WO2015064965A1 (fr) * 2013-10-29 2015-05-07 엘지전자 주식회사 Système de communication inter-dispositifs, appareil et son procédé de commande
EP2960098B1 (fr) * 2014-06-27 2020-11-04 Volvo Car Corporation Procédés, dispositif et système pour aider un occupant de véhicule utilisant la fonctionnalité d'un dispositif nomade par l'intermédiaire d'un système embarqué
US20160028870A1 (en) * 2014-07-23 2016-01-28 Lg Electronics Inc. Method of sharing information of a mobile terminal for interworking between an in-vehicle infotainment system and the mobile terminal
US20160044519A1 (en) * 2014-08-08 2016-02-11 GM Global Technology Operations LLC Method and apparatus for supporting mobile device screen replication in automotive environment using flexible network connectivity

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120166076A1 (en) * 2010-12-23 2012-06-28 Rody Hardy Predictive Traffic Warning And Suggestive Rerouting System And Method
EP2793116A2 (fr) * 2013-03-26 2014-10-22 Samsung Electronics Co., Ltd. Appareil de terminal pouvant être monté dans un véhicule, dispositif mobile pour travailler avec l'appareil de terminal et procédés de fourniture de service de celui-ci

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2016081326A1 *

Also Published As

Publication number Publication date
CN107077317A (zh) 2017-08-18
JP7093181B2 (ja) 2022-06-29
MX2017006086A (es) 2017-07-27
WO2016081326A1 (fr) 2016-05-26
RU2017117421A3 (fr) 2019-06-05
RU2707410C2 (ru) 2019-11-26
KR20170088384A (ko) 2017-08-01
JP2018508843A (ja) 2018-03-29
AU2015350267B2 (en) 2020-06-25
AU2015350267A1 (en) 2017-05-11
KR102416405B1 (ko) 2022-07-01
CA2965703A1 (fr) 2016-05-26
BR112017008421A2 (pt) 2017-12-26
US10116748B2 (en) 2018-10-30
RU2017117421A (ru) 2018-11-21
EP3221783B1 (fr) 2021-09-01
CA2965703C (fr) 2022-08-23
US20160150020A1 (en) 2016-05-26

Similar Documents

Publication Publication Date Title
CA2965703C (fr) Interface multimodale embarquee
US11745585B2 (en) Vehicle infotainment apparatus using widget and operation method thereof
AU2019213441B2 (en) Device, method, and graphical user interface for synchronizing two or more displays
US11784951B1 (en) Determining contextually relevant application templates associated with electronic message content
CN106062514B (zh) 便携式装置与车辆头端单元之间的交互
US10402460B1 (en) Contextual card generation and delivery
TWI572849B (zh) 用於實施執行於行動裝置上之應用程式的方法及儲存該方法之機器可讀媒體
EP3165994A1 (fr) Dispositif de traitement d'informations
EP2980744A1 (fr) Liens profonds de miroitage
US20150339031A1 (en) Context-based vehicle user interface reconfiguration
CN109631920B (zh) 具有改进的导航工具的地图应用
WO2013173148A2 (fr) Interaction et gestion de dispositifs utilisant la détection du regard
CN110932888A (zh) 用于协商对共享音频或视觉资源的控制的系统和方法
US20200309547A1 (en) Aligning content playback with vehicle travel
CN109029480B (zh) 具有改进的导航工具的地图应用
US20210191610A1 (en) Head-Up Display Controller
JP2009175852A (ja) 情報提供装置及び情報提供方法

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170329

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190904

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20210326

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1426920

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210915

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015072925

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

RAP4 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211201

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211201

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1426920

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211202

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220101

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220103

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015072925

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211116

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211130

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20211130

26N No opposition filed

Effective date: 20220602

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211130

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211116

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20151116

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230512

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231019

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231019

Year of fee payment: 9

Ref country code: DE

Payment date: 20231019

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210901