WO2013179636A1 - Notification de la compatibilité d'un dispositif d'entrée tactile - Google Patents

Notification de la compatibilité d'un dispositif d'entrée tactile Download PDF

Info

Publication number
WO2013179636A1
WO2013179636A1 PCT/JP2013/003328 JP2013003328W WO2013179636A1 WO 2013179636 A1 WO2013179636 A1 WO 2013179636A1 JP 2013003328 W JP2013003328 W JP 2013003328W WO 2013179636 A1 WO2013179636 A1 WO 2013179636A1
Authority
WO
WIPO (PCT)
Prior art keywords
touch
sensitive input
vehicle
mobile device
vehicle device
Prior art date
Application number
PCT/JP2013/003328
Other languages
English (en)
Inventor
Kurt DUSTERHOFF
David Blanc
Original Assignee
Denso Corporation
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 Denso Corporation filed Critical Denso Corporation
Publication of WO2013179636A1 publication Critical patent/WO2013179636A1/fr

Links

Images

Classifications

    • 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
    • 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/038—Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry
    • 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
    • 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/72415—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 for remote control of appliances
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
    • G01C21/34—Route searching; Route guidance
    • G01C21/36—Input/output arrangements for on-board computers
    • G01C21/3664—Details of the user input interface, e.g. buttons, knobs or sliders, including those provided on a touch screen; remote controllers; input using gestures
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
    • G01C21/34—Route searching; Route guidance
    • G01C21/36—Input/output arrangements for on-board computers
    • G01C21/3688—Systems comprising multiple parts or multiple output devices (not client-server), e.g. detachable faceplates, key fobs or multiple output screens
    • 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/0383—Remote input, i.e. interface arrangements in which the signals generated by a pointing device are transmitted to a PC at a remote location, e.g. to a PC in a LAN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/22—Details of telephonic subscriber devices including a touch pad, a touch sensor or a touch detector

Definitions

  • the present disclosure relates to touch-sensitive input device compatibility notification and in particular but not exclusively to a method, device, and system for touch-sensitive input device compatibility notification.
  • a mobile device can be connected to a vehicle to use these services in the vehicle.
  • JP 2003-244343 A discusses an arrangement where the image on the screen of a portable terminal is displayed on a screen of an in-vehicle device when the portable terminal is in the vehicle and connected to the in-vehicle device.
  • the portable terminal can be remotely operated from the in-vehicle display. This arrangement is designed for keypad-controlled terminals.
  • the input means of the in-vehicle device may not be compatible with all available input means of mobile devices.
  • the user experience can thus be degraded depending on the type of mobile device used.
  • an in vehicle device can identify a touch interface capability of a connected mobile device and can take account of this compatibility when facilitating user interaction with the mobile device via the in vehicle device.
  • This can take the form, for example, of notifying a user of incompatibilities, of restricting user interactions, or of providing an interpretative interface to translate inputs to the in vehicle device into a form compatible with the mobile device.
  • mobile devices for example mobile devices having a touch-sensitive input device, can be satisfactorily connected to and controlled by an in-vehicle device.
  • a method comprising connecting a mobile device having a touch-sensitive input device to an in-vehicle device having a touch-sensitive input device, wherein, when the mobile device and the in-vehicle device are connected, the mobile device is remotely operable from the in-vehicle device using at least user inputs from the touch-sensitive input device of the in-vehicle device; receiving at the in-vehicle device specification information for the mobile device from the mobile device; obtaining one or more touch-sensitive input device capabilities for the in-vehicle device; obtaining one or more touch-sensitive input device capabilities for the mobile device based on the specification information; determining whether incompatibility exists between the one or more touch-sensitive input device capabilities for the in-vehicle device and the one or more touch-sensitive input device capabilities for the mobile device for remotely operating the mobile device from the in-vehicle device; and if an incompatibility has been identified, presenting, using the in-vehicle device, a
  • Such a method facilitates the use of touch-sensitive input device mobile devices with in-vehicle devices as the user may be able to determine whether a feature is not working because of an error at the mobile device and/or at the in-vehicle device, or because of an incompatibility between the touch-sensitive input devices of the mobile and in-vehicle devices. For example, if the in-vehicle-device screen is only capable of detecting one input at a point in time but the mobile-device screen is capable of detecting at least two inputs at a point in time (e.g. includes multi-touch screen), the incompatibility can be identified and the user can be notified that the in-vehicle device can not control the mobile device using a multi-touch interface. Owing to such a method, a usable and functional remote control connection for a touch-sensitive input device mobile device from an in-vehicle device can provided.
  • Presenting a notification may include at least one of displaying a message on a display of the in-vehicle device; displaying an icon on a display of the in-vehicle device and playing a sound. It may for example be considered as appropriate to display a visual notification on a touchscreen that will be used to control the mobile device remotely, and/or to play a message so that a driver can be safely notified while driving.
  • the specification information may include at least one of a model number, a serial number, a manufacturer, screen identification information, a touch-sensitive input device technology, and a touch-sensitive input device capability for the mobile device. This can help with efficiently obtaining of the one or more touch-sensitive input device capabilities of the mobile device.
  • the one or more touch-sensitive input device capabilities may include at least one of single-touch; multi-touch; and one or more recognised touch operations. For example, in some situations, it may be appropriate not only to determine whether the touch-sensitive input device can detect single and/or multi-touch inputs, but also which operations it can detect for an improved incompatibility check.
  • Part of the touch-sensitive input device of the mobile device and/or part of the touch-sensitive input device of the in-vehicle device may comprise at least one of a touchscreen and a touch panel.
  • the touch-sensitive input device may or may not be operable to display content.
  • Obtaining one or more touch-sensitive input device capabilities for the mobile device may include retrieving at least part of the one or more touch-sensitive input device capabilities for the mobile device from a capabilities table using the specification information for the mobile device.
  • a table may be maintained in a storage, located for example in the car or in a remote location, and the in-vehicle device can use the table to retrieve a mobile-device one or more touch-sensitive input device capabilities based on a phone model included in the specification information.
  • the determining step may include detecting whether a first touch-sensitive input device capability is available for the mobile device and is not available for the in-vehicle device; and, if a first capability has been detected, determining whether a first input means is available at the in-vehicle device to compensate fully or partially for the lack of the first capability for the in-vehicle device and, if a first input means is available, presenting a notification includes presenting a notification regarding the first input means being available to compensate fully or partially, respectively, for the lack of the first capability in the in-vehicle device. This can be used to inform the user on alternative input means that can be used if an incompatibility has been identified.
  • a zoom in/out button can be used to compensate for the lack of a pinch in/out operation on the in-vehicle-device touch-sensitive input device and the user can be informed of the alternative input means, thereby facilitating a full interaction with the remote device via the in vehicle device.
  • an in-vehicle device comprising a communication element operable to send and receive messages; a touch-sensitive input device; a connection element operable to control a connection with a mobile device, wherein the connection element is operable to control remotely a mobile device using at least user inputs from the touch-sensitive input device; and a compatibility element operable to receive from a mobile device having a touch-sensitive input device specification information for the mobile device; to obtain one or more touch-sensitive input device capabilities for the in-vehicle device; to obtain one or more touch-sensitive input device capabilities for the mobile device based on the specification information; to determine whether incompatibility exists between the one or more touch-sensitive input device capabilities for the in-vehicle device and the one or more touch-sensitive input device capabilities for the mobile device for remotely operating the mobile device from the in-vehicle device; and to present, if an incompatibility has been identified, a notification regarding the identified incompatibility using the in-vehicle device.
  • a system comprising an in-vehicle device having a touch-sensitive input device; and a mobile device having a touch-sensitive input device, the mobile device being connectable to the in-vehicle device and being remotely operable, when the mobile device and the in-vehicle device are connected, from the in-vehicle device using at least user inputs from the touch-sensitive input device of the in-vehicle device.
  • the mobile device is operable to send specification information to in-vehicle device; the in-vehicle device is operable to obtain one or more touch-sensitive input device capabilities for the in-vehicle device and to obtain, upon reception of the specification information, one or more touch-sensitive input device capabilities for the mobile device based on the specification information; and the in-vehicle device is operable to determine whether incompatibility exists between the one or more touch-sensitive input device capabilities for the in-vehicle device and the one or more touch-sensitive input device capabilities for the mobile device for remotely operating the mobile device from the in-vehicle device; and to present, if an incompatibility has been identified, a notification regarding any identified incompatibility.
  • FIG. 1 is a schematic illustration of a mobile device and an in-vehicle device
  • Fig. 2 is an illustration of a mobile device connected to an in-vehicle device via a remote control connection.
  • Fig. 3 is a flowchart illustrating a method for presenting an incompatibility notification;
  • Fig. 4 is a flowchart illustrating a further method for presenting an incompatibility notification;
  • Fig. 5A is illustration of possible single or multi-touch operations.
  • Fig. 5B is illustration of possible single or multi-touch operations.
  • Fig. 5C is illustration of possible single or multi-touch operations.
  • Fig. 5D is illustration of possible single or multi-touch operations.
  • mobile device may refer to any mobile and/or portable device, for example a mobile phone (including a smartphone), a satellite navigation (i.e., sat-nav) device, a tablet, a netbook, an audio player, a video player or a portable computer.
  • a mobile phone including a smartphone
  • satellite navigation i.e., sat-nav
  • tablet including a smartphone
  • netbook i.e., a netbook
  • audio player i.e., sat-nav
  • video player i.e., a video player or a portable computer.
  • ⁇ vehicle> may refer to any transport, for example any form of car, lorry or motorcycle.
  • Fig. 1 is a schematic illustration of a mobile device 10 and an in-vehicle device 20 which may be used in accordance with the present disclosure.
  • the mobile device 10 is connectable to an in-vehicle device 20, and may include the following elements: a communication unit 14, a control unit 16 for controlling processes running on the mobile device 10, and a memory unit 18.
  • the in-vehicle device 20 may include a touch-sensitive input device 22 (also referred to as a display unit or an in-vehicle display 22) for displaying content to a user, a communication unit 24 for communicating with at least the mobile device 10, a control unit 26 for controlling processes running on the in-vehicle device 20 and a memory unit 28.
  • the control unit 26 may function as a connection element or a compatibility element.
  • the mobile device 10 and the in-vehicle device 20 may be connected via their respective communication units so that the mobile can be remotely controlled from the in-vehicle device 20 and so that display information is received at the in-vehicle device 20 to be displayed on the display unit 22 of the in-vehicle device 20.
  • Such a connection may be referred to as a remote control connection.
  • the physical connections between the mobile device 10 and the in-vehicle device 20 may be a wired connection such as a USB or FireWire connection or, alternatively, may be a wireless connection such as Bluetooth, Wi-Fi or IR.
  • Fig. 2 is an illustration of a mobile device 10 connected to an in-vehicle device 20 via a remote control connection.
  • the display unit 22 of the in-vehicle device 20 in this example shows the same image as a display unit 12 (also referred to as a mobile-device display 12) of the mobile device 10.
  • the mobile device 10 can be remotely controlled from the in-vehicle device 20, for example with the use of the display unit 22 that serves as a touch-sensitive input device 22 and/or the use of a one or more buttons 25.
  • Each of the display unit 22 and the button 25 may be thus referred to as input device or portion. Any other suitable input means, for example voice command input means, may be used. It is noteworthy that, in the illustration of Fig.
  • the screen of the mobile device 10 is turned on at least for the ease of illustrating an example comparison between the displays of the mobile device 10 and of the in-vehicle device 20.
  • the screen of the mobile device 10 may sometimes or always be turned off and/or locked, for example to save battery and/or for security reasons, either because it is connected to the in-vehicle device 20 or because the mobile device 10 has not been used for a predetermined time.
  • buttons 25a and 25b and directional pad 25c buttons 25a and 25b and directional pad 25c, to enter menus that are native menus of the mobile device 10 and to use the mobile device 10 as if the user was using the mobile-device native input means and display.
  • the mobile device 10 can send display information to the in-vehicle device 20 and the in-vehicle device 20 can display at least part of the display information on its in-vehicle display 22 (or on a part of it), wherein display information includes information as to what can be displayed on the remote display, in this case the in-vehicle display.
  • display information sent by the mobile device 10 will corresponds exactly to what is or would have been displayed on the mobile-device display 12.
  • the display information can have the same pixel and colour resolution as the mobile-device display.
  • the display information may correspond to a display which differs from the mobile-device display.
  • the display information may for example have a lower pixel and/or colour resolution so that less information has to be transmitted. In some cases, the display information may have a higher pixel and/or colour resolution, for example if the in-vehicle display 22 has a higher pixel and/or colour resolution than the mobile-device display 12. In the event that the in-vehicle display 22 has a different pixel and/or colour resolution than that of the display information received from the mobile device 10, adjustments may be made when displaying the display information on the in-vehicle display 22.
  • the connection between the mobile device 10 and in-vehicle device 20 may be used for example to use a sat-nav function of the mobile-device from the in-vehicle device 20, or any other function of the mobile device 10.
  • the user may use a web browser, games, mobile apps, etc. of the mobile device 10 from the in-vehicle device 20.
  • the remote control connection between the mobile device 10 and the in-vehicle device 20 can be considered as a VNC or VNC-like connection.
  • suitable systems can also include an X-Windows (or X11) type approach or a MirrorLink TM approach.
  • Fig. 3 is a flowchart illustrating a method for presenting an incompatibility notification.
  • the example method of Fig. 3 is illustrated showing steps performed at the mobile device 10 (i.e., the control unit 16) and steps performed at the in-vehicle device 20 (i.e., the control unit 26). In other examples, only steps performed at the mobile device 10 or at the in-vehicle device 20 may be considered and/or additional or fewer steps may be considered.
  • the mobile device 10 and in-vehicle device 20 are connected, for example according to a connection as discussed above, the mobile device 10 sends specification information to the in-vehicle device 20 at step S310.
  • the specification information may include at least one of: a model number, a serial number, a manufacturer, and screen identification information.
  • the specification information may also include touch-sensitive input device capability information.
  • the model number, serial number and manufacturer may be in respect of the mobile device 10 or in respect of any element involved for the touch-sensitive input device, such as a graphic card, a GPU, and/or the touch-sensitive input device itself.
  • the specification information is received by the in-vehicle device 20 at S320.
  • the in-vehicle device 20 then obtains at S321 one or more touch-sensitive input device capabilities for the mobile device 10, based on the specification information, and one or more touch-sensitive input device capabilities for the in-vehicle device 20.
  • this step may be carried out as two separate steps, for example obtaining one or more capabilities for a first of the two devices, and then obtaining one or more capabilities for the second of the two devices.
  • Different methods may be used to obtain one or more touch-sensitive input device capabilities for the mobile device 10 based on the specification information. For example, if the specification information includes a serial number, the in-vehicle device 20 may retrieve the one or more touch-sensitive input device capabilities from an element, for example a table, a database or any other organised form of data store.
  • the element may be part of the in-vehicle device 20, e.g. a table stored in the memory 28.
  • the element may be a remote element, for example, the in-vehicle device 20 may include wireless (e.g. GPRS, 3G, 4G, WiMAX, etc.) communication means and may query the remote element for one or more touch-sensitive input device capabilities for the mobile device 10.
  • the one or more touch-sensitive input device capabilities may be based more directly on the specification information, for example the specification information may include at least a part of the one or more touch-sensitive input device capabilities.
  • the specification information may include at least one of resistive screen; capacitive screen; and any other touch-sensitive technology.
  • resistive screens are generally single-touch screens (although resistive technology may be used to provide multi-touch screens). It may therefore be appropriate, for example if no other information is available, to consider that a touch-sensitive input device having a resistive screen is a single-touch surface. It may also be appropriate, for example if there is no indication to the contrary, to consider that a capacitive screen is a multi-touch screen.
  • the one or more touch-sensitive input device capabilities may include at least one of single touch, multi-touch, and the detection of a touch-operation. Additionally, the touch-sensitive input device capabilities may include recognised touch operations, which can for example be recognised by the touch-sensitive input device and/or by a system processing the touch-sensitive input device inputs.
  • the touch-sensitive input device may have a multi-touch detection capability but may only be able to detect one point operations (for example as illustrated on Fig. 5A) and a two-point parallel sliding operation (for example as illustrated in Fig. 5B) and may not be able to detect and/or process other multi-touch inputs.
  • the touch-sensitive input device may thus for example not be operable to detect, or may not be used with a system operable to detect, a pinch-in or pinch-out operation (as illustrated in Fig. 5C-5D).
  • a touch-sensitive input device which may be according to this arrangement may include a touch panel on a computer (e.g.
  • the touch-sensitive input device may be operable to detect, and/or used with a system operable to detect, possibly any multi-touch operations or most well-known multi-point operations, for example parallel sliding and pinch-in/out.
  • the one or more touch-sensitive input device capabilities may include any appropriate touch-sensitive input device capability.
  • the in-vehicle device 20 identifies any incompatibility between the one or more touch-sensitive input device capabilities obtained for the mobile device 10 and for the in-vehicle device 20. For example it may be detected that the mobile device 10 has a multi-touch capability (or if it is an assumed capability if for example the surface is a capacitive screen, per the discussion above), and that the in-vehicle does not have a multi-touch capability, this may be identified as an incompatibility. For example, the user may then not be able to control the mobile device 10 from the in-vehicle device 20 in the same manner as when controlling the mobile device 10 directly without a remote control connection.
  • the in-vehicle device 20 has a multi-touch screen and the mobile device 10 has a single-touch screen, this may not be identified as an incompatibility.
  • the user may be able to control the mobile device 10 via the remote control connection in the same manner as when controlling the mobile device 10 directly, it may be appropriate to consider that this does not affect remote operation of the mobile device 10 and that this is thus not an incompatibility.
  • this may be considered as an incompatibility because the touch-sensitive input device capabilities differ between the mobile device 10 and the in-vehicle device 20 and this may therefore affect the remote operation of the mobile device 10 from the in-vehicle device 20 for example by causing the mobile device 10 not to be able to process user inputs received from the in-vehicle device 20 and which are multi-touch user inputs.
  • an incompatibility may be identified if the mobile device 10 can detect pinch-in/out operations while the in-vehicle device 20 can not detect these operations (e.g. if it can detect one or more multi-touch operations but not a pinch-in or pinch-out operation).
  • step S324 an incompatibility notification is presented using the vehicle device.
  • the in-vehicle device 20 may cause a sound system to play a sound, such as a voice message, a bleeping sound or any other suitable sound.
  • a voice message may be played which notifies the user of an incompatibility, and optionally, of the type of incompatibility, for example that multi-touch is not available from the in-vehicle device 20.
  • the presenting a notification may comprise displaying a visual notification on an in-vehicle display.
  • This in-vehicle display may be at least a part of the in-vehicle touch-sensitive input device 22 or at least a part of a different display.
  • the notification may be displayed on different element.
  • the touch-sensitive input device 22 may be operable to display content and the notification may be displayed on this and/or a different display.
  • Possible in-vehicle displays include a central dashboard screen (e.g. used for the vehicle configuration and/or sat-nav), a head-up display, an icon or symbol on the dashboard (e.g. behind the wheel or in a more central position in the vehicle).
  • the notification may include one or more different types of notification, for example, it may include displaying an icon on a display and playing a sound.
  • step S323 In the event that, at step S323, no incompatibility has been identified, the method skips step S324 and carries on (for example ends or carries on with additional steps).
  • Fig. 4 is a flowchart illustrating a further method for presenting an incompatibility notification.
  • the method is represented from the point of view of the in-vehicle device 20, but in other examples it may be represented including more and/or different elements and may include more or fewer steps.
  • the in-vehicle device 20 receives specification information from the mobile device 10.
  • the in-vehicle device 20 obtains one or more touch-sensitive input device capabilities for the mobile device 10, based on the specification information, and one or more touch-sensitive input device capabilities for the in-vehicle device 20.
  • the in-vehicle device 20 identifies any incompatibility between the obtained touch-sensitive input device capabilities at S422.
  • step S423 it is determined whether any input means are available to compensate fully or partially for the identified incompatibility.
  • the mobile-device display 12 that includes a touch-sensitive input device or a touch-sensitive surface serves as an input device or portion is a multi-touch touchscreen and the in-vehicle display 22 is a single-touch touchscreen
  • the in-vehicle display can not be used for pinch-in (see Fig. 5C) or pinch-out (see Fig. 5D) operations, for example to zoom out or in on a map.
  • buttons 25a and 25b which can be used on the in-vehicle device 20 to zoom in or out on a map displayed on the in-vehicle display 22
  • the user may be able to use zooming buttons 25a and 25b to compensate at least partially for the lack of detection of pinch-in/pinch-out operations on the in-vehicle display 22.
  • a message could be displayed on an in-vehicle display to notify the user that alternative input means are available, and optionally, the notification may indicate what the incompatibility is, what the alternatives input means is and/or how the alternative input means may be used to compensate for the incompatibility.
  • step S424 a notification is presented regarding the incompatibility.
  • the notification may clarify that no alternative input means has been identified to compensate (fully or partially) for the incompatibility.
  • the notification discussion in respect of S324 applies equally to the notifications of S425 and/or S426.
  • Fig. 5A-5D are illustrations of possible single or multi-touch operations on a touch-sensitive input device 32.
  • Fig. 5A is an example of a user input that can be entered on a single-touch or multi-touch touch-sensitive input device.
  • the starting point 50A indicates where the input started and the arrow 50 indicates the path followed by the user (e.g. using his finger or a stylus) while keeping in contact with the touch-sensitive input device 32.
  • only a point can be input (e.g. only point 50A) for example to simulate a click or double-click (e.g. two subsequent points in the same area), or different paths may be followed, such as a loop, a line, etc.
  • Fig. 5B illustrates two possible multi-touch operations, with two parallel sliding paths on a touch-sensitive input device 32.
  • Paths 52 and 53 starting from 52A and 53A respectively, can be followed substantially simultaneously by the user for example to encode a scroll down on a display.
  • paths 54 and 55 starting from 54A and 55A respectively, can be followed substantially simultaneously by the user for example to encode a scroll left.
  • Fig. 5C illustrates another possible multi-touch operation, sometimes referred to as pinch in.
  • the two paths 56 and 57 are substantially along the same direction and move towards each other.
  • This can be used to encode a zoom out operation.
  • the centre C1 may be estimated based on point 56A, point 57A, the path directions, and/or the speed along the paths, and the zoom out operation may be centred on point C1.
  • Fig. 5D illustrates a possible multi-touch operation, sometimes referred to as pinch out.
  • the two paths 58 and 59 are substantially along the same direction and move away from each other. This can be used to encode a zoom in operation.
  • the centre C2 may be estimated based on point 58A, point 59A, the path directions, and/or the speed along the paths, and the zoom in operation may be centred on point C2.
  • the representation of the mobile device 10 and of the in-vehicle device 20 in Fig. 1 is not intended to be limiting, for example on the physical and/or logical structure of the mobile device 10 and in-vehicle device 20.
  • this representation can be viewed from a logical point of view, wherein the elements represented may illustrate the function of the devices, which may for example all be performed by the same hardware and/or software (if any). In other examples they may also be viewed as physical elements and they may be physically separate elements.
  • touch inputs are not limited to a single- or dual-touch inputs and any number of simultaneous input may be considered under the present disclosure, for example one, two, three or more.
  • the single or multi touch operations are not limited to the operations illustrated in Fig. 5A-5C and any other suitable touch input may be used.
  • a touch-sensitive input device may be any appropriate touch-sensitive input device, such as a touchscreen (e.g. both a touch-sensitive input device and a display), a touch panel (e.g. which does not include a display) or any touch-sensitive surface.
  • the touch-sensitive display may use any appropriate touch technology. Examples of such technologies include capacitive (e.g. surface capacitance or projected capacitance), resistive, surface acoustic wave, or acoustic pulse recognition technologies.
  • the touch-sensitive input device may be operable to detect single touch and/or multi touch operations; may be operable to do so with the use of a neutral stylus, a conductive stylus, and/or any other suitable neutral or non-neutral input means (e.g.
  • the touch-sensitive display may also include a controller, for example for processing electrical changes on the surface and/or for outputting touch coordinates, e.g. to the control unit of the in-vehicle device 20 or of the mobile device 10 in the example of Fig. 1. In other examples, the function provided by such a controller may be provided by the control unit.
  • most or all of the method steps may be carried out by the control units of the in-vehicle device 20 and of the mobile device 10, as appropriate. However, in other examples, for at least one of the mobile and in-vehicle devices, some or all of the steps may be carried out by a physically and/or logically different element of the devices.
  • Presenting a notification includes presenting a notification in any appropriate manner. For example it may include playing sound, e.g. a bleeping sound; playing a voice message, e.g. to inform a user of an incompatibility between the obtained touchscreen capabilities; displaying a message, for example on an in-vehicle-device screen, on a head-up display or any other suitable display; and presenting any other visual signal, for example lighting a symbol on the dashboard, displaying an icon an in-vehicle display (e.g. a head-up display), turning on and/or off one or more lights of any colour, flashing one or more lights of any colour and at any frequency, etc.
  • playing sound e.g. a bleeping sound
  • playing a voice message e.g. to inform a user of an incompatibility between the obtained touchscreen capabilities
  • displaying a message for example on an in-vehicle-device screen, on a head-up display or any other suitable display
  • the selection of the type of notification presented may depend on one or more parameters, for example fixed (e.g. pre-configured), configurable (e.g. by the user and/or another party), and/or dynamic parameters. For example, it may decided that, if the vehicle speed is higher than a threshold, then a message notification will be presented on a head-up display only, but if the vehicle speed is less than the threshold, then a message notification will be presented on an in-vehicle display and on a head-up display, so that the message notification can be appropriately presented depending on the situation. In some example, a notification may or may not be presented depending on a parameter, e.g.
  • one or more notifications may be delayed until a certain condition is met, for example a condition in respect of the vehicle and/or the vehicle environment.
  • an icon notification may be presented as soon as the incompatibility has been detected, but an audio message (e.g. voice message or other sound) may be delayed until the vehicle speed has decrease below a certain limit (e.g. the vehicle has stopped) or until the vehicle has exited a particular zone (e.g. a high-speed or -risk zone).
  • the driver is not disturbed by the audio message while driving for example at high speed. And when the vehicle speed has been decreased to a lower value, the audio message may be played to the user.
  • incompatibility requirements may be configurable.
  • a party may be provided with the option to overwrite one or more of the parameters and/or incompatibility requirements.
  • the user may overwrite the incompatibility requirements for this mobile device 10 so that this type of incompatibility is no longer notified. In some examples, this may be done temporarily (e.g. for the duration of the connection) or permanently (e.g.
  • the overwriting information may be sent to a remote element. This may be appropriate for example to keep track of any user preference regarding incompatibilities to be notified.
  • overwriting instructions may be sent from a remote element to the in-vehicle device 20. For example if it has been detected that the assumed user preferences in respect of notifications could be improved, overwriting instructions may be sent to the in-vehicle device 20 to update the in-vehicle device 20 remotely and re-configure the notification parameters.
  • the in-vehicle device 20 obtained one or more capabilities for a mobile device which appear to be incorrect (e.g. ⁇ single-touch> when it should be ⁇ multi-touch>)
  • the specification information sent to the in-vehicle device 20 may be sent automatically (for example as part of a discovery message exchange once the in-vehicle and mobile devices are connected) or on request.
  • the in-vehicle device 20 may be operable to detect that a mobile device 10 is connected via a remote-control connection and send a specification information request to the mobile device 10.
  • the mobile device 10 may not have a touch-sensitive input device.
  • the in-vehicle device may then first determine whether the mobile device 10 comprises a touch-sensitive input device. This may be based on the specification information received.
  • the specification information may specify that the mobile device does not include any touch-sensitive input device or it may be derivable from the brand and model of the mobile device 10 that the mobile device 10 does not comprise any touch-sensitive input device.
  • it may be first determined by other means (e.g. sending a request to the mobile device 10). Then, in the event that the mobile device 10 comprises a touch-sensitive input device, the in-vehicle device 20 may receive, automatically or on request, the specification information (e.g. a single/multi touch capability indication).

Abstract

Lorsqu'un dispositif mobile (10) comportant un dispositif d'entrée tactile (12) est connecté à un dispositif embarqué (20) comportant un dispositif d'entrée tactile (22), le dispositif mobile peut être commandé à distance au moyen d'entrées utilisateur effectuées à partir du dispositif d'entrée tactile du dispositif embarqué. Le dispositif embarqué reçoit des informations de spécification pour le dispositif mobile provenant du dispositif mobile (S320, S420), et obtient ainsi une ou plusieurs fonctionnalités du dispositif d'entrée tactile pour le dispositif mobile tout en obtenant une ou plusieurs fonctionnalités du dispositif d'entrée tactile pour le dispositif embarqué (S321, S421). Il est déterminé s'il existe une incompatibilité entre les fonctionnalités du dispositif d'entrée tactile pour le dispositif embarqué et les fonctionnalités du dispositif d'entrée tactile pour le dispositif mobile pour commander à distance le dispositif mobile à partir du dispositif embarqué (S323, S423) Si une incompatibilité a été identifiée, le dispositif embarqué présente une notification concernant l'incompatibilité identifiée (S324, S426).
PCT/JP2013/003328 2012-05-31 2013-05-27 Notification de la compatibilité d'un dispositif d'entrée tactile WO2013179636A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB1209730.9A GB2502595A (en) 2012-05-31 2012-05-31 Touch sensitive input device compatibility notification when a mobile device is connected to an In-Vehicle device
GB1209730.9 2012-05-31

Publications (1)

Publication Number Publication Date
WO2013179636A1 true WO2013179636A1 (fr) 2013-12-05

Family

ID=46582160

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/003328 WO2013179636A1 (fr) 2012-05-31 2013-05-27 Notification de la compatibilité d'un dispositif d'entrée tactile

Country Status (2)

Country Link
GB (1) GB2502595A (fr)
WO (1) WO2013179636A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10366602B2 (en) 2013-05-20 2019-07-30 Abalta Technologies, Inc. Interactive multi-touch remote control

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6371683B2 (ja) * 2014-11-14 2018-08-08 株式会社デンソーテン 電子装置、通信システム、携帯通信端末、通信方法、及びプログラム
DE102015208363A1 (de) * 2015-05-06 2016-11-24 Volkswagen Aktiengesellschaft Fortbewegungsmittel, Arbeitsmaschine, Anwenderschnittstelle und Verfahren zur Anzeige eines Inhaltes einer ersten Anzeigeeinrichtung auf einer zweiten Anzeigeeinrichtung

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009073806A2 (fr) * 2007-12-05 2009-06-11 Johnson Controls Technology Company Systèmes et procédés d'interface utilisateur de véhicule
WO2012036279A1 (fr) * 2010-09-17 2012-03-22 クラリオン株式会社 Système d'informations embarqué, dispositif embarqué et terminal d'informations

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1665845B1 (fr) * 2003-09-08 2010-06-09 Nokia Corporation Systeme de raccordement de telephone portable pour vehicules automobiles integrant une mise a jour dynamique de l'interface utilisateur externe
US7783699B2 (en) * 2006-06-19 2010-08-24 Ford Motor Company User interface system for a vehicle
US8260369B2 (en) * 2009-10-09 2012-09-04 Honda Motor Co., Ltd. Vehicle hands-free communication apparatus and vehicle hands-free communication method
TWM389063U (en) * 2010-03-16 2010-09-21 Wonde Proud Technology Co Ltd Vehicle mobile device control system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009073806A2 (fr) * 2007-12-05 2009-06-11 Johnson Controls Technology Company Systèmes et procédés d'interface utilisateur de véhicule
WO2012036279A1 (fr) * 2010-09-17 2012-03-22 クラリオン株式会社 Système d'informations embarqué, dispositif embarqué et terminal d'informations
EP2617604A1 (fr) * 2010-09-17 2013-07-24 Clarion Co., Ltd. Système d'informations embarqué, dispositif embarqué et terminal d'informations

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10366602B2 (en) 2013-05-20 2019-07-30 Abalta Technologies, Inc. Interactive multi-touch remote control

Also Published As

Publication number Publication date
GB201209730D0 (en) 2012-07-18
GB2502595A (en) 2013-12-04

Similar Documents

Publication Publication Date Title
JP6525888B2 (ja) コンテキストに基づいた車両ユーザインターフェースの再構成
EP3092559B1 (fr) Présentation de contenu audiovisuel et interaction avec celui-ci dans un véhicule
US10366602B2 (en) Interactive multi-touch remote control
US9008856B2 (en) Configurable vehicle console
US9176651B2 (en) Pushing a user interface to a remote device
JP5555555B2 (ja) 携帯機器と連携し、該携帯機器に対して可能な入力操作を実現する車載機器
US20160342406A1 (en) Presenting and interacting with audio-visual content in a vehicle
US9041674B2 (en) Method for operating a control system for a vehicle and control system for a vehicle
US10628008B2 (en) Information terminal controlling an operation of an application according to a user's operation received via a touch panel mounted on a display device
JP5754410B2 (ja) 表示装置
US20140281964A1 (en) Method and system for presenting guidance of gesture input on a touch pad
JP2016097928A (ja) 車両用表示制御装置
WO2013179636A1 (fr) Notification de la compatibilité d'un dispositif d'entrée tactile
US20160253088A1 (en) Display control apparatus and display control method
JP4765893B2 (ja) タッチパネル搭載装置、外部装置、及び外部装置の操作方法
JP5602830B2 (ja) 情報表示システムおよび情報表示装置
US11230189B2 (en) System and method for application interaction on an elongated display screen
KR101847495B1 (ko) 인포테인먼트 디바이스 및 그 제어 방법
JP2014187415A (ja) 携帯端末装置、プログラム、車載装置
JP2016035640A (ja) 入力装置及び電子機器
JP5901865B2 (ja) 表示制御装置及び表示制御方法
JP2015118483A (ja) 表示装置、表示連携システム、表示装置の制御方法、プログラム
JP2013172165A (ja) 車載装置と携帯情報端末が連携するシステム
JP2015108984A (ja) 表示制御装置及び表示制御方法

Legal Events

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

Ref document number: 13726887

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13726887

Country of ref document: EP

Kind code of ref document: A1