JP2007090951A - In-vehicle unit - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an in-vehicle unit with its application programs capable of reliably acquiring information from external apparatuses. <P>SOLUTION: The in-vehicle unit includes such programs as a navigation application 10, driving skill evaluation application 11 and a safe driving information supply application 12, as well as a platform 13 including a navigation information platform manager. When the navigation information platform manager 13a and a vehicle information platform manager 13b receive requests for information from such programs as the navigation application 10, the driving skill evaluation application 11 and the safe driving information supply application12, those platform managers accept the request and determine the requested information. These platform managers accommodate the requests from the application programs by calling API in response to the results of the determinations and acquiring information from a car navigation system 15 or a vehicle control ECU 18. Thus, each application program can acquire information without need of intention of the presence of the car navigation system 15 or the vehicle control ECU 18. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an in-vehicle device equipped with a plurality of applications for processing information acquired from an external device.

For example, for safe driving of automobiles, it has been studied to grasp the driving skills of the driver and to perform warnings and controls corresponding to the driving skills. In Patent Document 1, the driver's driving is supported in time series based on the current situation where the vehicle is placed with respect to the driver and the situation where the vehicle is placed in the future. It describes that the content of assistance to the driver is reconfigured according to the change in the skill.
JP 2004-334283 A

However, the thing of the patent document 1 has the following subjects.
Currently, in-vehicle ECUs (electronic control units) for collecting driving skills are manufactured and sold by different manufacturers, and are installed at vehicle manufacturers, dealers, shops, etc. It is necessary to collect and analyze data from ECUs of various manufacturers by providing a conventional in-vehicle travel control ECU with a memory and analysis software, but the processing capacity of individual ECUs is limited, Since the memory is not installed, in order to grasp the driving skill, it is desirable to install hardware and an application for creating driving skill data in an in-vehicle device separate from the on-vehicle travel control ECU.

Here, the application for creating driving skill data includes user operation (brake, steering, accelerator, operation switch, etc.) and travel control ECU (brake system, engine / motor control system, suspension system) and vehicle running state. It is necessary to reliably collect data from sensors such as a G sensor that measures the speed, a speed sensor, and a GPS that measures the position without time delay.
However, the plurality of ECUs mounted on the vehicle are usually different from each other, and there is a possibility that the application for creating the driving skill data cannot access these devices and acquire information.
This invention is made | formed in view of the said situation, and it is providing the vehicle equipment which an application can acquire information reliably from an external apparatus.

  According to the invention of claim 1, when an application requests information acquisition from an external device, the platform acquires the information by accessing the external device through a corresponding API, and issues a request to acquire the information. Deliver to the application. Thereby, the application can acquire desired information from the external device without being aware of the existence of the connected external device.

  According to the invention of claim 2, when an external device is connected, the platform is set so that the external device can be accessed. Thus, the application can acquire information from the connected external device through the platform.

  According to the invention of claim 3, when a plurality of applications simultaneously request information acquisition, the platform controls access to the external device so as to reduce the burden on the external device. As a result, the application can efficiently access the external device.

  An embodiment of the present invention will be described below with reference to the drawings. The in-vehicle device of this embodiment is equipped with a driving skill evaluation system, a safe driving information provision system, and the like in addition to the route guidance system. In the following, description of the safe driving information providing system is omitted for the sake of simplicity.

  FIG. 2 is a block diagram showing a hardware configuration when the route guidance system is implemented. FIG. 3 is a block diagram showing a hardware configuration when the driving technology evaluation system is implemented. As can be seen from FIGS. 2 and 3, the communication controller 1, the position measuring device 2, the display 3, the audio 4, the drawing system 5, the map database (hereinafter referred to as DB) 6, the camera system 7, the HMI (Human Machine). Since the interface controller 8 has a hardware configuration that is duplicated in each system, in this in-vehicle device, those duplicated devices are constituted by the same hardware module, and the functions of the navigation data processing system are included in the hardware module. By installing an application to control and an application to control the function of the operation data processing system, the hardware configuration is made more efficient.

  FIG. 1 schematically shows a block diagram of a software configuration when a route guidance system and an operation data processing system are configured in the same hardware module in an in-vehicle device. In FIG. 1, an in-vehicle device 9 includes a route guidance navigation application (hereinafter referred to as a navigation application) 10, a driving technology evaluation application (hereinafter referred to as a driving technology evaluation application) 11, and a safe driving information provision application (hereinafter referred to as an application of each system). A manager layer (hereinafter referred to as the platform) that categorizes requests from each application (hereinafter referred to as “app”) and returns a response corresponding to the corresponding request under the three software called “safe driving information providing application” 12. 13) was constructed. In FIG. 1, the platform 13 includes various managers such as an HMI platform manager 13c, an additional device manager 13d, and a communication control manager 13e in addition to the navigation information platform manager 13a and the vehicle information platform manager 13b for handling the navigation information. It is configured.

  Each of the managers 13a to 13e manages an API (Application Program Interface) group for processing a specialized field request. In other words, when a request is made from an application, the corresponding manager receives the request, activates a required API from the API library provided for each manager, performs an operation according to the request, and responds to the request. Create an answer. For example, when a request is received from the application for the current position, the navigation information platform manager 13a receives the request, and the navigation information platform manager 13a acquires the position information using the position information acquisition API and sends it to the application. return.

  As an API library, a navigation information collection API library 14 is provided corresponding to the navigation information platform manager 13a. The navigation information collection API library 14 includes a position information acquisition API 14a, a curve angle acquisition API 14b, an intersection angle acquisition API 14c, a vehicle speed acquisition API 14d, an intersection approach information acquisition API 14e, and a curve approach information acquisition API 14f. The information from 15 (corresponding to an external device) is acquired by the control of the communication control ECU 16.

  A vehicle operation information API library 17 is provided corresponding to the vehicle information platform manager 13b. The vehicle operation information API library 17 includes a steering angle API 17a, a vehicle behavior sensor API 17b, a brake operation information API 17c, and an accelerator opening API 17d, and performs communication control of information from a vehicle control ECU (corresponding to an external device) 18. It is acquired under the control of the ECU 16.

On the other hand, the HMI platform manager 13c executes switch operation, display display, voice input from a microphone, audio control, and the like through the switch operation API 19a, the display API 19b, the voice generation API 19c, and the voice collection API 19d.
When the additional device 20 is mounted on the vehicle, the additional device manager 13d and the communication control manager 13e communicate with the additional device 20, acquire a program necessary for the additional device 20 through communication, and use the device. It can be so. In addition, when an additional function has a function corresponding to each platform manager, a new API is added to each function.

  In this case, if the platform 13 is set to use an API capable of obtaining device data with high positional accuracy, the function of the application can be improved almost simultaneously with the addition of a high-performance device. For example, when normal GPS is changed to RTKGPS, the position information is changed to information obtained by a new position information acquisition API.

  In addition, by adding priority data invisible to the application to the location information acquisition API, even if a high-precision device cannot be used depending on the location, the platform manager can use the medium-precision device data that can be used at that time. Can be returned, and the problem that the application stops can be avoided.

FIG. 4 is a block diagram illustrating a software configuration related to the driving skill evaluation application 11 among the applications installed in the in-vehicle device 9. In FIG. 4, the driving skill evaluation application 11 acquires navigation-related information from the car navigation device 15 and vehicle information from the vehicle control ECU 18 using each API library provided by the platform 13. That is, when acquiring the navigation information, the driving skill evaluation application 11 requests that from the navigation information platform manager 13a, and when acquiring the vehicle information, requests the vehicle information platform manager 13b. .
Then, the driving skill evaluation application 11 analyzes the acquired navigation information and vehicle information and evaluates the driving skill of the driver.

  FIG. 5 is a diagram for explaining a driving skill evaluation method by the driving skill evaluation application 11. As shown in FIG. 5, at the time of entering the curve, the ideal steering angle, accelerator opening, brake operation, vehicle according to the curve approach speed is calculated from the curve approach information, curve angle information, and vehicle speed information among the navigation information. The behavior is calculated and compared with the acquired vehicle information, and the difference is determined as driving evaluation.

Also, when approaching an intersection, the ideal steering angle, accelerator opening, brake operation, and vehicle behavior corresponding to the intersection approach speed are calculated and acquired from the intersection approach information, intersection angle information, and vehicle speed information in the navigation information. Compared to the vehicle information, the difference is regarded as driving evaluation.
And a driving | operation evaluation result table | surface is created based on the above driving | operation evaluation.

Now, a specific method in which the driving skill evaluation application 11 installed in the in-vehicle device 9 evaluates the driving skill of the driver will be described with reference to FIG.
[Step S1] Setting of Driving Skill Course In order to evaluate the driving skill of the driver, first, the driving skill course is set. The driving skill course may be arbitrarily selected by the driver, or may be automatically set by the driving data processing system.

When the driver arbitrarily selects, an evaluation start point, an evaluation end point, and a travel route are set for the car navigation device 15, and the vehicle travels according to the set route.
When the driving skill evaluation application 11 sets the driving skill course, the driving skill evaluation application 11 acquires the measurement of the current position from the car navigation device 15 and calls the route calculation result of the car navigation device 15 to reach the destination. Refer to the route calculation result. That is, the route calculation result of the car navigation device 15 is called.

  Next, a place suitable for driving skill measurement is searched from the map DB in the route called from the car navigation device 15. In order to search for a place where the driving skill is required on the route, search is made from the map DB for route shape data (bending, climbing, slipping, speed regulation), information on presence / absence of obstacles, and the like. Each course is given an evaluation point indicating the degree of difficulty depending on the shape of the route and the presence or absence of obstacles. That is, when the route shape is complicated or when it is difficult to travel along the route at a constant speed, the evaluation point of the difficulty level increases.

  The driving data processing system refers to the number of vehicle operations (driving times) by the driver. When it is confirmed that the driver is not used to driving the vehicle (less than the set number of driving times), a simple evaluation course can be selected. Or you may enable it to select automatically. Usually, the driving data processing system performs route selection according to the number of driving times of the driver. That is, when the driver is an immature person, driving is difficult even on a normal route, and correct evaluation becomes difficult.

[Step S2] Calculation of Recommended Driving Operation Pattern Next, the driving skill evaluation application 11 calculates a recommended driving operation pattern. The recommended pattern is to calculate and store an operation for good driving assuming safe driving.
The driving data processing system calculates a driving operation recommendation pattern when driving on the route selected in step S1 described above in safe driving. In other words, the vehicle speed at the starting point of the evaluation course, the steering operation pattern according to the road shape on the way, the use of the brake (position, frequency, acceleration during braking) are estimated based on the travel pattern database, Record the estimation results. In this case, since the operation of each operation device and its running result differ depending on the size and weight of the vehicle, the recommended pattern is registered using the values for the size and weight registered in the driving data processing system for each vehicle. Perform the calculation.

[Step S3] Notification of Entering Driving Skill Evaluation Course Next, the driving skill evaluation application 11 notifies the driver of entering the driving skill evaluation course before entering the driving skill evaluation course. That is, the driving data processing system measures the current position of the vehicle, and when the vehicle is about to enter the driving skill evaluation course, the driving data processing system transmits the fact of the driver using the display and audio. At this time, the countdown may be performed by voice or display.

[Step S4] Guidance of Start of Driving Skill Evaluation The driving data processing system notifies the driver that the driving skill is being evaluated using a display and audio. In this case, according to a driver | operator, you may make it ease tension | tensile_strength, or may flow BGM etc. which raise tension conversely. Operation of the steering wheel, steering, brake, operation switch, and the like in the driving skill course and the vehicle position are measured (the vehicle position uses a centerline photographed image or high-precision GPS (RTKGPS)) and stored in the memory.

[Step S5] Driving skill evaluation, data measurement, recording The position of the vehicle, the operation of the driver, the time, the movement of the vehicle (vibration, speed, acceleration) are measured, and the result is recorded. When it is determined that the driver is driving dangerously in the driving skill evaluation course, an alarm is issued with an audio function or the like.

[Step S6] Guidance of Completion of Driving Skill Evaluation The driving data processing system measures the position using the position measuring device, and when the vehicle reaches the driving skill evaluation completion point, the driver indicates that the driving skill evaluation is completed. Informs using a display and audio. Stop data recording and save as an evaluation data file.
The driving data processing system compares the driving skill evaluation result with the driving operation recommendation pattern calculated in step S2, and quantitatively calculates at what position the driving operation recommendation pattern differs from the driving operation recommendation pattern.

[Step S7] Display of Driving Skill Results When the driver issues a driving skill confirmation request, the driving skill results are displayed.
Hereinafter, the information delivery operation of the driving skill evaluation application 11, the navigation information platform manager 13a, and the vehicle information platform manager 13b will be described.

  FIG. 7 is a flowchart showing the operation of the driving skill evaluation application 11. In FIG. 7, the driving skill evaluation application 11 issues a request for curve / intersection approach information to the navigation information platform manager 13a (C1). If these requests are issued once, information will come up from the navigation information platform manager 13a every time a curve / intersection approaches.

  When approach information is acquired from the navigation information platform manager 13a, it is first determined whether it is a curve or an intersection (C2). If it is a curve (C2: curve), a curve angle information request is sent to the navigation information platform manager 13a (C3), and the curve angle information is acquired (C4). On the other hand, if it is an intersection (C2: intersection), an intersection angle information request is sent to the navigation information platform manager 13a (C8), and intersection angle information is acquired (C9).

  Next, a vehicle speed request is issued to the navigation information platform manager 13a (C5), and the vehicle speed is acquired (C6). At the same time, vehicle information (steering angle information, accelerator opening information, brake operation information, vehicle behavior information) is requested from the vehicle information platform manager 13b (C10) and acquired (C11).

Finally, from the information (curve angle information or intersection angle information, speed information) acquired from the navigation information platform manager 13a, the ideal vehicle data (steering angle information, accelerator opening information, brake operation information) for the curve (or intersection) is obtained. , Vehicle behavior information) is generated (C7). Then, the generated data is compared with the actually acquired vehicle data (C12), and the driving skill of the driver is evaluated (C13).
The series of operations described above are executed each time the vehicle enters a curve or an intersection.

FIG. 8 is a flowchart showing the operation of the navigation information platform manager 13a. In FIG. 8, the navigation application 10, the driving skill evaluation application 11, and the safe driving information provision application 12 installed in the in-vehicle device 9 request an information request from the platform 13 at a unique timing. The navigation information platform manager 13a receives an information request from the application (A1), and determines request information from the application (A2). As a result of the request information determination, when the request from the application is “curve approach information request” (A3: YES), the curve approach information acquisition API 14f is called (A10), and when it is “intersection approach information request” (A4: (Yes), the intersection approach information acquisition API 14e is called (A11). When “curve angle request” is made (A5: YES), the curve angle acquisition API is called (A12), and when “intersection angle request” is made (A6) : YES), the intersection angle acquisition API 14 c is called (A 13), and when “vehicle speed information request” is made (A 7: YES), the vehicle speed acquisition API 14 d is called (A 14). For other requests (A7: NO), the corresponding API is called (A8).
As described above, when information is acquired as a result of requesting information to the car navigation apparatus 15 through the API for which various information requests are requested (A9), the information is handed over to the application that requested the acquired information (A9). A15).

  FIG. 9 is a flowchart showing the operation of the vehicle information platform manager 13b. As shown in FIG. 9, when the vehicle information platform manager 13b receives an information request from each application (B1), similarly to the navigation information platform manager 13a described above, the vehicle information platform manager 13b determines the request information (B2), Information is acquired from the vehicle control ECU 18 by executing a predetermined API call based on the determination result (B8), and the acquired information is delivered to the requested application (B13).

FIG. 10 shows an example when the vehicle enters the right curve. In FIG. 10, when the vehicle enters the curve, ideal data of the vehicle is created prior to entering the curve. In this example, it is ideal that the vehicle travels along a travel locus indicated by a one-dot chain line, but the actual travel locus indicates that it is a chain line, and the evaluation is based on the amount of deviation between both travel trajectories. In addition, the operation by the driver is determined at each evaluation point. That is, when the vehicle is positioned at the first evaluation point PO1 shown in FIG. 10 based on the navigation information, it is determined whether or not the horn is sounded while keeping the speed limit 30Km. When the vehicle is positioned at the next point PO2, the speed limit It is determined that 40 km is protected and does not protrude into the oncoming lane, and it is determined whether the accelerator is opened to climb the hill when it is positioned at the next PO3. Based on such determination, a point which is a driving evaluation result is calculated and the point is displayed.
Therefore, the driver can know his / her driving skill level based on the displayed points.

According to such an embodiment, the in-vehicle device 9 is provided with the platform 13, and a plurality of applications installed in the in-vehicle device 9 request information acquisition from an external device such as the car navigation device 15 or the vehicle control ECU 18. In this case, since predetermined information is acquired from the external device through the API library of the platform 13 and delivered to the application, the application can acquire desired information without being aware of the connection of the external device.
In addition, when a new external device is connected to the vehicle-mounted device 9, the platform 13 manages the connection with the external device, so that the application can request from the external device without being aware of the connection state of the external device. Information can be acquired.

  In addition, since the platform 13 collectively controls information acquisition for external devices, even if a plurality of applications issues a request for information acquisition to the platform at the same time, the platform 13 responds to a request from the application. On the other hand, access can be controlled so as not to apply a load to an external device, and information can be efficiently acquired from a predetermined device and information can be acquired without impairing real-time performance.

The present invention is not limited to the above embodiment, but can be modified or expanded as follows.
The platform 13 may be mounted on the car navigation device 15 and the navigation information may be acquired from the car navigation software.

The figure which shows the whole software structure in one Example of this invention. Block diagram showing the hardware configuration of the route guidance system Block diagram showing the hardware configuration of the driving technology evaluation system Block diagram showing software configuration for driving technology evaluation app The figure for explaining the evaluation method of the driving skill with the driving skill evaluation application Flow chart showing the evaluation procedure of the driving technology evaluation app Flow chart showing operation of driving technology evaluation app Flow chart showing the operation of the navigation information platform manager Flow chart showing operation of vehicle information platform manager Illustration for explaining driving skill evaluation

Explanation of symbols

  In the drawing, 9 is an in-vehicle device, 10 is a route guidance navigation application, 11 is a driving skill evaluation application, 12 is a safe driving information providing application, 13 is a platform, 14 is a navigation information collection API library, and 15 is a car navigation device (external device). ), 17 is a vehicle operation information API library, and 18 is a vehicle control ECU (external device).

Claims (3)

Multiple applications that process information obtained from external devices,
A platform having an API library for accessing the external device and acquiring information;
When the application requests acquisition of information from the external device, the platform acquires information by accessing the external device through a corresponding API and delivers the information to the application.   The in-vehicle device according to claim 1, wherein the platform is set so that the external device can be accessed when the external device is connected. 3. The platform according to claim 1, wherein the platform controls access to the external device so as to reduce a burden on the external device when acquisition of information is simultaneously requested from the plurality of applications. In-vehicle device.

Images