GB2502587A - Storing a Screenshot of an in-vehicle display apparatus interfaced with mobile device when a remote control connection error is detected - Google Patents

Storing a Screenshot of an in-vehicle display apparatus interfaced with mobile device when a remote control connection error is detected Download PDF

Info

Publication number
GB2502587A
GB2502587A GB1209714.3A GB201209714A GB2502587A GB 2502587 A GB2502587 A GB 2502587A GB 201209714 A GB201209714 A GB 201209714A GB 2502587 A GB2502587 A GB 2502587A
Authority
GB
United Kingdom
Prior art keywords
mobile device
screenshot
buffer
storage unit
vehicle
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.)
Withdrawn
Application number
GB1209714.3A
Other versions
GB201209714D0 (en
Inventor
Kurt Dusterhoff
David Blanc
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.)
Denso Corp
Original Assignee
Denso Corp
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 Corp filed Critical Denso Corp
Priority to GB1209714.3A priority Critical patent/GB2502587A/en
Publication of GB201209714D0 publication Critical patent/GB201209714D0/en
Priority to PCT/JP2013/003329 priority patent/WO2013179637A1/en
Publication of GB2502587A publication Critical patent/GB2502587A/en
Withdrawn legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/60Substation equipment, e.g. for use by subscribers including speech amplifiers
    • H04M1/6033Substation equipment, e.g. for use by subscribers including speech amplifiers for providing handsfree use or a loudspeaker mode in telephone sets
    • H04M1/6041Portable telephones adapted for handsfree use
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0739Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in automotive or aircraft systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0742Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0769Readable error formats, e.g. cross-platform generic formats, human understandable formats
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0778Dumping, i.e. gathering error/state information after a fault for later diagnosis
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0787Storage of error reports, e.g. persistent data storage, storage using memory protection
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input 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/14Digital output to display device ; Cooperation and interconnection of the display device with other functional units
    • G06F3/1454Digital output to display device ; Cooperation and interconnection of the display device with other functional units involving copying of the display data of a local workstation or window to a remote workstation or window so that an actual copy of the data is displayed simultaneously on two or more displays, e.g. teledisplay
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/60Substation equipment, e.g. for use by subscribers including speech amplifiers
    • H04M1/6033Substation equipment, e.g. for use by subscribers including speech amplifiers for providing handsfree use or a loudspeaker mode in telephone sets
    • H04M1/6041Portable telephones adapted for handsfree use
    • H04M1/6075Portable telephones adapted for handsfree use adapted for handsfree use in a vehicle
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409User 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/72415User 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
    • GPHYSICS
    • G09EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09GARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
    • G09G2380/00Specific applications
    • G09G2380/10Automotive applications

Abstract

A method comprising connecting a mobile device having a display to an in-vehicle device having an in-vehicle display wherein, once connected, display information to be displayed on the in-vehicle display is received from the mobile device and wherein the mobile device is remotely controllable from the in-vehicle device, thereby providing a remote control connection between the mobile device and the in-vehicle device; storing, at certain times, a buffer screenshot from the display information in a buffer memory; and if a remote control connection error is detected, storing a buffer screenshot in a storage unit. Thus, identifying which program and/or command caused the problem while the mobile device was connected to the in-vehicle device can be facilitated, thereby improving the troubleshooting of mobile device/in-vehicle device connections. Additionally, because the relevant screenshot is stored in the storage unit, the user can also access it at any time. Generally, the latest screenshot before the remote connection error is likely to contain relevant information with respect to the remote control connection error which may be appropriate when troubleshooting.

Description

ERROR HANDLING METHOD AND DEVICE
Field
The invention relates to error handling method and device.
Background
As a result of recent developments in mobile device services, it is now possible to connect a mobile device to an in-vehicle device and to control the mobile device remotely from the in-vehicle device. For example, JP 2003-244343 discusses an arrangement where the image on the screen of a mobile device is displayed on an in-vehicle display of an in-vehicle device when the mobile device is in the vehicle and connected to the in-vehicle device. The mobile device can be remotely operated from the in-vehicle display using the input means of the in-vehicle device.
However, if an error occurs while the phone is connected to the in-vehicle device, it can be difficult, and possibly dangerous, for the user in the vehicle to find out what the error is or by what it was caused, he. tD troubleshoot the problem. For example, if the in-vehicle display no longer shows the display of the mobile device, the user can not identify which program andlor command caused the problem from the in-vehicle display. It may also not be possible for the user to look at the mobile device's display to obtain more information in that respect. For example the mobile device may be in sleep or locked mode, may have its screen blacked-out while it is connected to the in-vehicle device, or may not be accessible to the user (for example in a glove box).
JP 04-115834 proposes a diagnostic method for determining a reason for an abnormal program termination and displaying the results to a user. However, in the case of an error in a mobile device and in-vehicle device connection, it is very unlikely that the in-vehicle will be able to access, let alone use, such information.
Summary
Aspects of the invention are defined in the appended claims.
The present approach has been created in view of drawbacks of known systems.
According to one aspect of the present disclosure, there is provided an arrangement where the error handling is improved so that troubleshooting from the in-vehicle device is facilitated and so that, for example, the user can be provided with more information as to what caused an error.
According to a another aspect of the disclosure, there is provided a method comprising connecting a mobile device having a display to an in-vehicle device having an in-vehicle display wherein, once connected, display information to be displayed on the in-vehicle display is received from the mobile device and wherein the mobile phone is remotely controllable from the in-vehicle device, thereby providing a remote control connection between the mobile device and the in-vehicle device; storing, at certain times, a buffer screenshot from the display information in a buffer memory; and if a remote control connection error is detected, storing a buffer screenshot in a storage unit. Owing to such a method, identifying which program and/or command caused the problem while the mobile device was connected to the in-vehicle device can be facilitated, thereby improving the troubleshooting of mobile device/in-vehicle device connections Additionally, because the relevant screenshot is stored in a storage unit, the user can also access it at any time, including for example immediately or at a later point in time once the user has stopped the vehicle in a safe place.
The storage unit may be a storage unit of the in-vehicle device In such an arrangement, the implementation complexity of the method may be simplified while troubleshooting by the user himself is facilitated compared to for example a remote storage unit.
Storing a buffer screenshot in a storage unit may include storing the most recent buffer screenshot in the storage unit. Generally, the latest screenshot before the remote connection error is likely to contain relevant information with respect to the remote control connection error which may be appropriate when troubleshooting, for example an error message from an application and/or command or an identification of one or more applications running before the error detection.
The method may comprise detecting a time at which the mobile device becomes non-responsive, wherein storing a buffer screenshot in a storage unit may then include storing, in the storage unit, the most recent of the buffer screenshots stored in the buffer memory before the detected tima Such a method can be useful when, for example, the mobile device becomes non-responsive some time before the connection error is detected, such that the most recent buffer screenshot may not be as relevant as an earlier buffer screenshot.
The method may comprise displaying the buffer screenshot stored in the storage unit on the in-vehicle display automatically and/or displaying the buffer screenshot stored in the storage unit on the in-vehicle display upon request. For example, the user could receive an indication that the connection is terminated with an display of a relevant screenshot as soon as the connection is terminated. The user may also, alternatively or additionally, view the screenshot at a possibly more appropriate time, for example once the user has stopped the vehicle in a safe place.
The method may comprise transferring the buffer screenshot stored in the storage unit to a remote element automatically and/or transferring the buffer screenshot stored in the storage unit to a remote element upon request. This can be appropriate for example to provide centralised troubleshooting of mobile devices/in-vehicle devices connection troubleshooting or for a user to keep a copy of a screenshot in a different storage, for example in a home computer's hard drive.
Storing a buffer screenshot in a storage unit may include storing a plurality of buffer screenshots in a storage unit. This may be appropriate when for example a single screenshot is likely to provide sufficient troubleshooting information and/or it may be unclear which screenshots may be appropriate to store in the storage unit.
The detected remote control connection error may include at least one of: an abnormal connection termination, the mobile device being non-responsive, the mobile device not sending display information, the mobile device sending an error message, the mobile device sending an incorrect message. Accordingly, a wide range of errors can be detected which enables a finer detection of error and thus enables a finer selection of the relevant screenshot.
According to a second aspect of the disclosure, there is provided an in-vehicle device comprising an in-vehicle display; a connection unit operable to connect to a mobile device having a display; a control unit operable to, upon connection of the in-vehicle device with the mobile device, control the mobile device remotely and display, on the in-vehicle display, display information received from the mobile device thereby providing a remote control connection between the mobile device and the in-vehicle device; a buffer memory; and an error handling unit operable to store, at certain times, a buffer screenshot from the display information in a buffer memory; operable to detect a remote control connection error; and operable to store, if a remote control connection error is detected, a buffer screenshot in a storage unit.
In the present disclosure, mobile device may refer to any mobile and/or portable device, for example a mobile phone (including a smartphone), a satellite navigation (sat-nay") device, a tablet, an audio player, a video player, a netbook or a portable computer.
Also, the term "vehicle" may refer to any transport, for example any form of car, lorry or motorcycle. Other clarifications as to the meaning of certain terms used herein can be
found throughout the present disclosure.
Brief Description of the drawings
Example embodiments will now be described by way of example only, with reference to the following drawings, which merely illustrate example arrangements in accordance with the presently disclosure and cannot be considered as limiting the scope of the present invention: Fig. 1 is a schematic illustration ol a mobile device and an in-vehicle device; Fig. 2 is an example illustration of a mobile device connected to an in-vehicle device; Fig. 3 is a flowchart illustrating an example error handling method; Fig. 4A-4B are illustrations of possible in-vehicle devices; Fig. 5 is a flowchart illustrating another example error handling method; and Fig. 6 is an example illustration of a mobile device and an in-vehicledevice after a connection error.
While the invention is described herein by way of example for several embodiments and illustrative drawings, those skilled in the art will recognize that the invention is not limited to the embodiments or drawings described. It should be understood, that the drawings and detai!ed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention. The headings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description. As used throughout this application, the word "may" is used in a permissive sense (i.e. meaning "might") rather than the mandatory sense (i.e., meaning "must"). Similarly, the words "include", "including", and includes" mean including, but not limited to.
Description
With reference to Fig. 1, a mobile device 10, connectable to an in-vehicle device 20, may include the following elements: a display unit 12 for displaying content to a user, a communication unit 14 for communicating with at least the in-vehicle device 20, a control unit 16 for controlling processes running on the mobile device 10, and a memory unit 18.
On the other hand, the in-vehicle device 20 may include a display unit 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 in-vehicle device 20 may also include a connection unit 26B which may for example be part of the control unit 26 and/or the communication unit 24, the connection unit being for connecting the in-vehicle device to a mobile device. The mobile device 10 and the in-vehicle device 20 may be connected so that the mobile can be remotely controlled from the in-vehicle device and so that display information is received at the in-vehicle device 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. Connections may typically be a wired connection such as a USB or FireWire connection but may alternatively be a wireless connection such as Bluetooth, Wi-Fl or lR.
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 in this example shows the same image as the display unit 12 of the mobile device 10. Once connected, the mobile device 10 can be remotely controlled from the in-vehicle device, for example with the use of a touchscreen on the display unit 22 and/or the use of a one or more buttons 25.
Any other suitable input means, for example touch or voice command input means, may be used. It is noteworthy that, in the illustration of Fig. 2, the screen of the mobile device 10 is 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 However, in other examples 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 has not been used for a predetermined time. Once the mobile device 10 and the in-vehicle device 20 are connected, the user can control the mobile device 10 from the in-vehicle display-For example, the user may be able to use buttons, such as buttons 25a and 25b, 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's native input means and display.
Also, once connected, the mobile device 10 sends display information to the in-vehicle device 20 and the in-vehicle device 20 displays 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. Based on this display information, an image can be displayed on the in-vehicle display based on images received in the display information and/or based on images reconstructed from the received display information. In some examples, the display information sent by the mobile device 10 will corresponds exactly to what is -or would have been-displayed on the mobile device's display 12. In these cases, the display information can have the same pixel and colour resolution as the mobile device's display. In other cases, the display information may correspond to a display which differs from the mobile device's display. In that event, the display information may for example have a lower pixel andIor colour resolution so that less information has to be transmitted. However, in other 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's 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. This is known to the skilled person and may for example involve pixel resolution or colour resolution up-scaling or down-scaling, or displaying only a part of the mobile device's display (with for example the option to show another part of the mobile device's screen by moving a cursor to the sides of the in-vehicle display).
The connection between the mobile device 10 and in-vehicle device 20 may be used for example to use a sat-nay function of the mobile-device from the in-vehicle device, or any other function of the mobile device 10. For example the user may use a web browser, games, mobile apps, etc. of the mobile device 10 from the in-vehicle device. In other words, the remote control connection between the mobile device 10 and the in-vehicle device can be considered as a VNC or VNC-like connection.
When an error occurs in such a connection, it may not be possible to troubleshoot the connection between the mobile device 10 and the in-vehicle device. For example, if the display 12 of the mobile device 10 was turned off or blacked out when the error occurred, the user is unlikely to be able to identify a possible source of the technical fault from the in-vehicle device. In another example, even if the screen of the mobile device 10 is on when the error occurs, the user may not be able to see the display on the mobile device 10 (for example because it is out of sight in a glove box or elsewhere) and the in-vehicle display 22 may not, or no longer, show information relevant to the error. For example the in-vehicle display 22 may have stopped displaying the display information received from the mobile device 10 because of the remote control connection error, the error itself may have prevented the in-vehicle device 20 from receiving any error-related display information from the mobile device 10; and/or because too much time has elapsed since the error occurred.
Fig. 3 is a flowchart illustrating an example error handling method. At step S301, the mobile device 10 and in-vehicle device 20 connect so that the mobile device 10 can be controlled from the in-vehicle device 20 and so that display information from the mobile device 10 can be displayed on the in-vehicle display 22 as discussed above. The connection may be any suitable connection. For example it may be a wired and/or a wireless connection. The in-vehicle device 20 then stores at step S302 a screenshot in a buffer memory, wherein the screenshot is based on the display information received from the mobile device 10. The in-vehicle device can keep storing at certain times screenshots in the buffer as long as the mobile device 10 and the in-vehicle device 20 are connected via a the remote control connection, as checked at step S303. If the two devices are no longer connected, the in-vehicle device can stop storing screenshots in the buffer memory.
In the example of Fig-3, the in-vehicle device 20 monitors the connection for errors at step S311 in parallel to steps S302-S303. If an error is detected at step S312, the method moves on to step S313, otherwise the method keeps monitoring errors in the connections (step S311). At step S313, the in-vehicle device stores the most recent screenshot in the buffer memory into a storage unit, thereby saving possibly useful information for troubleshooting the connection error detected at S312, which would otherwise not be saved or stored. The screenshot. stored in the storage unit may then be accessed either automatically or upon request, for example to be displayed on the in-vehicle display 22 and/or to be transferred to a remote element. Accordingly, the connection troubleshooting by the user or by a party having access to the remote element is thereby faéilitated.
The certain times at which the screenshot can be stored in the buffer memory can be most appropriately chosen based on each specific situation and requirements for the system. For example, storing a screenshot periodically may be easier to implement. In one embodiment, the screenshot can be stored at regular intervals, for example every second or every 10 seconds. In another embodiment, it may be stored at irregular intervals, for example taking into account a random component and/or a processing load of the in-vehicle device 20. In one implementation, the new screenshot may be stored in the buffer memory after a time t has elapsed since the previous screenshot, where I = To + rand (0, t) and T0 and t0 are predetermined. Such an implementation ensures that at least T0 has passed since the last screenshot. It also ensures that the screenshots are not too regular, owing to the additional random component between 0 and t, which can be recommended for example in order to avoid several programs carrying out respective repetitive tasks at the same time which can cause activity peaks at the in-vehicle device. The relative weight of the regular component T0 and of the random component based on t0 may be adjusted by adjusting T0 and t0 in order to achieve the desired effect (a low random component, a high random component or balanced random/regular components). Likewise, the processing load of the in-vehicle device may, additionally or alternatively, be taken into account and the screenshot storing may for example be delayed to a certain extent if it is identified that the in-vehicle device 20 is busy.
Other indicators may also be considered when deciding when to store a screenshot in the buffer memory. For example, any indicator that an error is more likely to occur may be used. This may involve taking into account any indication that the mobile device 10 is running short of memory and/or processing resources (if for example communicated to the in-vehicle device 20) and/or any reduction or unexpected irregularities in the display information transmitted from the mobile device 10. If any error indicators appear to show that an error is more Iik&y, screenshots may be stored in the buffer memory more frequently.
Therefore the screenshot may be stored in the buffer memory at any appropriate time and, in some embodiments, the in-vehicle device may be configurable between different modes for deciding when to take the next screenshot, for example any of the modes discussed above.
It is noteworthy that the steps 8302-S303 and steps S31 1-8313 have been illustrated in parallel in Fig-3, however, they may be carried in series or in any suitable series and/or parallel order. For example, in one embodiment, the steps may be carried out in the following order S301, 8302, S31 1, a hybrid 8312-8303 step, with a return to 8302 or 8311 if no connection error is detected and moving on to step 8313 if an error is detecteft Also, the method may be implemented as appropriate and for example may include at least a part continuously running and checking for errors andlor storing screenshots; andlor at least a 1 5 part with a trigger-based implementation which only actively runs after it has been triggered.
For example, a trigger may be triggered by a connection error (eg. for S312) or the expiry of a timer (e.g. for S302).
Also, the connection error may include any of an abnormal connection termination, the mobile device 10 being non-responsive, the mobile device 10 not sending display information, the mobile device 10 sending an error message, the mobile device 10 sending an incorrect message. An abnormal connection termination may be for example the termination of a connection where one of the termination messages identifies the termination as abnormal, for example with the use of an error code or where a termination message was not expected at this stage. It may also include a termination caused by a connection time-out. The mobile device 10 being non-responsive may include the mobile device 10 not responding to in-vehicle device's messages and/or the mobile device 10 no longer sending messages it is expected to send, for example display information message or keep-alive messages. As discussed, the mobile device 10 not sending display information while it should be connected to the in-vehicle device 20 can be considered as a connection error in the connection between the mobile device 10 and the in-vehicle device 20. Also, if the mobile device 10 sends a error message, this could be an indication of a connection error, if for example the error message relates to a connection error for any layer lower than the layer for the remote control connection, to an error in the communication unit 14 or to an application used for or by the connection between the two devices. Another possible indication that an error has occurred is the mobile device 10 sending an incorrect message. If for example the mobile device 10 is expected to send a particular message,
B
either as a first message or following a previous message / in response to a previous message, and instead send a different message, this could be an indication that an error has occurred in the connection between the mobile device ID and the in-vehicle device 20.
Any other appropriate indication that an error has occurred, or is likely to have occurred, may be used at step Sal 2. Also, in some situations, the in-vehicle device may require more than one error indications before it detects that an error has occurred. If for example the indication has a relatively low reliability (e.g. the mobile device 10 has sent an incorrect message) for the purposes of indicating a remote control connection error, the in-vehicle device may wait for a second, third or more indication(s) confirming that an error has occurred before detecting the error If however the indication has a relatively higher reliability (e.g. an abnormal connection termination), the in-vehicle device may not wait for any additional indication and consider this single indication as reliable enough to detect that a connection error has occurred.
In the discussion above, the buffer memory or "buffer generally refers to some form of temporary storage. For example, a buffer may generally refer to a memory element, either independent or part of a bigger memory element, which is for short-term usage. Any data stored in a buffer generally remains available on a short term basis and may be erased later on. For example, it may be erased if the power source is turned off (e.g. volatile memory) andlor it may be erased when new data has to be stored in the buffer which would otherwise overflow. In the latter situation, the buffer is generally maintained based on a FIFO algorithm: the new data would overwrite the oldest data in the buffer. However, other implementations may be used (based for example on the least recently used data). Thus the buffer memory can for example include any appropriate one or combination of volatile memory, non-volatile memory, any fixed sized memory, any capped-size memory, volatile or non-volatile RAM memory. Also, the buffer may be provided as part of, or as a separate in-vehicle equipment. For example, the buffer may be part of a larger storage unit, may be part of the display unit.
The storage unit may refer to any longer term memory, for example non-volatile memory. It may be appropriate to use non-volatile memory because the screenshot stored in the storage unit would remain available even in the event of a power failure or of the * power source being turned off. Also, the storage unit may be an element of the in-vehicle device 20, for example all or part of the memory unit 28, or may be separate from the in-vehicle device, such as a memory card inserted by the user or may be a remote storage unit. For example, the storage unit may be a memory card (e.g. removable by the user, removable but not accessible to the user, or fixed to the in-vehicle device) and/or any removable or non removable memory element-In the event that the storage unit is removable, or contained in a removable element, the screenshot stored in the storage unit may be stored in the removable element, if present, that the user can take with him, for example to make backup copies of the screenshot on a computer, In the event that the storage unit is a remote storage unit, the screenshot may for example be stored in a configurable location such as a personal computer, a centralised server, or any other appropriate storage unit In other examples, the remote storage unit may not be configurable or not user-configurable. For example it may only be configurable remotely by a party authorised to maintain at least a part of the in-vehicle device. In some examples, the buffer and storage unit are provided in the same in-vehicle equipment, for example the ID display unit.
Fig. 4A and Fig. 4B are illustrations of possible in-vehicledevice arrangements. In Fig. 4A the memory unit 28 includes a buffer 28A and a storage unit 28B. In one example, the buffer 28A and the storage unit 2&B may correspond to different memory sectors of a single memory element. Alternatively, the representation may also be seen as a logical representation and the buffer 28A and the storage unit 28B may be from two different memory elements (e.g. RAM memory and a solid-state disk) which can be addressed from the same interface. In the arrangement of Fig. 4A, the control unit 26 is provided with an error handling unit 26A for carrying out most steps of the method as discussed above. For example, the error handling unit may be carrying out steps S302-303 and S31 1-313. In another example, the error handling unit 26A may only be carrying out some of these steps.
Also, the error handling unit 26A of Fig. 4A is better viewed as a logical element, for example as a function of the control unit 26, but it can also be viewed as a physical element (e.g. having its own hardware). In the example of Fig. 4A the error handling unit ZGA is logically and/or physically part of the control unit 26, but in other example, it may be an independent logical and/or physical element, for example controlled by the control unit 26.
In the arrangement of Fig. 4B, the buffer 28A and the storage unit 28B are separate and each is connected to the other elements of the in-vehicle device. In one example, the buffer 28A may be provided by RAM memory while the storage unit 28B may be provided by a non-volatile hard drive disk. Also, in this example, the error handling unit 26A is represented as an independent logical and/or physical element connected to the control unit 26. In other examples, the error handling unit 26A may also be an independent logical and/or physical element connected to any other element, for example to each of the display unit 22, the communication unit 24, the control unit 26, and the memory unit 28 and/or buffer 28A and/or storage unit 28B. Also, as discussed above, the in-vehicle device may include a connection unit (not shown). In other words, any other suitable arrangement which provide the functions discussed in the present disclosure may be used.
Fig 5 is a flowchart illustrating another example of a method for error handling. At S step 8501, the mobile device 10 and in-vehicle device 20 are connected, for example as in the discussion above in respect of Fig. 2 and 3. Then, the in-vehicle device (e.g. the error handling unit 26A) stores, at certain times, a screenshot from the display information received from the mobile device 10 in the buffer memory at step 5502 and carries on storing screenshots while the two devices remain connected (5503). In parallel, the in-vehicle device monitors errors in the connection and responsiveness of the mobile device at step 5521. At step S522, it is decided whether the mobile device 10 changed between responsive and non-responsive. Just after 5501, once the remote control connection is established, the mobile device 10 will be, or will be considered as, responsive If the mobile device 10 changes from responsive to non-responsive, the method moves to step 8523 where the detected change time is set as the cut-off time. In other words, at steps S522-523, it is detected a time at which the mobile device 10 becomes non-responsive. If the mobile device 10 changes from non-responsive to responsive, the cut-off time is reset at step 5524. Therefore, in a situation where the mobile device 10 changes from responsive to non-responsive and, at a later point in time, back to responsive, the cut-off time set when the mobile device 10 first became hon-responsive will no longer be used in the next steps of the method, even in a case where a connection error occurs while the mobile device 10 is responsive.
If the mobile device 10 did not change between responsive and non-responsive, or after steps 8523 or 8524 have been carried out, the method moves on to step 5525 to determine whether an error has been detected. If a connection error is detected, the last screenshot stored in the buffer before the cut-off time (La the time at which it is detected that the mobile device 10 changed from responsive to non-responsive) is stored into a storage unit. If no error has been detected at step S525, the connection errors and the responsiveness of the mobile device 10 remain monitored. Also, step S526 may include, if the cut-off time has not been set (e.g. if it has never been set at S523 or if it has been reset at S524) considering the current time as the cut-off time for the purpose of identifying which screenshot to store in the storage unit.
In another example, the method may not include step S524 (for example step in S522 changes to non-responsive are monitored). Step 5526 may then include checking for the mobile device's responsiveness and, accordingly, setting the current time as the cut-off time in an event that the mobile device 10 is detected as responsive, before the screenshot is stored in the storage unit. Thus, if the mobile device 10 is responsive when step S526 is carried out the most recent screenshot will be stored in the storage unit and, if the mobile device 10 is still non-responsive when step S526 is carried out, the most recent screenshot stored in the buffer before the cut-off time will be stored in the storage unit.
These example methods can be appropriate to avoid situations where possibly less useful screenshots are being stored in the storage unit. For example, if the mobile device had already crashed or frozen when the most recent screenshot in the buffer was taken, this last screenshot may for example be a blank or black screen which would then not be useful for troubleshooting the connection error. Additionally, the last screenshot before the mobile device became non-responsive may include hints as to what caused the mobile device to become non-responsive.
Alternatively, in some examples, the screenshot to be stored in the storage unit may depend on a pre-determined, configurable, or dynamic parameter T1 such that the buffer screenshot stored in the storage unit is the most recent of the buffer screenshot stored in the buffer before I -T1 where t corresponds, for example, to the current time or to the detected error time. T1 might be predetermined, if for example it has been observed that the most useful screenshots had been saved is or 10 ms before the error is detected, T1 may be fixed to the corresponding value. It may also be configurable, for example by the user and/or another party authorised to change this parameter. It may also be dynamically determined. For example T1 may be selected to be very small in an event that the remote control connection error detected is a sudden error (e.g. an abrupt end of a program), and may be selected to be bigger in the event of a less sudden error (e.g. an connection time-out).
Compared to the method of Fig. 3, the method of Fig. 5 (and any alternative and/or modification discussed) would be more complex to implement, but may provide more relevant troubleshooting information. Thus, if it is desired that the error-handling function of the in-vehicle device uses as little computing resources as possible, it may then for example be preferable to opt for an arrangement carrying out a method similar or identical to the method shown in Fig. 3 rather than that of Fig. 5.
Of course, the discussions in respect of the certain times for storing the screenshot in a buffer, steps being carried our in series and/or in parallel, the connection error, the buffer memory and the storage unit in the discussion above in respect of Fig. 3 apply equally to the method of Fig. 5, to any alternative and/or modified method discussed, and to any other appropriate method, device or system according to the present disclosure.
Other modifications and/or additions can be carried out to any of the previously discussed methods or arrangements as described below In the interest of conciseness and intelligibility, a screenshot stored in the buffer memory will be referred to as buffer screenshot' and a screenshot stored in the storage unit as storage screenshot".
In one example, if a time at which the mobile device becomes unresponsive is detected, both the most recent buffer screenshot and the most recent of the buffer screenshots stored in the buffer memory before the detected time are stored in a storage unit. They could for example be stored in the same or different storage unit More generally, n buffer screenshots may be stored in a storage unit, with n »= 1, and the number of storage screenshot may also depend on the situation, for example on the remote control connection error-In one example, a sudden disconnection could result in one buffer screenshot being stored while a connection timeout could result in at least two buffer screenshots being stored in a storage unit. Also, the n buffer screenshots stored in a storage unit may be storage in any number of storage unit, for example one or n.
Also, once a screenshot has been stored in the storage unit, it can be displayed on the in-vehicle display automatically and/or upon request. For example Fig. 6 is an example illustration of a mobile device and an in-vehicle device after a connection error, wherein at least one of the storage screenshot(s) is displayed on the in-vehicle display. In this example, the troubleshooter would be in a position to identify that the sat-nay application of the mobile device 10 is likely to have caused the error and address the problem accordingly. In some example, an error screen can be displayed on the in-vehicle display 22 automatically as soon as the error occurred (for example so that the user can know immediately that a connection error has occurred) andfor automatically at a later point in time (for example once it has been detected that the vehicle has stopped and that it is thus safer for the troubleshooter to use with the mobile device 10 and in-vehicle device 20 to fix the problem) and/or on request at a later point in time (for example once the user knows that he can safely use the two devices).
Also, the storage unit may not be part of the in-vehicle device and may be a remote element, such as a server or a personal computer. This may for example to facilitate central troubleshooting and detection of common problems which may for example indicate the presence of a bug and/or of a problem that should be worked around if possible.
The storage screenshot may also be sent to a remote element automatically andlor upon request so that the user can troubleshoot the connection error and a party centralising storage screenshots can detect common problems andlor carry out statistical analysis of the connection error& The methods discussed in the present disclosure may be implemented in any combination of software and hardware, including in full software implementation or in full hardware implementation.

Claims (20)

  1. Claims 1. A method comprising: connecting a mobile device having a display to an in-vehicle device having an vehicle display wherein, once connected, display information to be displayed on the in-vehicle display is received from the mobile device and wherein the mobile device is remotely controllable from the in-vehicle device, thereby providing a remote control connection between the mobile device and the in-vehicle device; storing, at certain times, a buffer screenshot from the display information in a buffer memory; and if a remote control connection error is detected, storing a buffer screenshot in a storage unit.
  2. 2. The method of claim 1 wherein the storage unit is a storage unit of the in-vehicle device.
  3. 3. The method of claim 1 or 2 wherein storing a buffer screenshot in a storage unit includes storing the most recent buffer screenshot in the storage unit.
  4. 4. The method of any preceding claim comprising detecting a time at which the mobile device becomes non-responsive, wherein storing a buffer screenshot in a storage unit includes storing, in the storage unit, the most recent of the buffer screenshots stored in the buffer memory before the detected time.
  5. 5. The method of any preceding claim comprising displaying the buffer screenshot stored in the storage unit on the in-vehicle display automatically.
  6. 6. The method of any preceding claim comprising displaying the buffer screenshot stored in the storage unit on the in-vehicle display upon request.
  7. 7. The method of any preceding claim comprising transferring the buffer screenshot stored in the storage unit to a remote element automatically.
  8. 8. The method of any preceding claim comprising transferring the buffer screenshot stored in the storage unit to a remote element upon request.
  9. 9. The method of any preceding claims wherein storing a buffer screenshot in a storage unit includes storing a plurality of buffer screenshots in a storage unit.
  10. 10. The method of any preceding claims wherein the detected remote control connection error includes at least one of: an abnormal connection termination, the mobile device being non-responsive, the mobile device not sending display information, the mobile device sending an error message, and the mobile device sending an incorrect message.
  11. 11. An in-vehicle device comprising: an in-vehicle display; a connection unit operable to connect to a mobile device having a display; a control unit operable to, upon connection of the in-vehicle device with the mobile device, control the mobile device remotely and display, on the in-vehicle display, display information received from the mobile device thereby providing a remote control connection between the mobile device and the in-vehicle device; a buffer memory; and an error handling unit operable to store, at certain times, a buffer screenshot from the display information in a buffer memory; operable to detect a remote control connection error; and operable to store, if a remote control connection error is detected, a buffer screenshot in a storage unit.
  12. 12. The in-vehicle device of claim 11, wherein the storage unit is comprised in the in-vehicle.
  13. 13. The in-vehicle device of claim 11 or 12 wherein the buffer screenshot stored in the storage unit is the most recent buffer screenshot.
  14. 14. The in-vehicle device of any one of claims 11 to 13, wherein the error handling unit is operable to detect a time at which the mobile device becomes non-responsive and wherein the buffer screenshot stored in the storage unit is the most recent of the buffer screenshots stored in the buffer memory before the detected time.
  15. 15. The in-vehicle device of any one of claims 11 to 14 wherein the error handling unit is operable to display the screenshot stored in the storage unit on the in-vehicle display automatically.
  16. 16. The in-vehicle device of any one of claims 11 to 15 wherein the error handling unit is operable to display the screenshot stored in the storage unit on the in-vehicle display upon request.
  17. 17. The in-vehicle device of any one of claims 11 to 16, wherein the error handling unit is operable to transfer the screenshot stored in the storage unit to a remote element automatically.
  18. 18. The in-vehicle device of any one of claims 11 to 17, wherein the error handling unit is operable to transfer the screenshot stored in the storage unit to a remote element upon request.
  19. 19. The in-vehicle device of any one of claims 11 to IS, wherein the error handling unit being operable to store, if a remote control connection error is detected, a buffer screenshot in a storage unit includes the error handling unit being operable to store, if a remote control connection error is detected, a plurality of buffer screenshots in a storage unit
  20. 20. The in-vehicle device of any one of claims 11 to 18, wherein the detected remote control connection error includes at least one of: an abnormal connection termination, the mobile device being non-responsive, the mobile device not sending display information, the mobile device sending an error message, and the mobile device sending an incorrect message.
GB1209714.3A 2012-05-31 2012-05-31 Storing a Screenshot of an in-vehicle display apparatus interfaced with mobile device when a remote control connection error is detected Withdrawn GB2502587A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
GB1209714.3A GB2502587A (en) 2012-05-31 2012-05-31 Storing a Screenshot of an in-vehicle display apparatus interfaced with mobile device when a remote control connection error is detected
PCT/JP2013/003329 WO2013179637A1 (en) 2012-05-31 2013-05-27 Error handling method and in-vehicle device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1209714.3A GB2502587A (en) 2012-05-31 2012-05-31 Storing a Screenshot of an in-vehicle display apparatus interfaced with mobile device when a remote control connection error is detected

Publications (2)

Publication Number Publication Date
GB201209714D0 GB201209714D0 (en) 2012-07-18
GB2502587A true GB2502587A (en) 2013-12-04

Family

ID=46582147

Family Applications (1)

Application Number Title Priority Date Filing Date
GB1209714.3A Withdrawn GB2502587A (en) 2012-05-31 2012-05-31 Storing a Screenshot of an in-vehicle display apparatus interfaced with mobile device when a remote control connection error is detected

Country Status (2)

Country Link
GB (1) GB2502587A (en)
WO (1) WO2013179637A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101736990B1 (en) 2015-10-26 2017-05-17 현대자동차주식회사 Apparatus and method for controlling mobile device engaging with vehicle
WO2017177302A1 (en) 2016-04-15 2017-10-19 Light Wave Technology Inc. Automotive rear-view camera peripheral
WO2018010023A1 (en) 2016-07-11 2018-01-18 Light Wave Technology Inc. Command relay device, system and method for providing remote assistance / remote control

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006063603A1 (en) * 2004-12-14 2006-06-22 Bayerische Motoren Werke Aktiengesellschaft System for utilizing at least one mobile terminal device in a motor vehicle
WO2007030638A2 (en) * 2005-09-08 2007-03-15 Johnson Controls Technology Company Front supervision of rear seat entertainment system
US20090153434A1 (en) * 2007-12-14 2009-06-18 Jzung-I Cheng Display assistant system
US20100328469A1 (en) * 2009-06-30 2010-12-30 Kabushiki Kaisha Toshiba Information processing apparatus and capture image transmitting method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003244343A (en) * 2002-02-21 2003-08-29 Toyota Motor Corp Display device, portable terminal and information display system
US8996930B2 (en) * 2010-10-26 2015-03-31 Red Hat, Inc. Error video creation, playback and reporting

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006063603A1 (en) * 2004-12-14 2006-06-22 Bayerische Motoren Werke Aktiengesellschaft System for utilizing at least one mobile terminal device in a motor vehicle
WO2007030638A2 (en) * 2005-09-08 2007-03-15 Johnson Controls Technology Company Front supervision of rear seat entertainment system
US20090153434A1 (en) * 2007-12-14 2009-06-18 Jzung-I Cheng Display assistant system
US20100328469A1 (en) * 2009-06-30 2010-12-30 Kabushiki Kaisha Toshiba Information processing apparatus and capture image transmitting method

Also Published As

Publication number Publication date
GB201209714D0 (en) 2012-07-18
WO2013179637A1 (en) 2013-12-05

Similar Documents

Publication Publication Date Title
US20180077230A1 (en) Method and apparatus for switching between servers in server cluster
CN108872762B (en) Electronic equipment leakage detection method and device, electronic equipment and storage medium
US10217299B2 (en) Vehicular information communication system and vehicular information communication method
US10521313B2 (en) Uninterrupted data availability during failure in redundant micro-controller system
CN110188016B (en) Method, terminal and storage medium for detecting application program no-response blocking
CN107145269B (en) Data rotation method and device
CN111104283B (en) Fault detection method, device, equipment and medium of distributed storage system
CN109673009A (en) A kind of VCU software over-the-air upgrade method and device
US20120047292A1 (en) Monitoring System, Device Server, Host Computer, Monitoring Method, and Storage Medium
CN107908487B (en) Task control management method, device and equipment and computer readable storage medium
GB2502587A (en) Storing a Screenshot of an in-vehicle display apparatus interfaced with mobile device when a remote control connection error is detected
US9336075B2 (en) Monitoring apparatus, monitoring method, and storage medium
CN104750537B (en) Method and device for executing test case
WO2023206883A1 (en) Dynamic storage method and apparatus for battery data, and related device
CN106970793B (en) Context consistency detection and repair system, detection method and platform
CN115396292B (en) Vehicle-mounted network recovery method, system, electronic equipment and storage medium
CN113849350A (en) Ring-shaped two-place three-center topology switching method, device, system and medium
JP6220176B2 (en) In-vehicle communication terminal
US9684355B2 (en) Identifying power state changes
KR20140077377A (en) Processing system and method for initial service image on virtualization platform
CN111712801A (en) Device with networking function
US20190243738A1 (en) Fault Monitoring for a Complex Computing Unit
WO2018135135A1 (en) See-through display device, system, program, and information processing method
US10528467B2 (en) Information processing device and information processing method
US20130238284A1 (en) Testing method

Legal Events

Date Code Title Description
WAP Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1)