Vehicle Trouble Response System

Abstract

To provide a vehicle troubleshooting system capable of providing suitable service regarding trouble generated in a vehicle.SOLUTION: A vehicle troubleshooting system 100 includes: a trouble detection unit M11 for detecting that a trouble related to travel of a vehicle 10 has occurred in the vehicle 10; a trouble information transmission unit M13 for acquiring trouble information related to the trouble detected by the trouble detection unit M11; a countermeasures generation unit M15 for generating countermeasures corresponding to the trouble detected by the trouble detection unit M11 based on the trouble information acquired by the trouble information transmission unit M13; and a countermeasures execution unit M17 for executing processing corresponding to the countermeasures generated by the countermeasures generation unit M15.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a vehicle trouble response system.

Background Art

[0002] Patent Document 1 describes a system that transmits the occurrence process and trouble situation of vehicle troubles from the vehicle to an external organization. In Patent Document 1, a traffic accident is assumed as a vehicle trouble, and a police department, a car dealer, or an insurance company is assumed as an external organization. And it is trying to process the vehicle trouble smoothly and quickly.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, as vehicle troubles, various things can be considered in addition to traffic accidents. An object of the present invention is to provide a system that can suitably solve various troubles related to vehicles.

Means for Solving the Problems

[0005] A vehicle trouble response system for solving the above problems comprises a first control device installed in the vehicle and a second control device located outside the vehicle, and is a system for responding to troubles related to the operation of the vehicle. In this vehicle trouble response system, the first control device includes a trouble detection unit that detects that the trouble has occurred in the vehicle, and a trouble information transmission unit that transmits trouble information related to the trouble detected by the trouble detection unit to the second control device. The second control device includes a countermeasure generation unit that generates countermeasures in accordance with the trouble information transmitted from the trouble information transmission unit.

[0006] According to the above configuration, when the first control unit detects a problem related to the vehicle's operation, trouble information related to that problem is transmitted outside the vehicle. The second control unit generates countermeasures in accordance with the trouble information transmitted from the first control unit. By generating countermeasures in accordance with the troubles that occur in the vehicle in this way, it is possible to respond to a variety of troubles that may occur in the vehicle. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 is a schematic diagram showing a vehicle trouble response system according to the first embodiment. [Figure 2] Figure 2 is a flowchart showing the process flow for sending trouble information. [Figure 3] Figure 3 is a flowchart showing the process flow for generating countermeasures for vehicles without problems and implementing those countermeasures. [Figure 4] Figure 4 is a schematic diagram showing the vehicle trouble response system of the second embodiment. [Figure 5] Figure 5 is a schematic diagram showing a vehicle trouble response system according to the third embodiment. [Figure 6] Figure 6 is a flowchart showing the process flow in which the server device generates countermeasures for vehicles without problems and transmits those countermeasures. [Figure 7]Figure 7 is a flowchart showing the process flow in the server device for generating countermeasures for vehicles that have already experienced problems and sending those countermeasures. [Figure 8] Figure 8 is a flowchart showing the process flow in which a client device receives and implements countermeasures for vehicles without problems and vehicles that have already experienced problems. [Figure 9] Figure 9 is a flowchart showing the process flow for implementing vehicle countermeasures in the client device in accordance with the wishes of the vehicle occupants. [Modes for carrying out the invention]

[0008] (First Embodiment) The first embodiment of a system for responding to vehicle driving troubles (hereinafter referred to as "vehicle driving troubles") (hereinafter referred to as "vehicle trouble response system") will be described below with reference to Figures 1 to 3.

[0009] Here, vehicle driving troubles include troubles that impede the driving of vehicle 10 and troubles that render vehicle 10 inoperable. Troubles that impede the driving of vehicle 10 include, for example, fade, deceleration slip, insufficient battery charge, and imbalance in tire pressure. Troubles that render the vehicle inoperable include, for example, getting stuck, overheating, flooding, and tire bursts. An imbalance in tire pressure can occur when some of the tires leak air.

[0010] As shown in Figure 1, the vehicle trouble response system 100 of this embodiment is configured so that multiple vehicles 10 can communicate with each other via vehicle-to-vehicle communication. Here, vehicle-to-vehicle communication refers to wireless communication between the vehicles 10.

[0011] <Vehicle Configuration> The vehicle 10 includes a vehicle detection system 11, a vehicle display unit 12, a vehicle operation unit 13, a vehicle control unit 14, and a vehicle communication unit 15.

[0012] The vehicle detection system 11 detects at least one of the following: information necessary to determine whether or not a vehicle driving trouble occurred in vehicle 10, or information indicating the circumstances when a vehicle driving trouble occurred. The vehicle detection system 11 includes, for example, a wheel speed sensor, an acceleration sensor, a tire pressure sensor, and an imaging device. The tire pressure sensor detects the air pressure of the tires. The imaging device captures images of the area outside the vehicle. In the following description, the output of the vehicle detection system 11 is referred to as "vehicle sensor information".

[0013] The vehicle display unit 12 displays information output from the vehicle control unit 14. The vehicle display unit 12 may be a display unit whose primary function is to display externally input information (hereinafter referred to as the "external information display function"), or it may be a display unit whose external information display function is secondary. Here, a display unit whose external information display function is secondary refers to a display unit that has an external information display function in addition to the function of displaying the processing results of the function of the device, such as the display unit of a navigation system.

[0014] The vehicle control unit 13 accepts operations from the occupants of the vehicle 10. The vehicle control unit 13 may include control buttons or a touch panel. The vehicle control unit 13 may also include a voice recognition device.

[0015] The vehicle control unit 14 includes a control unit (hereinafter referred to as "CPU") and memory. The memory stores a control program. The vehicle control unit 14 functions as a trouble detection unit M11, a trouble information transmission unit M13, a countermeasure generation unit M15, and a countermeasure execution unit M17, as the CPU periodically executes the control program.

[0016] The trouble detection unit M11 detects that a vehicle driving trouble has occurred in vehicle 10. In this embodiment, the trouble detection unit M11 detects that a vehicle driving trouble has occurred in vehicle 10 based on vehicle sensor information. In the following description, a vehicle 10 in which a vehicle driving trouble has already occurred will be referred to as a "vehicle with trouble 10a", and a vehicle 10 in which a vehicle driving trouble has not yet occurred will be referred to as a "vehicle without trouble 10y".

[0017] The trouble information transmission unit M13 generates information related to vehicle running troubles detected by the trouble detection unit M11 (hereinafter referred to as "trouble information"), and transmits the trouble information from the vehicle communication unit 15 to the outside of the vehicle.

[0018] Here, the trouble information includes the type of vehicle running trouble, the occurrence location of the vehicle running trouble, the occurrence date and time of the vehicle running trouble, information about the trouble vehicle 10a, and the severity level of the vehicle running trouble. In addition, the information about the trouble vehicle 10a includes the characteristics of the trouble vehicle, for example, the vehicle type, drive method, equipment, and power source of the trouble vehicle 10a. As the severity level of the vehicle running trouble, for example, information indicating whether it was possible to escape from the vehicle running trouble by oneself, the time required from the occurrence of the vehicle running trouble until escaping from the trouble, and the magnitude of the damage received by the trouble vehicle 10a due to the vehicle running trouble are considered.

[0019] The countermeasure generation unit M15 generates countermeasures (hereinafter referred to as "untroubled vehicle countermeasures") to suppress the occurrence of vehicle running troubles that occurred in the trouble vehicle 10a from occurring in the untroubled vehicle 10y based on the trouble information transmitted from one or more trouble vehicles 10a. The untroubled vehicle countermeasures are countermeasures aimed at preventing the occurrence of vehicle running troubles in the untroubled vehicle 10y.

[0020] The countermeasure generation unit M15 may generate untroubled vehicle countermeasures according to the number of occurrences of vehicle running troubles occurring in the same area based on the trouble occurrence location as trouble information, or may generate untroubled vehicle countermeasures according to the trouble severity as trouble information. When the number of occurrences of vehicle running troubles occurring in the same area is less than a predetermined value or when the severity level of the trouble is lower than a predetermined level, the countermeasure generation unit M15 may not generate untroubled vehicle countermeasures.

[0021] As a measure for vehicles that have not experienced any problems, for example, trouble information could be notified to the occupants of 10-year-old vehicles that have not experienced any problems. In this case, the location of the trouble could be indicated on a map with a predetermined mark, or the severity of the trouble could be indicated by the size and shape of a predetermined mark.

[0022] Furthermore, measures to address vehicles without problems could include proposing changes to the control mode, driving route, or equipment (hereinafter referred to as "changes to the control mode, etc.") or instructing changes to the control mode, etc. Changes to the driving route could be based on the location of vehicle driving problems as trouble information, and the route could be changed to one with a relatively low number of vehicle driving problems, or it could be based on the terrain shown in the map information and the type of vehicle driving problems included in the trouble information, and the route could be determined to be less prone to vehicle driving problems. Measures to address vehicles without problems could include proposing to cancel travel by vehicles without problems (10 years old), or prohibiting travel by vehicles without problems (10 years old).

[0023] Here, we will explain an example of countermeasures for a vehicle that is not experiencing problems when the vehicle is stuck. Getting stuck is a phenomenon in which the wheels of vehicle 10 become trapped in snow or mud, making it impossible to move vehicle 10 forward or backward.

[0024] Therefore, as a countermeasure against vehicles that have not experienced problems related to getting stuck, it is possible to suggest or instruct the driver to change to a control mode that suppresses the drive torque acting on the wheels or to change to a route where the likelihood of getting stuck is deemed low. Possible control modes to suppress the drive torque acting on the wheels include a control mode that suppresses the drive torque applied to the wheels, and a control mode that offsets a portion of the drive torque applied to the wheels with braking torque applied to the wheels. An example of a control mode to suppress the drive torque applied to the wheels is a control mode that suppresses the reduction ratio of the transmission. Also, an example of a control mode that offsets a portion of the drive torque applied to the wheels with braking torque applied to the wheels is a control mode that makes it easier for traction control to intervene.

[0025] Next, we will explain an example of countermeasures for vehicles that have not experienced a problem, specifically when the vehicle's driving trouble is deceleration slip. Deceleration slip is a phenomenon in which the wheels slip against the road surface. Therefore, possible countermeasures for vehicles that have not experienced a problem related to deceleration slip include suggesting a change to a control mode that suppresses the braking torque acting on the wheels, or changing to a driving route where the likelihood of deceleration slip occurring is deemed low, and instructing the driver to make these changes. As a control mode that suppresses the braking torque acting on the wheels, a control mode that makes it easier for the anti-lock brakes to intervene can be considered.

[0026] Measures to address vehicle issues related to deceleration and slippage that have not yet occurred could include suggesting the installation of tire chains or the replacement of tires with studless tires, providing information on locations for installing tire chains or changing to studless tires, and guiding drivers to these locations, or providing information on locations for purchasing tire chains or studless tires, and guiding drivers to these locations.

[0027] The countermeasure execution unit M17 executes processing according to the countermeasures for non-trouble vehicles generated by the countermeasure generation unit M15. More specifically, if the countermeasure for a vehicle without problems proposes a change in the control mode, etc., the countermeasure execution unit M17 notifies the occupant of the vehicle 10 of the proposed content and implements the proposed content on the condition that it receives confirmation from the occupant that it accepts the proposed content. In this case, the countermeasure execution unit M17 may display the proposed content on the vehicle display unit 12 or convert the proposed content into voice. The countermeasure execution unit M17 may also accept the operation of the vehicle operation unit 13 by the occupant of the vehicle 10 as the occupant's intention.

[0028] Furthermore, if the countermeasure for a vehicle without problems involves instructing a change in the control mode, etc., the countermeasure execution unit M17 will implement the instruction without confirming the intention of the occupant of the vehicle 10. <Processing flow for responding to vehicle driving problems> Figure 2 is a flowchart showing the process in vehicle 10 for detecting a vehicle driving trouble and transmitting trouble information related to that vehicle driving trouble (hereinafter referred to as the "trouble information transmission process"). Figure 3 is a flowchart showing the process in vehicle 10 (vehicle 10y without trouble) for receiving trouble information transmitted from vehicle 10a with trouble, generating countermeasures for the vehicle without trouble based on that trouble information, and implementing those countermeasures for the vehicle without trouble (hereinafter referred to as the "countermeasure implementation process"). The control programs corresponding to these processes are stored in the memory of the vehicle control unit 14 and are executed periodically by the CPU of the vehicle control unit 14.

[0029] In step S11, the vehicle control unit 14 determines whether or not a vehicle driving trouble has been detected by the trouble detection unit M11. If the vehicle control unit 14 determines that no vehicle driving trouble has been detected (S11: NO), it terminates the current process. However, if it determines that a vehicle driving trouble has been detected (S11: YES), it proceeds to the process in step S13.

[0030] In step S13, the vehicle control unit 14 generates trouble information related to the vehicle driving trouble detected in step S11 using the trouble information transmission unit M13, and transmits this trouble information to the outside of the vehicle via the vehicle communication unit 15. After that, the vehicle control unit 14 terminates the current process.

[0031] In step S21 of Figure 3, the vehicle control unit 14 of the non-trouble vehicle 10y determines whether or not trouble information transmitted from the troubled vehicle 10a has been received by the vehicle communication unit 15. If the vehicle control unit 14 determines that trouble information has not been received (S21: NO), it terminates the current process. However, if it determines that trouble information has been received (S21: YES), it proceeds to the process in step S22.

[0032] In step S22, the vehicle control unit 14 generates countermeasures for non-trouble vehicles based on trouble information using the countermeasure generation unit M15. In step S23, the vehicle control unit 14 determines whether the countermeasure for non-trouble vehicles generated in step S22 is a proposal to change the control mode, etc. If the vehicle control unit 14 determines that the countermeasure for non-trouble vehicles is not a proposal to change the control mode, etc. (S23: NO), it proceeds to step S26 without executing the processes from steps S24 to S25. On the other hand, if the vehicle control unit 14 determines that the countermeasure for non-trouble vehicles is a proposal to change the control mode, etc. (S23: YES), it executes the processes from steps S24 to S25 and then proceeds to step S26.

[0033] In step S24, the vehicle control unit 14 notifies the occupants of the unaffected vehicle 10y of the proposed measures via the countermeasure execution unit M17. At this time, the vehicle control unit 14 may also notify the occupants of the proposed measures and how to indicate their willingness to accept them.

[0034] In step S25, the vehicle control unit 14 determines, via the countermeasure execution unit M17, whether or not it has received an indication of acceptance of the proposal from the occupant of the unaffected vehicle 10y. If the vehicle control unit 14 determines that it has not received confirmation from the occupant that they intend to accept the proposal (S25: NO), it terminates the current process. The vehicle control unit 14 may wait for a predetermined time until the occupant's intention is received.

[0035] If the vehicle control unit 14 determines that it has received the occupant's intention to accept the proposal (S25: YES), it proceeds to step S26. In step S26, the vehicle control unit 14 executes processing according to the countermeasures for the vehicle without problems using the countermeasure execution unit M17. After that, the vehicle control unit 14 terminates the current processing.

[0036] <Operation and Effects of This Embodiment> According to this embodiment, when a vehicle driving trouble occurs in vehicle 10, the vehicle driving trouble is detected, and trouble information related to the vehicle driving trouble is transmitted outside the vehicle. In vehicle 10y that has not experienced trouble, when trouble information transmitted from vehicle 10a is received, countermeasures for the vehicle that has not experienced trouble are generated based on the trouble information, and countermeasures for the vehicle that has not experienced trouble are implemented. This makes it possible to suppress the occurrence of vehicle driving troubles in vehicle 10y that has not experienced trouble. Since countermeasures for the vehicle that has not experienced trouble are generated in accordance with the vehicle driving trouble that occurred in vehicle 10a that has experienced trouble, it is possible to suppress the occurrence of various vehicle driving troubles.

[0037] In the vehicle trouble response system 100, multiple vehicles 10 are connected in a communication manner. Therefore, countermeasures for vehicles without problems can be generated based on the number of vehicle driving troubles that have occurred. This allows appropriate countermeasures for vehicles without problems 10y to be implemented.

[0038] In the vehicle trouble response system 100, multiple vehicles 10 are connected to each other via vehicle-to-vehicle communication. Therefore, trouble information is transmitted to a vehicle 10y that is not experiencing trouble and is traveling in the vicinity of the vehicle 10a that has already experienced trouble. Here, since the vehicle 10y that is not experiencing trouble is traveling in the same environment as the vehicle 10a that has already experienced trouble, there is a high probability that the same vehicle driving trouble that occurred in the vehicle 10a will occur. Accordingly, according to this embodiment, it is possible to effectively suppress the occurrence of vehicle driving trouble in the vehicle 10y that is not experiencing trouble.

[0039] In the vehicle trouble response system 100, trouble information is notified to the occupant of the trouble-free vehicle 10y. Therefore, the occupant can consider countermeasures based on the trouble information. In addition, the vehicle trouble response system 100 proposes changes to the control mode, etc., to the occupant of the trouble-free vehicle 10y. Therefore, the occupant can decide whether or not to accept the proposal to change the control mode, etc. In other words, according to this embodiment, it is possible to suppress the occurrence of vehicle driving troubles in the trouble-free vehicle 10y while respecting the wishes of the occupant of the trouble-free vehicle 10y.

[0040] According to this embodiment, an instruction to change the control mode, etc., is generated as a countermeasure against vehicles without problems, and this instruction is implemented. This makes it possible to reliably suppress the occurrence of vehicle driving problems in vehicles without problems (10y).

[0041] In this embodiment, the vehicle control unit 14 of the vehicle 10a, which is the vehicle that experienced a vehicle driving trouble, corresponds to the first control device. In addition, the vehicle control unit 14 of the vehicle 10y, which is not experiencing trouble, receives trouble information transmitted from the vehicle 10a, corresponds to the second control device.

[0042] (Second Embodiment) Here, all or part of the functions of the vehicle display unit 12, vehicle operation unit 13, and vehicle control unit 14 in the first embodiment may be realized by a mobile communication device (for example, a smartphone or tablet) carried by the occupants of the vehicle 10.

[0043] Figure 4 is a schematic diagram showing a second embodiment of the vehicle trouble response system. The vehicle trouble response system 200 of the second embodiment includes a mobile communication device 30. In this embodiment, the mobile communication device 30 is positioned inside the vehicle 10 when the occupants of the vehicle 10 board the vehicle 10. In the following description, we will mainly describe the parts that differ from the first embodiment, and components that are the same as or equivalent to those in the first embodiment will be denoted by the same reference numerals and their descriptions will be omitted.

[0044] <Configuration of a mobile communication device> The mobile communication device 30 includes a mobile communication unit 35, a mobile detection system 31, a mobile display unit 32, a mobile operation unit 33, and a mobile control unit 34.

[0045] The mobile communication unit 35 communicates with the vehicle 10, outputs information transmitted from the vehicle 10 to the mobile control unit 34, and transmits information output from the mobile control unit 34 to the vehicle 10. Communication between the mobile communication unit 35 and the vehicle 10 may be wireless or wired.

[0046] The moving object detection system 31 detects information necessary to determine whether or not a vehicle driving trouble has occurred in vehicle 10, and information indicating the circumstances when a vehicle driving trouble occurs. The moving object detection system 31 is composed of, for example, a GPS, a magnetic sensor, an acceleration sensor, a gyroscope, etc. The GPS detects location information. The magnetic sensor detects the direction of the magnetic field. The gyroscope detects the rotational speed. In the following description, the output of the moving object detection system 31 is referred to as "moving object sensor information".

[0047] The mobile display unit 32 displays information output from the mobile control unit 34. The mobile control unit 33 accepts operation from the owner of the mobile communication device 30, i.e., the occupant of the vehicle 10. The mobile control unit 33 may include a touch panel, a voice recognition device, or operation buttons.

[0048] The mobile unit control unit 34 includes a CPU and memory. The memory stores a control program. The mobile unit control unit 34 functions as a trouble detection unit M211, a trouble information transmission unit M213, a countermeasure generation unit M215, and a countermeasure execution unit M217 by the CPU periodically executing the control program. The trouble detection unit M211, trouble information transmission unit M213, countermeasure generation unit M215, and countermeasure execution unit M217 in this embodiment correspond to the trouble detection unit M11, trouble information transmission unit M13, countermeasure generation unit M15, and countermeasure execution unit M17 of the first embodiment, respectively.

[0049] The trouble detection unit M211 detects that a vehicle driving trouble has occurred in vehicle 10 based on the mobile sensor information. The trouble information transmission unit M213 transmits trouble information from the mobile communication unit 35 to the vehicle 10, and the vehicle communication unit 15 transmits the trouble information outside the vehicle.

[0050] The countermeasure generation unit M215 acquires trouble information transmitted from one or more troubled vehicles 10a via the vehicle communication unit 15 and the mobile communication unit 35. Based on the trouble information, the countermeasure generation unit M215 generates countermeasures for vehicles that have not yet experienced trouble.

[0051] The countermeasure execution unit M217 of this embodiment executes processing according to the countermeasure for a vehicle without trouble. If the countermeasure for a vehicle without trouble is to notify the occupant of the vehicle without trouble 10y of trouble information, or if the countermeasure for a vehicle without trouble is to propose a change in the control mode, the countermeasure execution unit M17 may display the trouble information and proposed content on the mobile display unit 32, or it may convert the trouble information and proposed content into voice.

[0052] In this embodiment, the mobile control unit 34 of the mobile communication device 30 brought to the vehicle 10a, which is the vehicle 10 that has experienced a vehicle driving trouble, corresponds to the first control device. Furthermore, the mobile control unit 34 of the mobile communication device 30 brought to the vehicle 10y, which is not experiencing trouble, receives trouble information transmitted from the vehicle 10a, corresponds to the second control device.

[0053] (Third embodiment) Figure 5 is a schematic diagram showing a third embodiment of the vehicle trouble response system. The vehicle trouble response system 300 of the third embodiment is composed of a server device 50, a client device 70, and a vehicle 10. In the following description, the differences from the above multiple embodiments will be mainly described, and the same reference numerals will be used for components that are the same as or equivalent to those in the above multiple embodiments, and redundant explanations will be omitted.

[0054] In the vehicle trouble response system 300, the server device 50 and the client device 70 are each connected to multiple vehicles 10 via a mobile communication network 302. The server device 50 and the client device 70 may be connected via the mobile communication network 302 or via a fixed communication network.

[0055] In this embodiment, the server device 50 is installed at the facility of a company (hereinafter referred to as the "service company") that provides services to the occupants of a vehicle 10 when a vehicle driving trouble occurs in the vehicle 10, and the client device 70 is installed at the facility of an organization (hereinafter referred to as the "third party") that handles vehicle driving troubles in accordance with information provided by the service company. The third party could be the police, road management companies, road service providers, or stores that are affiliated with the service company (hereinafter referred to as "affiliated stores"). Examples of affiliated stores could be gas stations, vehicle repair shops, auto parts stores, etc.

[0056] <Server configuration> The server device 50 includes a server control unit 54 and a server communication unit 55. The server communication unit 55 outputs information received via the mobile communication network 302 to the server control unit 54, and transmits the information output from the server control unit 54 via the mobile communication network 302.

[0057] The server control unit 54 is equipped with a CPU and memory. The control program is stored in the memory. The server control unit 54 functions as a countermeasure generation unit M315 and a countermeasure transmission unit M319 by having the CPU periodically execute the control program.

[0058] The countermeasure generation unit M315 has a function corresponding to the countermeasure generation unit M15 of the first embodiment. The countermeasure generation unit M315 includes a countermeasure generation unit M315y for vehicles without problems and a countermeasure generation unit M315a for vehicles with problems.

[0059] The non-trouble vehicle countermeasure generation unit M315y is substantially the same as the countermeasure generation unit M15 of the first embodiment. The non-trouble vehicle countermeasure of this embodiment may, as in the first embodiment, propose a change in the control mode, etc., or it may instruct a change in the control mode, etc. Furthermore, the non-trouble vehicle countermeasure of this embodiment may propose changing the speed limit on roads where vehicle driving troubles frequently occur (hereinafter referred to as "trouble-prone roads") or prohibiting passage on trouble-prone roads (hereinafter referred to as "speed limit change, etc."), or it may instruct a speed limit change, etc.

[0060] The troubled vehicle countermeasure generation unit M315a generates countermeasures (hereinafter referred to as "troubled vehicle countermeasures") to allow the troubled vehicle 10a to escape from the vehicle driving trouble or to evacuate the troubled vehicle 10a or its occupants, based on trouble information received from one or more troubled vehicles 10a.

[0061] Measures to help the malfunctioning vehicle 10a escape from its driving trouble include requesting a third party to help it escape (hereinafter referred to as "request for escape"), suggesting or instructing the occupants of the malfunctioning vehicle 10a to change the control mode or request for escape. A request for escape may include having a third party go to the location where the malfunctioning vehicle 10a occurred, or receiving remote advice from a third party regarding the driving method of the malfunctioning vehicle 10a.

[0062] When proposing an evacuation request, the occupants of the vehicle already in trouble 10a may be notified of the name and contact information of the service provider and an estimate of the costs for the request. If proposing to have a third party go to the location where the trouble occurred, the occupants of the vehicle already in trouble 10a may be notified of an estimate of the time required for the third party to arrive at the location where the trouble occurred. If proposing to receive advice from a third party remotely, the occupants of the vehicle already in trouble 10a may be notified of the waiting time required until advice is received from the third party.

[0063] As a measure to evacuate the malfunctioning vehicle 10a and its occupants, it is possible to notify the occupants of the malfunctioning vehicle 10a of the location of the evacuation site (hereinafter referred to as the "evacuation site"), the distance to the evacuation site, and the route to the evacuation site. The evacuation site includes a place to park the malfunctioning vehicle 10a and a place where the occupants of the malfunctioning vehicle 10a will stay overnight. If the evacuation site is the occupants' accommodation, the contact information of the accommodation may also be notified to the occupants.

[0064] Here, we will explain an example of a measure to take when a vehicle is stuck. As a measure to take when a vehicle is stuck, one option is to request assistance from a third-party road service or affiliated shop, or to suggest such assistance.

[0065] Next, we will explain an example of countermeasures for a vehicle that has already experienced a braking problem, specifically when the vehicle's driving trouble is brake fade. Possible countermeasures for a vehicle that has already experienced a braking problem related to brake fade include changing to a control mode that promotes the use of braking forces other than frictional braking and suppresses the use of frictional braking, changing to a driving route that suppresses the generation of braking forces, or suggesting or instructing the stopping of the vehicle 10a that has already experienced a braking problem. Braking forces other than frictional braking can include mechanical braking and regenerative braking.

[0066] The countermeasure transmission unit M319 sets the targets for transmission of countermeasures for unaffected vehicles and countermeasures for already affected vehicles (hereinafter referred to as "vehicle countermeasures") generated by the unaffected vehicle countermeasure generation unit M315y, and transmits the vehicle countermeasures to those targets. The countermeasure transmission unit M319 sets the targets for transmission based on the trouble information and vehicle countermeasures.

[0067] For example, if the vehicle countermeasure is for a vehicle that has not experienced any problems, the countermeasure transmission unit M319 may, based on the location of the problem as trouble information, set a vehicle that has not experienced any problems 10y traveling in the vicinity of the vehicle that has already experienced problems 10a, or a vehicle that has not experienced any problems 10y traveling on the same road as the vehicle that has already experienced problems 10a, as the target for sending suggestions or instructions to change the control mode, etc.

[0068] On the other hand, if the vehicle countermeasure is for a vehicle that has already experienced trouble, the countermeasure transmission unit M319 may set third parties located around the vehicle that has already experienced trouble 10a as targets for sending escape requests, based on the location where the trouble occurred as trouble information.

[0069] Furthermore, if the vehicle countermeasure is for a vehicle without problems, the countermeasure transmission unit M319 may set the transmission target to the vehicle without problems 10y or a third party, depending on the content of the countermeasure for the vehicle without problems. In this case, if the countermeasure for the vehicle without problems proposes or instructs a change in the control mode, etc., the transmission target of the countermeasure transmission unit M319 will be set to the vehicle without problems 10y, and if the countermeasure for the vehicle without problems proposes or instructs a change in the speed limit on a road with frequent problems, etc., the transmission target will be set to a third party such as the police or a road management company.

[0070] On the other hand, if the vehicle countermeasure is for a vehicle that has already experienced trouble, the countermeasure transmission unit M319 may set the transmission target to the vehicle that has already experienced trouble 10a or a third party, depending on the content of the countermeasure for the vehicle that has already experienced trouble. In this case, if the countermeasure for the vehicle that has already experienced trouble proposes or instructs a change in the control mode, etc., or an escape request, the countermeasure transmission unit M319 sets the transmission target to the vehicle that has already experienced trouble 10a, and if the countermeasure for the vehicle that has already experienced trouble requests an escape, the transmission target is set to a third party such as a road service or affiliated store.

[0071] <Client device configuration> The client device 70 includes a client control unit 74 and a client communication unit 75.

[0072] The client communication unit 75 outputs information received via the mobile communication network 302 to the client control unit 74, and transmits the information output from the client control unit 74 via the mobile communication network 302.

[0073] The client control unit 74 is equipped with a CPU and memory. The memory stores a control program. The client control unit 74 functions as the countermeasure execution unit M321 by having the CPU periodically execute the control program.

[0074] The countermeasure execution unit M321 executes processing corresponding to the vehicle countermeasures transmitted from the server device 50. For example, if the vehicle countermeasure is for a vehicle that has not yet experienced trouble, such as proposing changes to the speed limit on roads prone to frequent problems to a third party such as the police or road management company, the countermeasure execution unit M321 will notify the police or road management company of the above proposal. If the vehicle countermeasure is for a vehicle that has already experienced trouble, such as instructing a third party such as a road service company, gas station, or vehicle repair shop to request assistance to get the vehicle out of the vehicle's breakdown, the countermeasure execution unit M321 will request the road service company, gas station, or vehicle repair shop to get the vehicle that has already experienced trouble, 10a, out of the vehicle's breakdown.

[0075] <Vehicle Configuration> The countermeasure execution unit M317 of this embodiment performs actions corresponding to vehicle countermeasures transmitted from the server device 50. The countermeasure execution unit M317 includes a non-trouble vehicle countermeasure execution unit M317y and a troubled vehicle countermeasure execution unit M317a.

[0076] The non-trouble vehicle countermeasure execution unit M317y is a function corresponding to the countermeasure execution unit M17 of the first embodiment. The non-trouble vehicle countermeasure execution unit M317y executes processing according to the non-trouble vehicle countermeasure transmitted from the server device 50.

[0077] The troubled vehicle countermeasure execution unit M317a executes processing according to the troubled vehicle countermeasure transmitted from the server device 50. For example, if the troubled vehicle countermeasure is a suggestion to change the control mode or to request an escape, the troubled vehicle countermeasure execution unit M317a notifies the occupants of the troubled vehicle 10a of the suggested change in the control mode or the suggestion to request an escape. Also, if the troubled vehicle countermeasure is an instruction to change the control mode or the like, the troubled vehicle countermeasure execution unit M317a implements the change in the control mode or the like.

[0078] The configuration of the vehicle 10 in this embodiment is substantially the same as that of the first embodiment, except for the functions described above. <Processing flow for responding to vehicle driving problems> (1) Flow of the trouble information transmission process The trouble information transmission process in this embodiment is substantially the same as the trouble information transmission process in the first embodiment shown in Figure 2. Therefore, a description of this process will be omitted. However, the target of trouble information transmission by the trouble information transmission unit M13 is the server device 50.

[0079] In this embodiment, the vehicle control unit 14 of the vehicle 10a, which is the vehicle 10 that experienced a vehicle driving trouble, corresponds to the first control device. In addition, the server control unit 54 of the server device 50 that receives trouble information transmitted from the vehicle 10a corresponds to the second control device.

[0080] (2) Process flow for generating countermeasures for vehicle driving troubles in the server device Figure 6 is a flowchart showing the process in which the server device 50 receives trouble information transmitted from the troubled vehicle 10a, generates countermeasures for the non-trouble vehicle based on that trouble information, and transmits the non-trouble vehicle countermeasures to the non-trouble vehicle 10y or a third party (hereinafter referred to as the "non-trouble vehicle countermeasure transmission process"). The program corresponding to this process is stored in the memory of the server control unit 54 and executed by the CPU of the server control unit 54.

[0081] The processes in steps S31y and S32y in Figure 6 are substantially the same as those in the first embodiment shown in steps S21 and S22 in Figure 3, respectively. If the server control unit 54 determines in step S31y that it has received trouble information transmitted from the already troubled vehicle 10a, then in step S32y, the non-trouble vehicle countermeasure generation unit M315y generates countermeasures for the non-trouble vehicle based on the trouble information.

[0082] The server control unit 54, using the countermeasure transmission unit M319, sets the transmission target in step S37y based on trouble information and countermeasures for vehicles without problems, and in step S38y transmits countermeasures for vehicles without problems to the transmission target.

[0083] Figure 7 is a flowchart showing the process in which the server device 50 receives trouble information transmitted from the troubled vehicle 10a, generates countermeasures for the troubled vehicle based on that trouble information, and transmits the countermeasures to the troubled vehicle 10a or a third party (hereinafter referred to as the "troubled vehicle countermeasure transmission process"). The program corresponding to this process is stored in the memory of the server control unit 54 and executed by the CPU of the server control unit 54.

[0084] The process in step S31a of Figure 7 is substantially the same as the process in the first embodiment shown in step S21 of Figure 3. If the server control unit 54 determines in step S31a that it has received trouble information transmitted from the already troubled vehicle 10a, it executes the processes from steps S32a to S38a.

[0085] In step S32a, the server control unit 54 generates countermeasures for previously troubled vehicles based on the trouble information using the previously troubled vehicle countermeasure generation unit M315a. The server control unit 54, using the countermeasure transmission unit M319, sets the transmission target in step S37a based on trouble information and countermeasures for vehicles with existing problems, and in step S38a transmits countermeasures for vehicles with existing problems to the transmission target.

[0086] (3) Process flow for implementing countermeasures against vehicle driving troubles in the client device Figure 8 shows the process in which the client device 70 receives vehicle countermeasures transmitted from the server device 50 and executes processing corresponding to those vehicle countermeasures. The program corresponding to this process is stored in the memory of the client control unit 74 and is executed periodically by the CPU of the client control unit 74.

[0087] In step S41, the client control unit 74 determines whether or not the vehicle countermeasures transmitted from the server device 50 have been received. If the client control unit 74 determines that the vehicle countermeasures have not been received (S41: NO), it terminates the current process. If the client control unit 74 determines that the vehicle countermeasures have been received (S41: YES), it proceeds to the process in step S43.

[0088] The processes in steps S43, S44, and S46 in Figure 8 correspond to the processes in steps S23, S24, and S26 in Figure 3, respectively. In step S43, the client control unit 74 determines whether the vehicle countermeasure is a change in the control mode or a suggestion to request escape. If the client control unit 74 determines that the vehicle countermeasure is a change in the control mode or a suggestion to request escape (S43:YES), it proceeds to the process in step S44. On the other hand, if the client control unit 74 determines that the vehicle countermeasure is not a change in the control mode or a suggestion to request escape (S43:NO), it proceeds to the process in step S46.

[0089] In step S44, the client control unit 74 notifies the occupants of the vehicle 10 of the proposed solution via the countermeasure execution unit M317. In step S46, the client control unit 74 executes processing according to the vehicle countermeasures using the countermeasure execution unit M317.

[0090] In this case, the proposal notified to the occupants of vehicle 10 in step S44 may include a request to a third party. For example, if vehicle 10 (the troubled vehicle 10a) becomes stuck, the client device 70 makes a proposal to the occupants of vehicle 10 to ask a third party to help them get out of the stuck state. In such a case, vehicle 10 sends a message to the client device 70 indicating whether or not the occupants are willing to accept the proposal.

[0091] Figure 9 shows the process in the client device 70 where, after notifying the occupants of the vehicle 10 of the proposed content in step S44, the occupants' response to the proposed content is received, and processing is performed according to that response. The program corresponding to this process is stored in the memory of the client control unit 74 and is executed periodically by the CPU of the client control unit 74.

[0092] In step S51, the client control unit 74 determines whether it has received the occupant's intention from the vehicle 10 that notified it of the proposal in step S44. The occupant's intention here refers to whether the occupant accepted the proposal notified by the client device 70.

[0093] In step S55, if the client control unit 74 determines that the occupant of vehicle 10 is willing to accept the proposal (S55: YES), it proceeds to step S56. If the client control unit 74 determines that the occupant of vehicle 10 is not willing to accept the proposal (S55: NO), it terminates the current process.

[0094] In step S56, the client control unit 74 executes processing according to the vehicle countermeasures using the countermeasure execution unit M317. (4) Flowchart for implementing countermeasures against vehicle driving problems in vehicles In a vehicle without problems (vehicle 10y), the process of receiving the countermeasures for the vehicle without problems transmitted from the server device 50 and implementing those countermeasures (hereinafter referred to as the "implementation process for implementing countermeasures for the vehicle without problems") corresponds to the vehicle countermeasure implementation process of the first embodiment. The control program corresponding to this process is stored in the memory of the vehicle control unit 14 and is executed periodically by the CPU of the vehicle control unit 14.

[0095] The vehicle control unit 14 of the trouble-free vehicle 10y determines whether or not it has received the trouble-free vehicle countermeasures from the server device 50. If it determines that the trouble-free vehicle countermeasures have been received, it executes a process that is substantially the same as the process from steps S23 to S26 of the first embodiment shown in Figure 3.

[0096] In the case of a vehicle 10a that has already experienced a problem, the process of receiving the countermeasures for the vehicle that has already experienced a problem transmitted from the server device 50 and implementing those countermeasures (hereinafter referred to as the "implementation process for implementing countermeasures for the vehicle that has already experienced a problem") differs from the implementation process for implementing countermeasures for a vehicle that has not experienced a problem in that the target of the implementation process for a vehicle that has not experienced a problem is a vehicle 10y that has not experienced a problem. However, the flow of the implementation process for implementing countermeasures for the vehicle that has already experienced a problem is substantially the same as the flow of the implementation process for implementing countermeasures for a vehicle that has not experienced a problem.

[0097] The vehicle control unit 14 of the vehicle 10a that has already experienced trouble determines whether or not it has received a troubled vehicle countermeasure from the server device 50. If the vehicle control unit 14 determines that it has not received a troubled vehicle countermeasure, it terminates the current process. However, if it determines that it has received a troubled vehicle countermeasure, it determines whether or not the troubled vehicle countermeasure is a suggestion for changing the control mode or requesting an escape.

[0098] If the vehicle control unit 14 determines that the proposed countermeasure for the malfunctioning vehicle is to change the control mode or to request an escape, the malfunctioning vehicle countermeasure execution unit M317a notifies the occupant of the malfunctioning vehicle 10a of the proposed content. If the vehicle control unit 14 receives confirmation from the occupant that they will accept the proposed content, the malfunctioning vehicle countermeasure execution unit M317a executes the processing corresponding to the malfunctioning vehicle countermeasure.

[0099] If the vehicle control unit 14 determines that the countermeasure for the vehicle that has already experienced trouble is not a change in the control mode or a proposal for an escape request, the vehicle countermeasure execution unit M317a executes processing according to the countermeasure for the vehicle that has already experienced trouble.

[0100] <Operation and Effects of This Embodiment> According to this embodiment, when a vehicle driving trouble occurs in vehicle 10, the vehicle driving trouble is detected, and trouble information related to the vehicle driving trouble is transmitted to the server device 50. When the server device 50 receives the trouble information transmitted from the already troubled vehicle 10a, a vehicle countermeasure is generated based on the trouble information, and the vehicle countermeasure is transmitted to the client device 70 and vehicle 10. When the client device 70 and vehicle 10 receive the vehicle countermeasure, processing corresponding to the vehicle countermeasure is executed.

[0101] Since the countermeasures for vehicles without problems are implemented for vehicles without problems (10y) in this manner, this embodiment has the same effects as the first embodiment for vehicles without problems (10y). Furthermore, since countermeasures for the already malfunctioning vehicle 10a are implemented, according to this embodiment, it is possible to get the already malfunctioning vehicle 10a out of the vehicle driving trouble, or to evacuate the already malfunctioning vehicle 10a and its occupants.

[0102] In the vehicle trouble response system 300, the vehicle 10 and the server device 50 are connected via a mobile communication network 302. Therefore, according to this embodiment, trouble information can be received from vehicles 10 located in a wider area than through vehicle-to-vehicle communication. Furthermore, since this trouble information is aggregated in the server device 50 to generate vehicle countermeasures, high-value-added vehicle countermeasures can be generated.

[0103] (Example of change) The above-described embodiments can be implemented with the following modifications. The above-described embodiments and the following modifications can be combined with each other to the extent that they do not contradict each other technically.

[0104] In the second embodiment, the functions of the trouble detection unit M11, the countermeasure generation unit M15, and the countermeasure execution unit M17 are implemented by the mobile communication device 30. However, some of these functions may be implemented by the mobile communication device 30 and the vehicle 10, or the mobile communication device 30 may be replaced by the vehicle 10.

[0105] For example, the trouble detection unit M11 may detect that a vehicle driving trouble has occurred based on vehicle sensor information in addition to mobile sensor information, or it may detect that a vehicle driving trouble has occurred based on vehicle sensor information instead of mobile sensor information.

[0106] The countermeasure execution unit M17 may display the proposed changes to the control mode, etc., on the vehicle display unit 12 in addition to the mobile display unit 32, or it may display them on the vehicle display unit 12 instead of the mobile display unit 32. Furthermore, the function of the countermeasure execution unit M17 related to proposing changes to the control mode, etc., may be implemented by the mobile control unit 34, while the function related to giving instructions for changing the control mode, etc., may be implemented by the vehicle control unit 14.

[0107] In the third embodiment, the vehicle trouble response system 300 is configured to include a server device 50, a client device 70, and a vehicle 10. However, the vehicle trouble response system does not necessarily have to include the client device 70.

[0108] In the third embodiment, the countermeasure generation unit M315 of the server device 50 includes a countermeasure generation unit M315y for vehicles without problems and a countermeasure generation unit M315a for vehicles with problems. However, the countermeasure generation unit M315 may include either the countermeasure generation unit M315y for vehicles without problems or the countermeasure generation unit M315a for vehicles with problems.

[0109] In the third embodiment, the countermeasure execution unit M317 of the vehicle 10 includes a countermeasure execution unit M317y for vehicles without problems and a countermeasure execution unit M317a for vehicles with problems. However, the countermeasure execution unit M317 may include either the countermeasure execution unit M317y for vehicles without problems or the countermeasure execution unit M317a for vehicles with problems.

[0110] In the third embodiment, the vehicle trouble response system 300 is configured such that the vehicle 10 and the server device 50 are connected in a communicative manner. However, the vehicle trouble response system may also be configured such that a mobile communication device and the server device 50 are connected in a communicative manner instead of the vehicle 10.

[0111] In this case, the mobile communication device is positioned inside the vehicle 10 when the occupants of the vehicle 10 board the vehicle 10. Furthermore, the functions of the trouble detection unit M11, trouble information transmission unit M13, and countermeasure execution unit M317 of the third embodiment are realized by the mobile communication device. In the mobile communication device, the configurations corresponding to the vehicle display unit 12, vehicle operation unit 13, vehicle control unit 14, and vehicle communication unit 15 of the third embodiment are substantially the same as the configurations of the mobile display unit 32, mobile operation unit 33, mobile control unit 34, and mobile communication unit 35 described in the second embodiment, respectively.

[0112] In the third embodiment, the client device 70 is assumed to be installed in police stations, road management companies, road service centers, or affiliated stores. However, the client device 70 may also be a mobile communication device such as a mobile phone or tablet. In this case, the officers, managers, and employees of the police stations, road management companies, road service centers, or affiliated stores can carry the client device 70 with them. Therefore, they can respond quickly to vehicle driving troubles.

[0113] In the third embodiment, the countermeasure execution unit M321 of the client device 70 notifies the occupant of the vehicle 10 of changes to the control mode, etc., or suggestions for an escape request, receives the occupant's intention, and determines whether or not they intend to accept the suggestion. However, the countermeasure execution unit M321 may also instruct the vehicle 10 to perform the above process.

[0114] In the third embodiment, the function of the countermeasure execution unit M317 was explained by illustrating a non-trouble vehicle countermeasure that proposes changes to speed limits on trouble-prone roads to the police or road management companies, acting as third parties. However, the non-trouble vehicle countermeasure may also involve instructing the police or road management companies to change speed limits on trouble-prone roads. In this case, the countermeasure execution unit M317 could change the speed limit on trouble-prone roads or display a no-entry sign for trouble-prone roads using variable signs or electronic display boards on the road.

[0115] The vehicle control unit 14, the mobile unit control unit 34, and the server control unit 54 are not limited to those that include a CPU and ROM to perform software processing. For example, they may include a dedicated hardware circuit to perform hardware processing on at least a portion of what is processed by software in each of the above embodiments.

[0116] <Technical concepts that can be understood from embodiments, etc.> Next, we will describe the technical concepts that can be understood from the above-described embodiments and modifications. (i) The first control device is a mobile communication device, a vehicle system. In this case, the first control device is located inside the vehicle when the occupants board the vehicle.

[0117] (b) The second control device is a vehicle system installed in a vehicle other than the vehicle in which the first control device is installed. Hereafter, the vehicle in which the first control device is installed will be referred to as the first vehicle, and the vehicle other than the first vehicle will be referred to as the second vehicle.

[0118] (h) A vehicle system comprising a second control device located in the second vehicle, which includes a countermeasure execution unit that executes the countermeasures generated by the countermeasure generation unit. (ii) The countermeasure execution unit of the second control device located in the second vehicle is a vehicle system that notifies the occupants of the second vehicle of information regarding the countermeasures generated by the countermeasure generation unit.

[0119] (e) The second control device is a vehicle system installed in a facility of an organization that provides services to the occupants of a vehicle in the event of a vehicle malfunction. (h) A vehicle system in which the trouble information transmission unit of the first control device transmits trouble information to the second control device via vehicle-to-vehicle communication.

[0120] (t) A vehicle system in which the trouble information transmission unit of the first control device transmits trouble information to the second control device via a mobile communication network. (C) The second control device is a vehicle system installed in a facility that provides services to the occupants of a vehicle when a vehicle driving trouble occurs in a vehicle where the first control device is installed.

[0121] (i) A vehicle system comprising a second control device and a countermeasure transmission unit that transmits countermeasures generated by a countermeasure generation unit to a first control device. (Nu) A vehicle system in which the first control device is equipped with a countermeasure execution unit that executes countermeasures transmitted from the second control device.

[0122] (L) A vehicle system comprising a second control device which includes a countermeasure transmission unit that transmits the countermeasures generated by the countermeasure generation unit to a third control device separate from the first and second control devices. (Wo) The third control device is a vehicle system located in a vehicle different from the vehicle in which the first control device is located.

[0123] (Wa) The third control device is a vehicle system installed in a facility of an organization that deals with vehicle driving problems. (c) The third control device is a mobile communication device, a vehicle system.

[0124] (Yo) A vehicle system in which the countermeasure transmission unit of the second control device sets the target for transmission of countermeasures based on at least one of the trouble information transmitted from the first control device and the countermeasures generated by the countermeasure generation unit.

[0125] (t) A control device comprising the above-mentioned vehicle system, comprising: a trouble detection unit that detects when a trouble related to the operation of the vehicle occurs; and a trouble information transmission unit that transmits trouble information related to the trouble detected by the trouble detection unit to the outside of the vehicle.

[0126] (e) A control device comprising the above-mentioned vehicle system, the control device comprising: a trouble information receiving unit that receives trouble information from outside the vehicle; and a countermeasure generation unit that generates countermeasures corresponding to the trouble information received by the trouble information receiving unit.

[0127] (S) A control device equipped with a transmission unit that transmits countermeasures generated by a countermeasure generation unit. [Explanation of symbols]

[0128] 10... Vehicles 10y...Trouble-free vehicle 10a... Vehicles that have already experienced problems 14. Vehicle control unit (first control unit, second control unit) 30…Mobile communication equipment (first control unit, second control unit) 50…Server device (second control unit) 70…Client device (third control unit) 100, 200, 300... Vehicle trouble response system (vehicle system) M11, M211... Trouble detection unit M13, M213... Trouble information transmission unit M15, M215, M315... Countermeasure generation unit M17, M217, M317, M321... Countermeasures Implementation Department M319... Countermeasure transmission unit

Claims

1. A vehicle trouble response system comprising a first control device located inside the vehicle and a second control device located outside the vehicle, which responds to troubles related to the operation of the vehicle, The first control device is A trouble detection unit that detects that the aforementioned trouble has occurred in the vehicle, The system includes a trouble information transmission unit that transmits trouble information related to the trouble detected by the trouble detection unit to the second control device, The second control device is, The system includes a countermeasure generation unit that generates countermeasures corresponding to the trouble information transmitted from the trouble information transmission unit, The countermeasure generation unit generates a countermeasure for non-trouble vehicles to suppress the occurrence of the trouble in non-trouble vehicles where the trouble has not occurred, as the countermeasure. The measures for the non-trouble vehicle include at least one of the following: a proposal to change the control mode in the non-trouble vehicle, and an instruction to change the control mode in the non-trouble vehicle. A vehicle trouble response system characterized by the following features.

2. The trouble detection unit detects at least one of the following as the trouble: a trouble that hinders the driving of the vehicle and a trouble that makes it impossible to drive the vehicle. The vehicle trouble response system according to claim 1.

3. The trouble information transmission unit of the first control device transmits the trouble information, including the location where the trouble occurred, to the second control device. The countermeasure generation unit of the second control device generates countermeasures for vehicles without problems, corresponding to the number of occurrences of the trouble in the same area, based on the location of occurrence as the trouble information received. A vehicle trouble response system according to claim 1 or 2.

4. A vehicle trouble response system comprising a first control device located inside the vehicle and a second control device located outside the vehicle, which responds to troubles related to the operation of the vehicle, The first control device is A trouble detection unit that detects that the aforementioned trouble has occurred in the vehicle, The system includes a trouble information transmission unit that transmits trouble information related to the trouble detected by the trouble detection unit to the second control device, The second control device is, The system includes a countermeasure generation unit that generates countermeasures corresponding to the trouble information transmitted from the trouble information transmission unit, The trouble detection unit detects at least one of the following as a trouble: a trouble that hinders the vehicle's operation, and a trouble that makes the vehicle unable to operate. The countermeasure generation unit generates a countermeasure for a vehicle that has already experienced trouble, which includes at least one of the following: a countermeasure for a vehicle that has already experienced trouble to escape from the trouble, and a countermeasure for a vehicle that has already experienced trouble to evacuate from the trouble. The second control device includes a countermeasure transmission unit that transmits the countermeasures for the troubled vehicle, which have been generated by the countermeasure generation unit, to the troubled vehicle. A vehicle trouble response system characterized by the following features.

5. The countermeasure generation unit generates at least one of the following countermeasures as a countermeasure for the vehicle that has already experienced trouble: a proposal to change the control mode of the vehicle that has already experienced trouble, and an instruction to change the control mode of the vehicle that has already experienced trouble. The vehicle trouble response system according to claim 4.

Images