Information communication system for vehicle

Abstract

To provide an information communication system for a vehicle capable of appropriately disclosing abnormality information communicated between the vehicle and a control server to a user.SOLUTION: The vehicular information communication system includes the in-vehicle device 15 having the vehicular communication device 26c using the short-range wireless communication standard and CP _ ECU21, the mobile communication terminals 6 having the first terminal communication device 31a using the short-range wireless communication standard, the second terminal communication device 31b using the non-short-range wireless communication standard, the display 31c, and the terminal communication device ECU30, and the control server 7 having the server communication device 36a using the non-short-range wireless communication standard. CP _ ECU21 transmits the abnormality information only to the portable communication terminals 6 paired with the in-vehicle device 15, and CP _ ECU30 displays information extracted from the received abnormality information on the display unit 31c and transmits the abnormality information to the server communication unit 36a.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a vehicle information communication system using a mobile communication terminal. [Background technology]

[0002] In recent years, information and communication systems have been put into practical use that communicate information between an on-board device and an external control server or the like when an abnormality occurs due to a vehicle breakdown or the like. For example, Patent Document 1 discloses a technology in which, when a vehicle abnormality is detected, a first communication unit mounted on the vehicle is used to execute communication via a base station using a first communication method, and the abnormality information is transmitted to a predetermined server. Patent Document 1 also discloses a technology in which, when communication using the first communication unit is not possible, a second communication unit that enables direct communication between terminals is used to request a nearby terminal to transmit the abnormality information to the server on its behalf. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-24363 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the technology disclosed in the above-mentioned Patent Document 1 is basically for transmitting abnormality information to a control server etc. using the first communication unit. Therefore, when an abnormality occurs in the vehicle, a user such as a driver can only obtain limited information displayed on an instrument panel etc., and it is difficult to obtain specific abnormality information.

[0005] Furthermore, the technology disclosed in Patent Document 1 uses an unspecified terminal to send anomaly information by proxy when communication using the first communication unit is not possible. Therefore, with the technology disclosed in Patent Document 1, there is a risk that it may be difficult to transmit information such as analysis results of the anomaly information from the control server to the user.

[0006] An object of the present invention is to provide a vehicle information communication system that can appropriately disclose abnormality information communicated between a vehicle and a control server to a user. [Means for solving the problem]

[0007] A vehicle information communication system according to one embodiment of the present invention comprises an in-vehicle device having a vehicle communication means for communicating using a first communication standard that does not involve a base station and a vehicle control means, a mobile communication terminal having a first terminal communication means for communicating using the first communication standard, a second terminal communication means for communicating using a second communication standard that involves the base station, a display means for displaying information to a user, and a terminal control means, and a control server having a server communication means for communicating using the second communication standard, wherein when a vehicle abnormality is detected, the vehicle control means transmits abnormality information of the vehicle from the vehicle communication means only to the first terminal communication means of the mobile communication terminal that is paired with the in-vehicle device, and when the terminal control means receives the abnormality information from the in-vehicle device, it displays information extracted from the abnormality information on the display means and transmits the abnormality information from the second terminal communication means to the server communication means.

[0008] In addition, another aspect of the present invention provides a vehicle information communication system comprising an in-vehicle device having a vehicle communication device that communicates using a first communication standard that does not involve a base station and a vehicle processor, a mobile communication terminal having a first terminal communication device that communicates using the first communication standard, a second terminal communication device that communicates using a second communication standard that involves the base station, a display device that displays information to a user, and the terminal processor, and a control server having a server communication device that communicates using the second communication standard, wherein when a vehicle abnormality is detected, the vehicle processor transmits abnormality information of the vehicle from the vehicle communication device only to the first terminal communication device of the mobile communication terminal that is paired with the in-vehicle device, and when the terminal processor receives the abnormality information from the in-vehicle device, it displays information extracted from the abnormality information on the display device and transmits the abnormality information from the second terminal communication device to the server communication device. [Effects of the Invention]

[0009] According to the vehicle information communication system of the present invention, abnormality information communicated between the vehicle and the control server can be appropriately disclosed to the user. [Brief explanation of the drawings]

[0010] [Figure 1] Schematic diagram of a vehicle information and communication system [Figure 2] A flowchart showing an abnormality response control routine in an on-board device when an abnormality occurs in the vehicle. [Figure 3] A flowchart showing an abnormality response control routine in a mobile communication terminal when a vehicle abnormality occurs. [Figure 4] A flowchart showing an abnormality response control routine in the control server when a vehicle abnormality occurs. [Figure 5] FIG. 10 is an explanatory diagram illustrating an example of a transition state regarding a response to an abnormality in a vehicle; [Figure 6] FIG. 10 is an explanatory diagram showing a display example on a display device of a mobile communication terminal; [Figure 7] FIG. 10 is an explanatory diagram showing a display example on a display device of a mobile communication terminal; DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of one aspect of the present invention will be described in detail below with reference to the drawings. Note that in the drawings used in the following description, each component is shown at a different scale so that it can be recognized. Therefore, the present invention is not limited to the number of components, the shapes of the components, the size ratios of the components, and the relative positional relationships of the components shown in these drawings.

[0012] As shown in FIG. 1, the vehicle information communication system 1 includes, for example, an in-vehicle device 15 provided in a driving assistance device 5, a mobile communication terminal 6, and a control server .

[0013] The driving assistance device 5 is mounted on a vehicle (host vehicle) M. The driving assistance device 5 has a camera unit 10 fixed to the center of the upper front part of the cabin of the host vehicle M, for example.

[0014] The camera unit 10 includes, for example, a stereo camera 11, an image processing unit (IPU) 12, an image recognition unit (image recognition_ECU) 13, and a driving control unit (driving_ECU) 14.

[0015] The stereo camera 11 includes a main camera 11a and a sub-camera 11b. The main camera 11a and the sub-camera 11b capture stereoscopic images of information about the driving environment in front of the vehicle from different viewpoints at imaging cycles synchronized with each other.

[0016] The IPU 12 performs predetermined image processing on the driving environment information captured by the stereo camera 11. For example, the IPU 12 obtains distance information from the positional deviation of corresponding edges on the left and right images. As a result, the IPU 12 generates image information including distance information (distance image information).

[0017] The image recognition_ECU 13 recognizes driving environment information of the host vehicle M based on the distance image information and the like input from the IPU 12. For example, the image recognition_ECU 13 performs predetermined pattern matching on the distance image information. As a result, the image recognition_ECU 13 recognizes lane markings on the road. Furthermore, the image recognition_ECU 13 recognizes various three-dimensional objects extending along the road, such as guardrails, curbs, median strips, nearby vehicles, and pedestrians.

[0018] The traveling_ECU 14 is a control unit for controlling the driving assistance device 5 in an integrated manner.

[0019] A locator unit 20 and the like are connected as various sensors to the travel_ECU 14. In addition, various control units, such as a cockpit control unit (CP_ECU) 21, an engine control unit (E / G_ECU) 22, a transmission control unit (T / M_ECU) 23, a brake control unit (BK_ECU) 24, and a power steering control unit (PS_ECU) 25, are connected to the travel_ECU 14 via an in-vehicle communication line such as a CAN (Controller Area Network).

[0020] Locator unit 20 includes a GNSS sensor 20a and a high-precision road map database (road map DB) 20b.

[0021] The GNSS sensor 20a receives positioning signals transmitted from a plurality of positioning satellites, thereby determining the position (latitude, longitude, altitude, etc.) of the host vehicle M.

[0022] The road map DB 20b is a large-capacity storage medium such as an HDD. High-precision road map information (dynamic map) is stored in this road map DB 20b. The road map information includes, for example, lane data required for autonomous driving, such as lane width data, lane center position coordinate data, lane travel azimuth data, and speed limit data. The lane data is stored at intervals of several meters for each lane on the road map. Furthermore, the road map DB 20b also stores, for example, traffic light data as data accompanying the lane data.

[0023] For example, based on a request signal from the driving_ECU 14, the road map DB 20b outputs road map information of a set range based on the vehicle position measured by the GNSS sensor 20a to the driving_ECU 14 as driving environment information.

[0024] The CP_ECU 21 is connected to, for example, a display device 26a and a speaker 26b as a human-machine interface (HMI) arranged around the driver's seat.

[0025] When the CP_ECU 21 receives various information related to driving assistance control and the like from the traveling_ECU 14, it notifies the driver of the received information as appropriate. Such notification is performed by displaying the information using the display device 26a and outputting audio using the speaker 26b.

[0026] The E / G_ECU 22 performs drive control on a throttle actuator (not shown) and the like based on control signals from the travel_ECU 14 or detection signals from various sensors. As a result, the E / G_ECU 22 adjusts the amount of intake air into the engine to generate a desired engine output. The E / G_ECU 22 also outputs signals such as the accelerator opening detected by the various sensors to the travel_ECU 14. Furthermore, the E / G_ECU 22 performs abnormality diagnosis (fault diagnosis) of the engine based on the signals detected by the various sensors.

[0027] The T / M_ECU 23 performs hydraulic control for a hydraulic control circuit (not shown) and the like based on the engine torque signal estimated by the E / G_ECU 22, detection signals from various sensors, and the like. As a result, the T / M_ECU 23 operates friction engagement elements, pulleys, and the like provided in the automatic transmission to shift the engine output at a desired gear ratio. The T / M_ECU 23 also outputs signals such as a shift position detected by various sensors to the travel_ECU 14. Furthermore, the T / M_ECU 23 performs abnormality diagnosis (fault diagnosis) of the automatic transmission based on the signals detected by the various sensors, and the like.

[0028] The BK_ECU 24 performs drive control on a brake actuator (not shown) and the like based on control signals from the travel_ECU 14 or detection signals from various sensors. As a result, the BK_ECU 24 appropriately generates braking force on each wheel to perform forced braking control, yaw rate control, and the like on the host vehicle M. The BK_ECU 24 also outputs signals of the brake operation state, yaw rate, longitudinal acceleration, vehicle speed (host vehicle speed), and the like detected by various sensors to the travel_ECU 14. Furthermore, the BK_ECU 24 performs abnormality diagnosis (fault diagnosis) of the braking system based on signals detected by the various sensors.

[0029] The PS_ECU 25 performs drive control for an electric power steering motor (not shown) and the like based on control signals from the travel_ECU 14 or detection signals from various sensors. As a result, the PS_ECU 25 generates a steering torque for the steering mechanism. The PS_ECU 25 also outputs signals of the steering torque, steering angle, and the like detected by the various sensors to the travel_ECU 14. Furthermore, the PS_ECU 25 performs abnormality diagnosis (fault diagnosis) of the steering system based on signals detected by the various sensors.

[0030] The driving_ECU 14 performs driving assistance control for the vehicle M based on driving information of the vehicle M input from various on-board sensors, and driving environment information input from the image recognition_ECU 13 and the locator unit 20, etc.

[0031] During driving assistance control, the traveling_ECU 14 calculates, for example, control signals for each of the ECUs 21 to 25. As a result, the traveling_ECU 14 realizes driving assistance control that appropriately combines adaptive cruise control (ACC), active lane keep centering control (ALKC), active lane keep bouncing control (ALKB), and the like.

[0032] In the driving assistance device 5, the CP_ECU 21 is further connected to a vehicle communication device 26c as a vehicle communication means.

[0033] The vehicular communicator 26c is a communicator for performing communication using a short-range wireless communication standard such as BLUETOOTH (registered trademark). That is, the vehicular communicator 26c is capable of performing wireless communication using a communication standard (first communication standard) that does not involve a base station.

[0034] The vehicle communication device 26c, together with the CP_ECU 21 and the like, constitutes the in-vehicle device 15. The in-vehicle device 15 is a device for performing information communication with the control server 7 and the like when an abnormality occurs in the vehicle M or the like.

[0035] When functioning as the on-vehicle device 15, the CP_ECU 21 corresponds to a specific example of a vehicle control means (vehicle processor). That is, the CP_ECU 21 collects the results of abnormality diagnosis performed by each of the ECUs 22 to 25, etc. When the collected abnormality diagnosis results include abnormality information of the host vehicle M, the CP_ECU 21 records the abnormality information. Furthermore, the CP_ECU 21 collects information accompanying the abnormality information from the image recognition_ECU 13, the locator unit 20, and each of the ECUs 22 to 25, etc.

[0036] The CP_ECU 21 displays the acquired abnormality information by using an indicator display or the like on the display device 26a.

[0037] Here, the abnormality information supplied from each of the ECUs 22 to 25 includes an error code that is assigned in advance depending on the state of the abnormality, etc. The accompanying information collected by the CP_ECU 21 includes, for example, the total travel distance of the vehicle M when the abnormality occurred, the date, time, and location when the abnormality occurred, the system startup time of the vehicle M when the abnormality occurred, information on the traveling environment when the abnormality occurred, log information on the vehicle speed until the abnormality occurred, log information on the steering angle until the abnormality occurred, and log information on the brake operation until the abnormality occurred.

[0038] Furthermore, the CP_ECU 21 communicates with the mobile communication terminal 6 using the vehicle communication device 26c. This enables the vehicle communication device 26c to transmit the abnormality information and associated information acquired by the CP_ECU 21 to the mobile communication terminal 6. In this case, the CP_ECU 21 permits the vehicle communication device 26c to communicate only with the mobile communication terminal 6 that is coupled with the in-vehicle device 15.

[0039] The mobile communication terminal 6 is configured by, for example, a smartphone, a tablet terminal, a wearable terminal, a mobile phone terminal, etc. The mobile communication terminal 6 has a terminal control unit (terminal_ECU) 30 as a terminal control means (terminal processor).

[0040] The terminal control unit 30 is connected to, for example, a first terminal communicator 31a as a first terminal communication means, a second terminal communicator 31b as a second terminal communication means, and a display device 31c as a display means.

[0041] The first terminal communicator 31a is a communicator for performing communication using a short-range wireless communication standard such as BLUETOOTH (registered trademark). That is, the vehicle communicator 26c is capable of performing wireless communication using a communication standard (first communication standard) that does not involve a base station.

[0042] The second terminal communicator 31b is a communicator for performing communication using a non-short-range wireless communication standard. That is, the second terminal communicator 31b is capable of performing wireless communication using a communication standard (second communication standard) that uses the base station 40 as an intermediary.

[0043] The display device 31c is configured to include, for example, a touch panel type liquid crystal display, etc. The display device 31c displays various types of information to the user.

[0044] The terminal_ECU 30 communicates with the in-vehicle device 15 using the first terminal communicator 31a. This enables the first terminal communicator 31a to receive abnormality information and associated information from the in-vehicle device 15. In this case, the terminal_ECU 30 permits the first terminal communicator 31a to communicate with the in-vehicle device 15 only when coupling between the mobile communication terminal 6 and the in-vehicle device 15 is established.

[0045] Furthermore, the terminal_ECU 30 displays the abnormality information received from the in-vehicle device 15 on the display device 31c. In this case, the terminal_ECU 30 displays part of the abnormality information received from the in-vehicle device 15 on the display device 26a. For example, as shown in Fig. 6, the terminal_ECU 30 displays an error code and a brief explanation of the abnormality from the abnormality information on the display device 26a. Furthermore, it is preferable that the terminal_ECU 30 displays a search screen that allows the user to search for specific abnormality details, etc.

[0046] Furthermore, the terminal_ECU 30 communicates with the control server 7 using the second terminal communicator 31b. This enables the second terminal communicator 31b to transmit all of the abnormality information and associated information received from the in-vehicle device 15 to the control server 7. Furthermore, when an information search is performed using a search screen, the terminal_ECU 30 is able to transmit an information search request to the control server 7, etc. In these cases, the terminal_ECU 30 transmits terminal information for identifying the mobile communication terminal 6 to the control server 7 as associated information.

[0047] Furthermore, the terminal_ECU 30 is capable of receiving various types of information transmitted from the control server 7 through communication using the second terminal communicator 31b. As will be described later, the information received from the control server 7 can include various types of information such as countermeasures to be taken in the event of an abnormality in the vehicle M and search results for an information search. In this case, for example, as shown in FIG. 7, the terminal_ECU 30 displays information on countermeasures to be taken in the event of an abnormality (and information on the search results) on the display device 26a, along with an error code and a brief explanation of the abnormality.

[0048] The control server 7 is installed in a dealer, etc. The control server 7 has a server control unit (server_ECU) 35 as a server control means (server processor).

[0049] The server_ECU 35 is connected to, for example, a server communicator 36a as a server communication means and an abnormality database (abnormality DB) 36b.

[0050] The server communicator 36a is a communicator for performing communication using a non-short-range wireless communication standard. That is, the server communicator 36a is capable of performing communication using a communication standard (second communication standard) that uses the base station 40 as an intermediary.

[0051] The abnormality database 36b is a large-capacity recording medium such as a HDD, etc. The abnormality database 36b stores explanations of various error codes, countermeasures for abnormalities, and the like.

[0052] The server_ECU 35 communicates with the mobile communication terminal 6 using the server communicator 36a. This allows the control server 7 to receive various information transmitted from the mobile communication terminal 6. That is, the control server 7 can receive various information transmitted from the in-vehicle device 15 via the mobile communication terminal 6. This allows the control server 7 to collect abnormality information and associated information of the vehicle M.

[0053] The server_ECU 35 also analyzes the collected abnormality information of the vehicle M as appropriate. When analyzing this abnormality information, the server_ECU 35 can take into consideration accompanying information and information stored in the abnormality DB 36b. The analysis results include, for example, information on the user's countermeasures for the abnormality. The server_ECU 35 can then transmit the analysis results based on the abnormality information to the mobile communication terminal 6 through communication using the server communicator 36a.

[0054] Furthermore, the server_ECU 35 can receive a search request for an abnormality from the mobile communication terminal 6 through communication with the server communicator 36a. Upon receiving the search request, the server_ECU 35 searches the abnormality DB 36b for information in response to the search request. The server_ECU 35 can then transmit the search results for the search request to the mobile communication terminal 6 through communication with the server communicator 36a.

[0055] Next, abnormality response control in the on-board device when an abnormality occurs in the vehicle will be described with reference to the flowchart showing the abnormality response control routine shown in Fig. 2. This routine is repeatedly executed by the CP_ECU 21 at set time intervals.

[0056] When the routine starts, the CP_ECU 21 collects abnormality diagnosis results from the ECUs 22 to 25 in step S101.

[0057] In the following step S102, the CP_ECU 21 checks whether a new abnormality in the vehicle M has been detected based on the collected abnormality diagnosis results and the like.

[0058] Then, in step S102, if it is determined that no new abnormality has been detected (step S102: NO), the CP_ECU 21 proceeds to step S105.

[0059] On the other hand, if it is determined in step S102 that a new abnormality has been detected (step S102: YES), the CP_ECU 21 proceeds to step S103.

[0060] In step S103, the CP_ECU 21 records the newly detected abnormality information in a storage or the like.

[0061] In the following step S104, the CP_ECU 21 collects various pieces of information associated with the abnormality information from the image recognition_ECU 13, the locator unit 20, and each of the ECUs 22 to 25, etc.

[0062] Furthermore, when the process proceeds from step S102 to step S105, the CP_ECU 21 checks whether there has been a change in the abnormality information stored in the storage, etc. Here, a case where the abnormality information has changed corresponds to, for example, a case where the abnormality has been improved or resolved as a result of a user or other person taking action against the abnormality of the vehicle M.

[0063] Then, if it is determined in step S105 that there is no change in the abnormality information (step S105: NO), the CP_ECU 21 proceeds to step S107.

[0064] On the other hand, if it is determined in step S105 that there has been a change in the abnormality information (step S105: YES), the CP_ECU 21 proceeds to step S106.

[0065] In step S106, the CP_ECU 21 updates the abnormality information recorded in the storage or the like, and then proceeds to step S107. For example, if the abnormality information recorded in the storage or the like has been improved, the CP_ECU 21 rewrites the abnormality information with the improved abnormality information. In this case, the CP_ECU 21 moves and stores the abnormality information before improvement in an abnormality history folder or the like provided in the storage or the like. Also, for example, if the abnormality information recorded in the storage or the like has been resolved, the CP_ECU 21 moves and stores the abnormality information in the abnormality history folder or the like.

[0066] When the process proceeds from step S104, step S105, or step S106 to step S107, the CP_ECU 21 checks whether or not there is currently any abnormality information recorded in a storage or the like.

[0067] Then, in step S107, if it is determined that there is no abnormality information (step S107: NO), the CP_ECU 21 proceeds to step S109.

[0068] On the other hand, if it is determined in step S107 that abnormality information exists (step S107: YES), the CP_ECU 21 proceeds to step S108.

[0069] In step S108, the CP_ECU 21 displays, for example, the abnormality information on an indicator on the display device 26a or the like, and then proceeds to step S109.

[0070] When the process proceeds from step S107 or step S108 to step S109, the CP_ECU 21 checks whether the current abnormality information has changed from the abnormality information previously recorded in a storage or the like. Here, the abnormality information may change, for example, when abnormality information is added due to a new abnormality being detected. Furthermore, the abnormality information may change, for example, when the abnormality is improved or resolved as a result of a user's response to the abnormality in the vehicle M.

[0071] Then, in step S109, if it is determined that the abnormality information has not changed (step S109: NO), the CP_ECU 21 exits the routine.

[0072] On the other hand, if it is determined in step S109 that the abnormality information has changed (step S109: YES), the CP_ECU 21 proceeds to step S110.

[0073] In step S110, the CP_ECU 21 checks whether the user's mobile communication terminal 6 is connected to the in-vehicle device 15 so as to be able to communicate with it.

[0074] Then, in step S110, if it is determined that the user's mobile communication terminal 6 is not connected (step S110: NO), the CP_ECU 21 proceeds to step S111.

[0075] In step S111, the CP_ECU 21 instructs the user to couple the in-vehicle device 15 and the mobile communication terminal 6, for example, by displaying on the display device 26a or outputting audio from the speaker 26b, and then returns to step S110.

[0076] On the other hand, if it is determined in step S110 that the user's mobile communication terminal 6 is connected (step S110: YES), the CP_ECU 21 proceeds to step S112.

[0077] In step S112, the CP_ECU 21 transmits the abnormality information and associated information to the user's mobile communication terminal 6 using the vehicle communication device 26c, and then exits the routine.

[0078] Next, abnormality response control in the mobile communication terminal when an abnormality occurs in the vehicle will be described with reference to the flowchart showing the abnormality response control routine shown in Fig. 3. This routine is repeatedly executed by terminal_ECU 30 at set time intervals.

[0079] When the routine starts, the terminal_ECU 30 checks whether or not information (such as abnormality information and accompanying information) from the vehicle M has been received.

[0080] Then, in step S201, if it is determined that information has not been received from the vehicle M (step S201: NO), the terminal_ECU 30 proceeds to step S206.

[0081] On the other hand, if it is determined in step S201 that information has been received from the vehicle M (step S201: YES), the terminal_ECU 30 proceeds to step S202.

[0082] In step S202, the terminal_ECU 30 selects some information from the received information and stores the selected information in a storage, etc. In this case, the terminal_ECU 30 selects, for example, the minimum amount of information from the received information that can identify an abnormality in the vehicle M, such as an error code.

[0083] In the following step S203, the terminal_ECU 30 displays abnormality information or the like corresponding to the error code on the display device 31c (see, for example, FIG. 6), and then proceeds to step S204.

[0084] In step S204, terminal_ECU 30 checks whether communication with base station 40 is possible.

[0085] Then, in step S204, if it is determined that communication with the base station 40 is not possible (step S204: NO), the terminal_ECU 30 remains in standby mode.

[0086] On the other hand, if it is determined in step S204 that communication with the base station 40 is possible (step S204: YES), the terminal_ECU 30 proceeds to step S205.

[0087] In step S205, the terminal_ECU 30 transmits (transfers) the information received from the in-vehicle device 15 (such as abnormality information and associated information) to the control server 7, and then proceeds to step S206. In this case, the terminal_ECU 30 adds, for example, the terminal information of the mobile communication terminal 6 to the information to be transmitted to the control server 7.

[0088] When the process proceeds from step S201 or step S205 to step S206, the terminal_ECU 30 checks whether or not the user has performed an information search on the mobile communication terminal 6.

[0089] Then, in step S206, if it is determined that an information search is not being performed (step S206: NO), the terminal_ECU 30 proceeds to step S209.

[0090] On the other hand, if it is determined in step S206 that an information search has been performed (step S206: YES), the terminal_ECU 30 proceeds to step S207.

[0091] In step S207, terminal_ECU 30 checks whether communication with base station 40 is possible.

[0092] Then, in step S207, if it is determined that communication with the base station 40 is not possible (step S207: NO), the terminal_ECU 30 remains in standby mode.

[0093] On the other hand, if it is determined in step S207 that communication with the base station 40 is possible (step S207: YES), the terminal_ECU 30 proceeds to step S208.

[0094] In step S208, the terminal_ECU 30 transmits a search request for the information input by the user to the control server 7, and then proceeds to step S209. In this case, the terminal_ECU 30 adds the terminal information of the mobile communication terminal 6 to the information to be transmitted to the control server 7, for example.

[0095] When the process proceeds from step S206 or step S208 to step S209, the terminal_ECU 30 checks whether or not information from the control server 7 has been received.

[0096] Then, in step S209, if it is determined that information has not been received from the control server 7 (step S209: NO), the terminal_ECU 30 exits the routine.

[0097] On the other hand, if it is determined in step S209 that the information has been received from the control server 7 (step S209: YES), the terminal_ECU 30 proceeds to step S210.

[0098] In step S210, the terminal_ECU 30 stores the information received from the control server 7.

[0099] In the following step S211, the terminal_ECU 30 displays the received information on the display device 31c (see, for example, FIG. 7), and then exits the routine.

[0100] Next, abnormality response control in the control server when an abnormality occurs in the vehicle will be described with reference to the flowchart showing the abnormality response control routine shown in Figure 4. This routine is repeatedly executed by the server_ECU 35 at set time intervals.

[0101] When the routine starts, the server_ECU 35 checks in step S301 whether or not information has been received from the mobile communication terminal 6.

[0102] Then, in step S301, if it is determined that information has not been received from the mobile communication terminal 6 (step S301: NO), the server_ECU 35 exits the routine.

[0103] On the other hand, if it is determined in step S301 that information has been received from the mobile communication terminal 6 (step S301: YES), the server_ECU 35 proceeds to step S302.

[0104] In step S302, the server_ECU 35 recognizes the terminal information included in the received information.

[0105] In the following step S303, the server_ECU 35 checks whether the information received from the mobile communication terminal 6 includes abnormality information.

[0106] Then, in step S303, if it is determined that abnormality information is not included (step S303: NO), the server_ECU 35 proceeds to step S306.

[0107] On the other hand, if it is determined in step S303 that abnormality information is included (step S303: YES), the server_ECU 35 proceeds to step S304.

[0108] In step S304, the server_ECU 35 stores the received information in a storage or the like in association with the terminal information.

[0109] In the following step S305, the server_ECU 35 analyzes the received information. That is, the server_ECU 35 analyzes the abnormality information while taking into consideration, for example, accompanying information received together with the abnormality information and information stored in the abnormality DB 36b.

[0110] When the process proceeds from step S303 or step S305 to step S306, the server_ECU 35 checks whether the information received from the mobile communication terminal 6 includes a search request.

[0111] Then, in step S306, if it is determined that the received information does not include a search request (step S306: NO), the server_ECU 35 proceeds to step S308.

[0112] On the other hand, if it is determined in step S306 that the received information includes a search request, the server_ECU 35 proceeds to step S307.

[0113] In step S307, the server_ECU 35 searches the abnormality DB 36b for information in response to the search request.

[0114] When the process proceeds from step S305 or step S307 to step S308, the server_ECU35 checks whether there is information to be transmitted to the mobile communication terminal 6. That is, the server_ECU35 checks whether information that can be transmitted to the mobile communication terminal 6 has been generated in the above-mentioned step S305 or step S307.

[0115] Then, in step S308, if it is determined that there is no transmission information (step S308: NO), the server_ECU 35 exits the routine.

[0116] On the other hand, if it is determined in step S308 that transmission information exists (step S308: YES), the server_ECU 35 proceeds to step S309.

[0117] In step S309, the server_ECU 35 checks whether communication with the mobile communication terminal 6 is possible.

[0118] Then, in step S309, if it is determined that communication with the mobile communication terminal 6 is not possible (step S309: NO), the server_ECU 35 remains in standby mode.

[0119] On the other hand, if it is determined in step S309 that communication with the mobile communication terminal 6 is possible (step S309: YES), the server_ECU 35 proceeds to step S310.

[0120] In step S310, the server_ECU 35 transmits the information generated in step S305 or step S307 to the mobile communication terminal 6 corresponding to the terminal information recognized in step S302, and then exits the routine.

[0121] 5, when an abnormality occurs in the vehicle M, the CP_ECU 21 of the in-vehicle device 15 transmits abnormality information and the like to the mobile communication terminal 6 by communication using a short-range wireless communication standard. In this case, the CP_ECU 21 transmits the abnormality information and the like only to the mobile communication terminal 6 that is coupled with the in-vehicle device 15.

[0122] When receiving the abnormality information, etc., the terminal_ECU30 of the mobile communication terminal 6 displays part of the received abnormality information on the display device 31c. In this case, the portable_ECU30 displays the abnormality that has occurred in the vehicle M on the display device 31c using specific text information, etc. In this way, the terminal_ECU30 allows the user, etc. to accurately recognize the abnormality that has occurred in the vehicle M.

[0123] Furthermore, the terminal_ECU 30 transmits all of the information received from the in-vehicle device 15 to the control server 7 by communication using a non-short-range wireless communication standard. In this way, the mobile communication terminal 6 is involved in the information communication from the vehicle M to the control server 7. As a result, even if the vehicle M becomes unable to travel in a location where it cannot communicate with the control server 7, for example, the user holding the mobile communication terminal 6 can transmit abnormality information, etc. to the control server 7 simply by getting out of the vehicle M and moving a predetermined distance.

[0124] At this time, the terminal_ECU 30 adds the terminal information to the information transmitted from the mobile communication terminal 6. As a result, the control server 7 obtains information about the user who is the source of the information transmission without requesting the user information from the user or the like.

[0125] The server_ECU35 of the control server 7 transmits information (such as countermeasure information for the abnormality) generated by analyzing the abnormality information to the mobile communication terminal 6 via communication using a non-short-range wireless communication standard. At that time, the server_ECU35 accurately transmits the countermeasure information to the user's mobile communication terminal 6 by using the acquired terminal information.

[0126] The terminal_ECU30 of the mobile communication terminal 6 displays the countermeasure information etc. received from the control server 7 on the display device 31c. This allows the user etc. to obtain detailed countermeasure information for the abnormality of the vehicle M.

[0127] Furthermore, by displaying detailed countermeasure information on the mobile communication terminal 6, the user or the like can take measures to deal with the abnormality of the vehicle M if the abnormality of the vehicle M is minor.

[0128] When an abnormality countermeasure is taken, the CP_ECU 21 updates the abnormality information as necessary and transmits the updated abnormality information to the mobile communication terminal 6.

[0129] Then, the terminal_ECU 30 displays the updated abnormality information on the display device 31c, thereby enabling the user or the like to immediately check the results of the countermeasures taken against the abnormality of the vehicle M.

[0130] Furthermore, the terminal_ECU30 transmits the updated abnormality information to the control server 7. As a result, even if a user or the like takes measures to deal with the abnormality, the updated abnormality information is reflected in the control server 7.

[0131] According to this embodiment, the vehicle information communication system 1 includes an in-vehicle device 15 having a vehicle communicator 26c that communicates using a short-range wireless communication standard without the intervention of a base station and a CP_ECU 21, a mobile communication terminal 6 having a first terminal communicator 31a that communicates using the short-range wireless communication standard, a second terminal communicator 31b that communicates using a non-short-range wireless communication standard that requires the intervention of a base station, a display device 31c that displays information to a user, and a terminal_ECU 30, and a control server 7 having a server communicator 36a that communicates using the non-short-range wireless communication standard. When an abnormality in the vehicle M is detected, the CP_ECU 21 transmits abnormality information about the vehicle M from the vehicle communicator 26c only to the first terminal communicator 31a of the mobile communication terminal 6 that is paired and registered with the in-vehicle device 15. Furthermore, when the terminal_ECU 30 receives abnormality information from the in-vehicle device 15, it displays information extracted from the abnormality information on the display device 31c, and also transmits the abnormality information from the second terminal communicator 31b to the server communicator 36a. This allows the abnormality information communicated between the vehicle M and the control server 7 to be appropriately disclosed to the user.

[0132] That is, in the vehicle information communication system 1 of this embodiment, the mobile communication terminal 6 that is coupled with the in-vehicle device 15 is always involved in the information communication between the in-vehicle device 15 and the control server 7. This allows the abnormality information to be appropriately displayed as text on the display device 31c of the mobile communication terminal 6 used by the user or the like.

[0133] In this case, the abnormality information includes an error code, and the terminal_ECU 30 can display a search screen on the display device 31c that allows a user to search for detailed information corresponding to the error code. Therefore, even when a user or the like needs detailed information about the abnormality information, the information can be quickly disclosed.

[0134] Furthermore, when transmitting abnormality information or the like to the control server 7, the terminal_ECU30 attaches information identifying the mobile communication terminal 6 to the abnormality information. As a result, when the control server 7 analyzes the abnormality information, the server_ECU35 can accurately transmit information such as the analysis results to the user's mobile communication terminal 6.

[0135] In the above-described embodiment, the image recognition_ECU 13, the driving_ECU 14, the CP_ECU 21, the E / G_ECU 22, the T / M_ECU 23, the BK_ECU 24, the PS_ECU 25, the terminal_ECU 30, and the server_ECU 35 are configured by well-known microcomputers including a CPU (processor), RAM, ROM, a non-volatile storage unit, and peripheral devices. The ROM stores programs to be executed by the CPU and fixed data such as data tables in advance. Note that all or part of the functions of the processor may be configured by logic circuits or analog circuits. Furthermore, the processing of various programs may be realized by electronic circuits such as FPGAs.

[0136] The invention described in the above embodiments is not limited to those embodiments, and various modifications can be made in the implementation stage without departing from the gist of the invention. For example, in the above embodiments, an example of a configuration in which the first terminal communicator 31a performs wireless communication with the vehicle communicator 26c, etc. using a short-range wireless communication standard has been described. However, it is also possible to configure the first terminal communicator 31a to perform wired communication with the vehicle communicator 26c, etc. Furthermore, the above embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining the disclosed multiple constituent elements.

[0137] For example, if the stated problem can be solved and the stated effect can be obtained even if some of the constituent elements are deleted from all the constituent elements shown in the above form, the configuration from which these constituent elements are deleted can be extracted as an invention. [Explanation of symbols]

[0138] 1 ... Vehicle information and communication system 5. Driving assistance devices 6. Mobile communication devices 7... Control server 10...Camera unit 11...Stereo camera 11a ... Main camera 11b ... Sub camera 13...Image Recognition_ECU 14 … Driving_ECU 15…In-vehicle equipment 20... Locator unit 20a ... GNSS sensor 20b ... Road map DB 21 … CP_ECU 22 ... E / G_ECU 23 ... Transmission ECU 24 … BK_ECU 25 … PS_ECU 26a...Display device 26b ... Speaker 26c … Vehicle communication device 30 ... Terminal ECU 31a ... First terminal communication device 31b ... Second terminal communication device 31c…Display device 35 ... Server ECU 36a ... Server communication device 36b … Anomaly Database 40 … Base station M: Vehicle (own vehicle)

Claims

1. an in-vehicle device including a vehicle communication means for performing communication using a first communication standard without the intervention of a base station and a vehicle control means; a mobile communication terminal having a first terminal communication means for performing communication using the first communication standard, a second terminal communication means for performing communication using a second communication standard via the base station, a display means for displaying information to a user, and a terminal control means; a control server having a server communication means for performing communication using the second communication standard, when an abnormality in the vehicle is detected, the vehicle control means transmits abnormality information of the vehicle from the vehicle communication means only to the first terminal communication means of the mobile communication terminal that is paired and registered with the in-vehicle device; The vehicle information communication system is characterized in that, when the terminal control means receives the abnormality information from the in-vehicle device, it causes the display means to display information extracted from the abnormality information, and transmits the abnormality information from the second terminal communication means to the server communication means.

2. The abnormality information includes an error code, 2. The vehicle information communication system according to claim 1, wherein the terminal control means displays, on the display means, a search screen on which detailed information corresponding to the error code can be searched.

3. The vehicle information communication system according to claim 1, characterized in that when the terminal control means transmits the abnormality information from the second terminal communication means to the server communication means, the terminal control means attaches information identifying the mobile communication terminal to the abnormality information.

4. the control server has a server control means, the server control means transmits an analysis result based on the anomaly information from the server communication means to the second terminal communication means; 4. The vehicle information communication system according to claim 3, wherein the terminal control means causes the display means to display the analysis results received from the control server.

5. an in-vehicle device including a vehicle communicator that performs communication using a first communication standard without using a base station, and a vehicle processor; a mobile communication terminal having a first terminal communicator for performing communication using the first communication standard, a second terminal communicator for performing communication using a second communication standard that uses the base station as an intermediary, a display device for displaying information to a user, and a terminal processor; a control server having a server communicator that performs communication using the second communication standard, When an abnormality in the vehicle is detected, the vehicle processor transmits abnormality information of the vehicle from the vehicle communicator only to the first terminal communicator of the mobile communication terminal that is paired and registered with the in-vehicle device; When the terminal processor receives the abnormality information from the in-vehicle device, it displays information extracted from the abnormality information on the display device, and transmits the abnormality information from the second terminal communicator to the server communicator.

Images