JP2004314773A - On-vehicular information system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To always inform a user, i.e., an owner of a message. <P>SOLUTION: When an event is generated during a period that a user class becoming a driver at present and discriminated by a user discrimination part 104 is not the owner, a message processing part 105 extracts the message corresponding to the event and the user class generated from a message table of a memory 106 and displays it on an indicator 11. The message processing part 105 extracts the message corresponding to the event generated from the message table and the user class and stores it in the memory 106 as uninformed message data. The message processing part 105 displays the message indicated by the uninformed message data stored in the memory 106 on the indicator 11 at the time when the user discrimination part 104 discriminates that the user in which the user class is the owner becomes the driver at present. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a technology for notifying a driver of a message for notifying a situation related to a vehicle in an in-vehicle information system mounted on a vehicle.
[0002]
[Prior art]
In the in-vehicle information system mounted on the car, as a technology for notifying the driver of a message that notifies the driver of the situation related to the vehicle, the occurrence of a failure in the vehicle is monitored and displayed on a simple message driver regarding the generated failure, 2. Description of the Related Art A technique for displaying detailed information on a failure for maintenance in response to a predetermined terminal short-circuit operation at a repair shop or the like is known (for example, JP-A-10-266889).
[0003]
Prior art document information related to the invention of this application includes the following.
[0004]
[Patent Document 1]
JP, 2002-245762, A
[Problems to be solved by the invention]
Now, one vehicle may be shared by a plurality of users. For example, in a home, it is common to see a father driving a car mainly for excursions on weekends and a mother driving a car for shopping and picking up children on weekdays. Even when the vehicle is shared by a plurality of users, one of the plurality of users often has authority or responsibility for repair and management of the vehicle.
[0006]
Now, in a vehicle, there are various types and types of messages to be notified to a driver according to a situation regarding the vehicle. And not all messages are equally useful to all users. On the other hand, there are also messages that need to be always notified to a specific user. For example, a message regarding the management of a vehicle that does not require urgency (for example, a notification of the issuance of an upgraded version of software of a vehicle-mounted navigation device) is unnecessary for a user who does not have authority or responsibility for repair or management of a vehicle. On the other hand, it is necessary to notify the user having such authority or responsibility without fail.
[0007]
Therefore, an object of the present invention is to notify a user who is to be notified of a situation regarding a vehicle to a user who is appropriate as a notification destination of the information in a form suitable for the user.
[0008]
[Means for Solving the Problems]
In order to achieve the above object, the present invention provides an in-vehicle information system mounted on an automobile for notifying a driver of a message corresponding to an event that has occurred, for each of a plurality of users, a user class in which the class of the user is registered. A management table, a message table for specifying a message for each event to be notified to the user for each class, a storage means for storing, a user who is currently a driver, and the user class management table of the identified user User identification means for extracting a class registered in the message table, and message notification means for notifying a driver of a message for an event that has occurred, the message being specified in the message table for the class extracted by the user identification means, when an event occurs. And so on.
[0009]
According to such an in-vehicle information system, it is possible to notify a driver at the time of an event of a message according to a class as a user of the driver. Thus, for example, if a class of users has a class of users who have authority or responsibility for repair or management of vehicles and a class of other users, a user having authority or responsibility for repair or management of vehicles can be provided. When the user is a driver, the user is notified of a message including detailed information necessary for repairing and managing the vehicle related to the event that has occurred. To the user, a message related to the event that occurred is not necessary for a user who does not have authority or responsibility for repair or management of the vehicle, or information that is not appropriate to be presented to such a user is excluded. Or be notified.
[0010]
Here, in such an in-vehicle information system, in the message notification unit, when an event occurs, the class extracted by the user identification unit is not a predetermined specific class, but in the message table, for the specific class, When a message for the event that has occurred is specified, the message is stored as an unnotified message, and the message stored as an unnotified message when the user identification unit extracts the specific class is sent to the driver. It is also preferable that the notification be made.
[0011]
By doing so, for example, as described above, when a class of a user who has authority or responsibility for repair and management of a vehicle and a class of another user are provided as classes of a user, repair and management of the vehicle are performed. When a user with authority or responsibility for repairing or managing a vehicle issues a message about an event that occurs when the user with authority or responsibility for You will be able to be notified when you board as a driver.
[0012]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described.
FIG. 1 shows a configuration of an in-vehicle information system according to the present embodiment.
As shown in the figure, the on-vehicle information system includes an electronic control unit 6 (ECU) that performs electronic control of basic functional systems as an automobile, such as an engine system 1, a transmission system 2, a suspension system 3, a brake system 4, and a door lock system 5. )have. Further, an ignition key unit 7 for receiving a user's operation of an ignition key, a keyless entry system 8 for receiving a key operation of unlocking and locking a door by a user's remote key (for example, an infrared remote controller), and a control unit 10 to which an input device 9 is connected. And a display control device 12 for performing control such as switching display on the display device 11. The in-vehicle information system includes various electric devices such as an accessory device 13 such as a navigation device and an AV device, an air conditioner 14, and a sea position actuator 15 for adjusting a sea position.
[0013]
In such a configuration, the control unit 10 is connected to the ignition key unit 7, the keyless entry system 8, the display control device 12, the accessory device 13, the air conditioner 14, the sea position actuator 15, the ECU 6, and the control bus 16. The control bus 16 is used to exchange information with the connected devices and to control the operation of the connected devices.
[0014]
Further, the display control device 12 is connected to a display signal line 17 used by the control unit 10 and the accessory device 13 for outputting a video signal, and the display control device 12 transmits the video signal to the display device 11 according to the control of the control unit 10. The processing of switching the output source of the video signal for outputting the video signal, or combining the video signals from a plurality of output sources on one screen and displaying it on the display device 11 is performed.
[0015]
Next, FIG. 2 shows a configuration of the control unit 10.
As shown in the figure, the control unit 10 performs input from each device via the input device 9 and the control bus 16, output of a video signal to the display control device 12, and output to each device via the control bus 16. It has an input / output processing unit 101 for controlling, an event analysis unit 102, a device control unit 103, a user identification unit 104, a message processing unit 105, and a memory 106. The memory 106 stores a user management table, a vehicle management table in which vehicle inspection and periodic inspection due dates are registered, a message table, a current user table, unreported message data, and the like.
[0016]
In such a configuration, when the input / output processing unit 101 receives a notification of an event from each device via the control bus 16 or a notification of a user operation occurrence event from the input device 9, the input / output processing unit 101 sends the notification to the event analysis unit 102. The event analysis unit 102 distributes the transferred event to the device control unit 103, the user identification unit 104, and the message processing unit 105 according to the content of the transferred event and the current processing status of the control unit 10. .
[0017]
Then, the device control unit 103, the user identification unit 104, and the message processing unit 105 perform processing according to the sorted event.
Hereinafter, operations of the device control unit 103, the user identification unit 104, and the message processing unit 105 will be described.
First, upon receiving a notification of a user's key operation event from the ignition key unit 7 and a notification of a user's door lock locking / unlocking operation event from the keyless entry system 8, the event analysis unit 102 transmits the notification to the device control unit. 103 and the user identification unit 104.
[0018]
The device control unit 103 controls the ECU 6 via the input / output processing unit 101 to control the engine system 1 in response to a key operation by the user, and to control the door lock system 5 in response to the locking / unlocking operation of the door lock by the user. Instruct.
On the other hand, if the transferred event is an event indicating a transition from the non-boarding state of the driver to the boarding of the driver, such as a key mount to the ignition key unit 7 or an unlocking operation of the door, the user identification unit 104 Based on the identification data notified from the ignition key unit 7 and the keyless entry system 8 when the event occurs, the user who is the current driver and its class are referred to by referring to the user management table stored in the memory 106. The determination is made, and the identification and class of the determined user are stored in the memory 106 as current user data. Further, the device control unit 103 is notified of the determined user, and the device control unit 103 controls the input / output processing unit 101 to realize the air conditioning state and the seat position state registered in advance for the determined user. The control unit controls the air conditioner 14 and the seat position system via the air conditioner.
[0019]
Here, in the user management table, as shown in FIG. 3A, for a plurality of users, user IDs (A, B, C), identification data for identifying the users, and user Class is registered. In the present embodiment, as the class of the user, an owner, which is a class of a user who is in charge of management of the vehicle, and a general, which is a class of another user, are used.
[0020]
By the way, the user identification data notified by the ignition key unit 7 or the keyless entry system 8 is detected by the ignition key unit 7 or the keyless entry system 8 as follows, for example. That is, in the present embodiment, a key prepared for each user and having a remote control key function and a short-range communication function in which identification data of the user who is the key user is stored in advance is used as the key of the automobile. When the user operates the key / remote key, the ignition key unit 7 and the keyless entry system 8 communicate with the key, receive the stored identification data from the key, detect the user identification data, and perform the key operation. / The control unit 10 is notified of the detected identification data together with the event indicating the remote key operation.
[0021]
Hereinafter, the operation of the message processing unit 105 of the control unit 10 will be described.
First, a message table used in the processing of the message processing unit 105 will be described.
As shown in FIG. 3B, a plurality of message records (each row in the figure) registered for each event for displaying a message as a response to the occurrence of the event are registered in the message table. In each message record, a corresponding event, owner message data, driver message data, and an emergency message are registered.
[0022]
The owner message data receives, when a corresponding event occurs, an owner message, which is a message to be notified to the user whose class is the owner, and receives an operation from the user for the user who is the owner after notifying the owner message data. This specifies the owner menu, which is the menu to be displayed. In addition, the driver message data includes a driver message that is a message to be notified to a user whose class is currently not a driver when a corresponding event occurs and a driver that is a user who is not an owner after notifying the driver message. On the other hand, a driver menu, which is a menu displayed to accept an operation from the user, is designated. The urgent message represents a message that is unconditionally notified to the driver at the time when the corresponding event occurs.
[0023]
Here, in each message record, all of the owner message data, the driver message data, and the emergency message need not always be prepared, but only necessary ones may be prepared according to the event.
Here, the owner message data is used to notify the owner of the vehicle of the occurrence of the event, the details of the event, and the detailed countermeasures for the event as a message for vehicle management, such as events that require vehicle inspection to be completed or changes to the on-board equipment settings. For events where it is desirable to do so. In addition, driver message data is provided for general events that notify the driver of event occurrence and countermeasures as a message.Emergency messages are used to promptly notify the driver of the event occurrence and countermeasures, such as vehicle abnormalities, as a message. Be prepared for events that need to be done.
[0024]
Further, the owner message data and the driver message data may not include the menu specification but include only the message specification. Note that the difference between the owner menu and the driver menu of the same message record is that, for example, activation of a process to be performed in response to an event that has occurred is performed by using a menu including an item for automatically accepting an activation operation of the process. An operation accepting item of an operation appropriate to be permitted only to the owner, for example, when displayed and accepted on the display 103, is included only in the owner menu and not in the driver menu.
[0025]
For example, in the case of a message record corresponding to an error occurrence event of an in-vehicle AV device, the owner menu specified by the owner message data may be a menu that accepts a change in the settings of the in-vehicle AV device that caused the error from the driver. The driver menu specified by the message data is, for example, a menu that accepts only the acknowledgment of the message.
[0026]
Now, using such a message table, the message processing unit 105 performs the message processing shown in FIG.
As shown in the figure, in this process, first, the occurrence of unreported message data in the memory 106 (step 402) and the transfer of an event from the event analysis unit 102 (step 404) are monitored.
Then, when the event is transferred from the event analysis unit 102 (step 404), a message record corresponding to the transferred event is obtained from the message table (step 406), and an emergency message is registered in the obtained message record. It is checked whether or not it is present (step 508), and if it is registered, an urgent message is displayed by requesting the input / output processing unit 101 to display an urgent message (step 420). The input / output processing unit 101 controls the display control unit to display the message requested to be displayed on the display device 11.
[0027]
On the other hand, if no emergency message is registered in the acquired message record (step 408), it is checked whether the class of the user who is the current driver is the owner based on the current user data in the memory 106 (step 410). . Then, if the owner is the owner, it is checked whether or not the owner message data is registered in the acquired message record (step 412). If not, the process proceeds to step 426.
[0028]
On the other hand, if the owner message data has been registered (step 412), the owner message included in the registered owner message data is displayed (step 414). Then, when the owner message data includes the owner menu (step 416), the device control unit 103 that displays the owner menu, receives a user operation on the menu, and performs a process according to the received user operation is executed. The owner menu process is started (step 418), and the process returns to step 402. On the other hand, if the owner message data does not include the owner menu (step 416), the process directly returns to step 402.
[0029]
On the other hand, when it is determined in step 410 that the class of the user is not the owner, it is first checked whether or not the owner message data is registered in the acquired message record (step 422). The identification of the acquired data record is stored in the memory 106 as the notified message data (step 424), and the process proceeds to step 426. On the other hand, if the owner message data is not registered in the acquired message record (step 422), the process directly proceeds to step 426. After storing the notified message data in step 424, the occurrence of unreported message data is detected in step 402.
[0030]
In step 426, it is checked whether or not driver message data is registered in the obtained message record. If registered, the driver message included in the registered driver message data is displayed (step 428). If the driver message data includes a driver menu (step 430), the device control unit 103 that displays the driver menu, receives a user operation on the menu, and performs a process according to the received user operation is performed. The driver menu process is started (step 432), and the process returns to step 402. On the other hand, when the driver message data does not include the driver menu (step 430), the process returns to step 402 as it is.
[0031]
If the occurrence of unreported message data is detected in step 402, it is checked from the current user data in the memory 106 whether the class of the user who is the current driver is the owner (step 434). If not, the process returns to monitoring the occurrence of unreported message data in the memory 106 (step 402) and the transfer of the event from the event analysis unit 102 (step 404). On the other hand, if the class of the user is the owner (step 434), a message record in which the identification is stored in the unreported message data is obtained from the message table (step 436), and the unreported message data is deleted. Then, the process proceeds to step 414, where the owner message is displayed and the owner menu is processed (steps 416 and 418) based on the acquired message record as described above.
[0032]
The embodiments of the present invention have been described above.
As described above, according to the present embodiment, it is possible to notify a driver of a message corresponding to a class as a user of the driver. Therefore, when the owner class user is the driver, a user other than the owner class user is the driver while notifying the user of a message including detailed information on the event that has occurred. Sometimes, a message about an event that has been prepared for the user in the message table as a driver message and that has generated information that is not necessary for non-owner class users or that excludes information that is not appropriate to be presented to non-owner class users is excluded. Or be notified.
[0033]
Further, according to the present embodiment, for a message registered as an owner message in the message table in advance, even if the driver when the event corresponding to the message occurs is not a user of the owner class, the owner class Is displayed on the display device 11 when the user becomes a driver, the user of the owner class is always notified.
[0034]
【The invention's effect】
As described above, according to the present invention, information to be notified to a user regarding a situation related to a vehicle can be notified to a user appropriate as a notification destination of the information in a form appropriate for the user.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of an in-vehicle information system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating a configuration of a control unit according to the embodiment of the present invention.
FIG. 3 is a diagram showing a table stored in a memory of a control unit according to the embodiment of the present invention.
FIG. 4 is a flowchart illustrating a procedure of a process performed by a message processing unit according to the embodiment of the present invention.
[Explanation of symbols]
REFERENCE SIGNS LIST 1 engine system 2 transmission system 3 suspension system 4 brake system 5 door lock system 6 electronic control unit 7 ignition key unit 8 keyless entry system 9 input device DESCRIPTION OF SYMBOLS 10 ... Control unit, 11 ... Display device, 12 ... Display control device, 13 ... Accessory equipment, 14 ... Air conditioner, 15 ... Sea position actuator, 16 ... Control bus, 17 ... Display signal line, 101 ... I / O processing unit, 102: an event analysis unit; 103: a device control unit; 104: a user identification unit; 105: a message processing unit;

Claims (4)

An in-vehicle information system mounted on an automobile, which notifies a driver of a message corresponding to an event that has occurred,
For each of a plurality of users, a user class management table in which the class of the user is registered, a message table for defining a message for each event to be notified to the user for each class, and storage means for storing
User identification means for identifying a user who is currently a driver, and extracting a class registered in the user class management table of the identified user;
An in-vehicle information system comprising: a message notifying unit that notifies a driver of a message corresponding to an event that has occurred, the message being specified for the class extracted by the user identifying unit in the message table when the event occurs. The in-vehicle information system according to claim 1,
The message notification unit may be configured such that, when an event occurs, the class extracted by the user identification unit is not a predetermined specific class, and a message for the generated event is specified for the specific class in the message table. Wherein the message is stored as an unnotified message, and when the user identification means extracts the specific class, the message stored as the unnotified message is notified to a driver. . A message notification method for notifying a driver of a message according to an event that has occurred in an in-vehicle information system mounted on an automobile,
Identifying a user who is currently a driver and extracting a class given in advance to the identified user;
A method of notifying a driver of an event that has occurred and a message defined in advance for the extracted class in response to the occurrence of the event to a driver. A computer program read and executed by a computer mounted on an automobile,
To the computer,
Identifying a user who is currently a driver and extracting a class given in advance to the identified user;
In response to occurrence of a predetermined event, the step of notifying a driver of an event that has occurred and a message defined in advance for an extracted class to a driver.

Images