Vehicle communication system and vehicle communication device

Abstract

The invention provides a vehicle communication system and a vehicle communication device capable of reducing communication cost when transmitting predetermined vehicle data to a server. A communication system (1) is provided with a vehicle (20) and a server (10) capable of communicating with the vehicle (20). The vehicle (20) has a TCU (40) capable of collecting prescribed vehicle data (90) and uploading the same to the server (10). A server (10) has a storage unit (13) that stores vehicle data (90) uploaded from a vehicle (20). A TCU (40) of a vehicle (20) is configured so as to be able to communicate with a server (10) by means of mobile communication, which is amount-based charging data communication, and fixed communication, which is quota-based charging data communication, and in a state in which communication with the server (10) by means of the fixed communication is possible, uploads vehicle data (90) to the server (10) by means of the fixed communication.

Description

Technical Field

[0001] The present invention relates to a vehicle communication system and a vehicle communication device. Background Art

[0002] In recent years, in order to ensure that more people have access to affordable, reliable and sustainable modern energy, research and development related to secondary batteries that contribute to improving energy efficiency have been underway. The secondary battery is mounted on a vehicle, for example, and supplies power to a motor as a drive source.

[0003] In addition, a system for transmitting and receiving data between a communication device provided in a vehicle and a device outside the vehicle has been known in the past. For example, Patent Document 1 discloses a charging system that performs wireless communication between an electric vehicle equipped with a storage battery and a charging station, and the vehicle receives diagnostic information from the charging station.

[0004] Prior Art Documents

[0005] Patent Documents

[0006] Patent Document 1: Japanese Unexamined Patent Application Publication No. 2014-155400 Summary of the Invention

[0007] Problems to be Solved by the Invention

[0008] However, a communication device of a vehicle sometimes collects driving data, data related to a storage battery, etc. and uploads them to an external server in order to manage the vehicle state including fault diagnosis. These data have a large capacity. For example, when uploading from the vehicle to the server via mobile communication which is pay-per-use data communication during the vehicle's driving, the communication cost increases, and the burden on the vehicle user increases. Therefore, there is room for improvement.

[0009] The present invention provides a vehicle communication system and a vehicle communication device capable of reducing communication costs when sending specified vehicle data to a server.

[0010] Means for Solving the Problems

[0011] The present invention provides a vehicle communication system including:

[0012] a vehicle equipped with a storage battery that supplies power to a drive source; and

[0013] a server capable of communicating with the vehicle, wherein

[0014] the vehicle has a communication device capable of collecting specified vehicle data and uploading the vehicle data to the server,

[0015] the server has a server-side storage device that stores the vehicle data uploaded from the vehicle,

[0016] The communication device of the vehicle is configured to be able to communicate with the server through mobile communication as pay-per-use data communication and fixed communication as flat-rate data communication.

[0017] When the communication device of the vehicle is in a state where it can communicate with the server through the fixed communication, the vehicle data is uploaded to the server through the fixed communication.

[0018] In addition, the present invention provides a vehicle communication device provided in a vehicle having a battery that supplies power to a drive source, capable of collecting prescribed vehicle data and uploading the vehicle data to a server, wherein

[0019] the vehicle communication device is configured to be able to communicate with the server through mobile communication as pay-per-use data communication and fixed communication as flat-rate data communication.

[0020] When the vehicle communication device is in a state where it can communicate with the server through the fixed communication, the vehicle data is uploaded to the server through the fixed communication.

[0021] Advantageous Effects of the Invention

[0022] According to the present invention, it is possible to reduce the communication cost when sending prescribed vehicle data to the server. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 is a structural diagram of a communication system 1 according to an embodiment of the present invention.

[0024] Figure 2 is a block diagram showing the structure of a vehicle 20.

[0025] Figure 3 is a flowchart of the upload process of the vehicle data of the TCU 40.

[0026] Figure 4 is a diagram showing a first example of the upload process of the vehicle data 90.

[0027] Figure 5 is a diagram showing a second example of the upload process of the vehicle data 90.

[0028] Figure 6 is a diagram showing a third example of the upload process of the vehicle data 90.

[0029] REFERENCE SIGNS LIST

[0030] 1 Communication system (vehicle communication system)

[0031] 10 Server

[0032] 13 Storage unit (server - side storage device)

[0033] 20 Vehicle

[0034] 21 Battery

[0035] 40 TCU (Communication device)

[0036] 43 Storage unit (vehicle - side storage device)

[0037] 90 Vehicle data

[0038] Period T1 (First period)

[0039] Period T2 (Second period). Detailed implementation manners

[0040] Hereinafter, based on the accompanying drawings, a vehicle communication system and a vehicle communication device according to an embodiment of the present invention will be described.

[0041] (Overall structure of the vehicle communication system)

[0042] Figure 1 is a structural diagram of the communication system 1. The communication system 1 includes a server 10 and a vehicle 20. The server 10 and the vehicle 20 are configured to be able to communicate via a network NW.

[0043] The server 10 is a device that performs information processing with devices (including the vehicle 20) connected to the network NW as clients. The server 10 has: a communication unit 11 that communicates with the devices via the network NW and transmits and receives specified data; a control unit 12 that performs specified processing such as analysis on the received data; and a storage unit 13 that stores the received data. The control unit 12 can be implemented by a computer having a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), I / O, and a bus, etc. The storage unit 13 is implemented by, for example, a non - volatile storage medium and stores various data, programs, etc. The control unit 12 reads, for example, programs stored in the storage unit 13 to perform specified processing.

[0044] The vehicle 20 is an electric vehicle equipped with a battery 21 that supplies power to an electric motor as a drive source. The vehicle 20 is, for example, a battery - powered electric vehicle or a plug - in hybrid vehicle, and is configured to be able to charge the battery 21 by supplying power from a charging device 5 as an external power source. The charging device 5 is provided, for example, in a parking lot of a commercial facility, a charging point, a home, etc.

[0045] The vehicle 20 is configured to be able to communicate with the server 10 via mobile communication, which is pay-per-use data communication, and fixed communication, which is flat-rate data communication. The mobile communication is, for example, a cellular communication method such as 3G (third-generation mobile communication method), 4G (fourth-generation mobile communication method), LTE (Long Term Evolution), 5G (fifth-generation mobile communication method), etc. For example, when the vehicle 20 is traveling, it wirelessly communicates with the server 10 via a base station (not shown). The fixed communication is a communication method that uses a fixed communication line with a flat rate. For example, when the vehicle 20 is connected to the charging device 5 via a charging cable for charging, it wirelessly connects to the server 10 using the fixed communication line of the charging device 5. In addition, for example, when the vehicle 20 is parked at home, it wirelessly communicates with the server 10 using Wi-Fi (registered trademark) or the like connected to the fixed communication line subscribed at home.

[0046] (Structure of the vehicle)

[0047] Figure 2 It is a block diagram showing the structure of the vehicle 20. The vehicle 20 has, for example, an HMI (Human Machine Interface) 22, a navigation device 23, an ignition sensor 24, a vehicle sensor 25, a battery sensor 26, a plurality of ECUs (Electronic Control Units) 30, and a TCU (Telematics Control Unit) 40, which are configured to be able to communicate with each other via the in-vehicle network 28. The in-vehicle network 28 is, for example, a multi-communication line such as a CAN (Controller Area Network) communication line, a serial communication line, or a wireless communication network.

[0048] The HMI 22 presents various information to the occupants of the vehicle 20 and at the same time receives input operations from the occupants. The HMI 22 includes various display devices, speakers, buzzers, touch panels, switches, buttons, etc.

[0049] The navigation device 23 includes, for example, a GNSS (Global Navigation Satellite System) receiver 23a and a navigation HMI 23b. The navigation device 23 stores map information in a storage device such as an HDD (Hard Disk Drive) or a flash memory. The GNSS receiver 23a determines the position of the vehicle 20 based on the signals received from GNSS satellites. The navigation HMI 23b includes a display device, a speaker, a touch panel, buttons, etc. The navigation HMI 23b may be partially or fully shared with the above-mentioned HMI 22.

[0050] The ignition sensor 24 is a sensor that detects whether the ignition power supply of the vehicle 20 is on or off. The ignition sensor 24 outputs data indicating whether the ignition power supply is on or off to a specified ECU 30.

[0051] The vehicle sensor 25 includes a vehicle speed sensor that detects the traveling speed of the vehicle 20 (also simply referred to as "vehicle speed"), an acceleration sensor that detects acceleration, an angular velocity sensor that detects the angular velocity about the vertical axis, an azimuth sensor that detects the orientation of the vehicle 20, and the like. In addition, the vehicle sensor 25 also includes sensors that detect driving torque, accelerator opening, brake pedal force, and the like.

[0052] The battery sensor 26 includes a current sensor that detects the current flowing out of the battery 21, a voltage sensor that detects the voltage of the battery 21, and the like. The detection values of the current sensor and the voltage sensor are used, for example, to calculate the state of charge (State of Charge: hereinafter referred to as SOC) of the battery 21. In addition, the battery sensor 26 may also include a temperature sensor that detects the temperature of the battery 21.

[0053] Each ECU 30 includes, for example, a processing unit 32 and a storage unit 33, and controls the vehicle 20 and various devices provided in the vehicle 20. The processing unit 32 has a data acquisition unit 32a and a data output unit 32b as functional units. The data acquisition unit 32a acquires the detection results of the ignition sensor 24, the vehicle sensor 25, the battery sensor 26, etc., and stores them in the storage unit 33. Specifically, the data acquisition unit 32a acquires the on or off of the ignition switch, vehicle speed, acceleration, angular acceleration, driving torque, accelerator opening, brake pedal force, and the SOC of the battery 21, etc., based on the detection results of the respective sensors 24 to 26. The data output unit 32b sends various data stored in the storage unit 33 to the TCU 40 via the in-vehicle network 28 based on an instruction from the TCU 40.

[0054] The TCU 40 communicates with the server 10 via the network NW. The TCU 40 has a communication unit 41, a processing unit 42, and a storage unit 43.

[0055] The communication unit 41 has a mobile communication unit 41a and a fixed communication unit 41b. The mobile communication unit 41a is equipped with communication hardware related to the communication method of the above-mentioned pay-per-use data communication, and performs wireless communication with the server 10 via the network NW under the control of the processing unit. The fixed communication unit 41b is equipped with communication hardware related to the communication method using the above-mentioned flat-rate fixed communication line, and performs wireless communication with the server 10 via the network NW under the control of the processing unit 42.

[0056] The processing unit 42 is, for example, a CPU, and has a communication control unit 42a and a collection unit 42b as functional units. The communication control unit 42a controls the communication unit 41 based on the data collection setting file 80 transmitted from the server 10. The collection unit 42b collects the specified vehicle data 90 from each ECU 30 based on the data collection setting file 80, and uploads it to the server 10 at a specified timing.

[0057] The data collection setting file 80 is a file that specifies the type of data to be collected, the timing of collection, the timing of uploading the collected data to the server 10, etc. The data collection setting file 80 is transmitted from the server 10 to the vehicle 20 at an arbitrary timing in a state where the server 10 and the vehicle 20 can communicate, and is stored, for example, in the storage unit 43 of the TCU 40.

[0058] In the present embodiment, the vehicle data 90 refers to non-control data that is not used for the control operation of the vehicle 20, and in principle, is data that does not need to be immediately uploaded to the server 10 after being collected by the collection unit 42b. The vehicle data 90 is data with a large capacity. The vehicle data 90 may also include, for example, diagnostic information for diagnosing the states of various devices provided in the vehicle 20. The specific content of the vehicle data 90 will be described later.

[0059] The storage unit 43 has a non-volatile storage area for storing programs and data non-volatilely. The storage unit 43 stores non-volatilely the programs executed by the processing unit 42, the aforementioned vehicle data 90, the data collection setting file 80, etc. In addition, the storage unit 43 may include non-volatile storage devices such as HDDs and SSDs (Solid State Drives).

[0060] (Upload processing to the server)

[0061] As described above, since the vehicle data 90 is data with a large capacity, when the TCU 40 uploads the vehicle data 90 collected by the collection unit 42b to the server 10 via mobile communication, the communication cost increases compared to fixed communication. In addition, when the vehicle 20 is in motion, the communication state of mobile communication changes every moment, so the upload of the vehicle data 90 based on mobile communication easily becomes unstable.

[0062] Therefore, when the TCU 40 is in a state where it can communicate with the server 10 through fixed communication, it sends the vehicle data 90 to the server 10 through fixed communication. Specifically, in the data collection setting file 80 sent from the server 10, as an upload condition of the data, it is defined in principle that the vehicle data 90 is uploaded to the server 10 only when in a state where it can communicate with the server 10 through fixed communication. The TCU 40 uploads the vehicle data 90 to the server 10 in accordance with the upload condition defined in the data collection setting file 80 when in a state where it can communicate with the server 10 through fixed communication. Thereby, the communication cost can be reduced. In addition, the vehicle data 90 can be stably uploaded to the server 10.

[0063] Figure 3 FIG. 4 shows an example of a flowchart of the upload process in which the TCU 40 uploads the vehicle data 90 to the server 10. The TCU 40 repeatedly executes this flowchart at a prescribed control cycle, for example.

[0064] The TCU 40 determines whether fixed communication can be performed (step S11). If fixed communication cannot be performed (step S11: NO), the TCU 40 ends this flowchart. At this time, if there is collected vehicle data 90, the TCU 40 continuously stores the vehicle data 90 in the storage unit 43.

[0065] If fixed communication can be performed (step S11: YES), the TCU 40 determines whether there is collected vehicle data 90 (step S12). If there is no collected vehicle data 90 (step S12: NO), the TCU 40 ends this flowchart.

[0066] If there is collected vehicle data 90 (step S12: YES), the TCU 40 uploads the vehicle data 90 to the server 10 through fixed communication (step S13).

[0067] After uploading the vehicle data 90, the TCU 40 deletes the vehicle data 90 stored in the storage unit 43 (step S14). Thereby, it is possible to prevent a large amount of vehicle data from being continuously stored in the storage unit 43 and suppress the capacity of the storage unit 43 from being oppressed.

[0068] Figure 4This is a diagram showing the first example of the upload process of vehicle data 90 to the server 10. In the first example, the vehicle data 90 is data collected before and after the timing t1 when the change in the SOC of the battery 21 is large. When the vehicle 20 is running, if there is a timing t1 when the change in the SOC of the battery 21 is larger compared to other times, the TCU 40 collects data including battery-related information and driving-related information during a specified period T1 including the timing t1 as the vehicle data 90. Here, the specified period T1 is, for example, a period of 15 seconds before and after the timing t1, and the time interval for collecting data is from 10 [ms] to 1 [s]. In addition, various data constituting the vehicle data 90 are data always acquired by the data acquisition unit 32a of the ECU 30 at a specified time interval during the start-up of the vehicle 20, and are data stored for at least a specified period. Therefore, the TCU 40 can also collect the vehicle data 90 before the timing t1.

[0069] The driving-related information is, for example, information including at least one of the time-varying information of vehicle speed, acceleration, angular acceleration, driving torque, accelerator opening, and brake pedal force during the period T1, and the driving location information. Additionally, the driving-related information may also include information on the outside air temperature. The battery-related information is information including at least the time-varying information of the SOC of the battery 21 during the period T1. Since the vehicle data 90 including such time-varying information has a large capacity, for example, when the vehicle 20 uploads it to the server 10 via mobile communication during driving, the communication cost may increase and the upload may fail.

[0070] When the TCU 40 is not in a state where it can communicate with the server 10 via fixed communication, it continuously stores the vehicle data 90 collected during the period T1 in the storage unit 43. And the TCU 40, for example, when the vehicle 20 is parked at home and becomes in a state where it can communicate with the server 10 via Wi-Fi connected to a fixed communication line, uploads the vehicle data 90 stored in the storage unit 43 to the server 10 via fixed communication. Thereby, the communication cost can be reduced, and in addition, the vehicle data 90 can be stably uploaded to the server 10.

[0071] The vehicle data 90 during period T1 can also be used to improve the accuracy of calculating the cruising range of the vehicle 20. Specifically, the server 10 learns the calculation logic for calculating the change amount of the SOC of the battery 21 corresponding to the driving behavior of the user of the vehicle 20 based on the vehicle data 90 uploaded from the vehicle 20. The server 10 calculates the cruising range of the vehicle 20 based on the change amount of the SOC of the battery 21 calculated by the calculation logic. By preparing calculation logics that are carefully customized for each user, the cruising range can be calculated with high accuracy according to different users. In addition, it can also be configured such that the server 10 sends the learned calculation logic to the vehicle 20, and the vehicle 20 calculates the cruising range.

[0072] The highly accurate cruising range calculated in this way can be displayed on the display devices provided in the HMI 22 of the vehicle 20 and the navigation HMI 23b, or on the specified application program screen of the portable terminal used by the user. It can also be displayed on the map. Specifically, it is displayed on the map as an area where it is highly likely to reach with the remaining amount of the current battery 21.

[0073] In addition, the vehicle data 90 during period T1 can also be used to improve the locations, roads, or facilities where the SOC of the battery 21 decreases. Specifically, based on the vehicle data 90 uploaded from the vehicle 20, the server 10 determines the locations (such as roads and facilities) where the vehicle 20 travels at the timing t1 when the SOC decreases significantly, and analyzes the tendencies of the slope, curvature, road surface material, etc. at the locations where the SOC decreases significantly. Thereby, the operator of the server 10 can provide the analysis results to the local relevant departments, etc., which helps to improve the roads and facilities where the SOC may decrease significantly.

[0074] Figure 5 It is a diagram showing a second example of the upload process of the vehicle data 90. In the second example, the vehicle data 90 is data collected when the vehicle 20 starts. Specifically, the vehicle data 90 is data including start-up information obtained during a period T2 from the timing t2 when the ignition of the vehicle 20 is turned on until after a specified time (for example, 15 seconds). The TCU 40 collects the vehicle data 90 obtained during the period T2. The time interval for collecting data is, for example, from 10 [ms] to 1 [s].

[0075] The start-up information is, for example, information including at least one of the temperature, charge state, time-varying information of current, and time-varying information of voltage of the battery 21 obtained during the period T2. In addition, the start-up information may also include information related to the state of the vehicle 20, such as the temperature of the vehicle 20. Since the vehicle data 90 including such time-varying information has a large capacity, if it is uploaded to the server 10 via mobile communication, the communication cost may increase and the upload may fail.

[0076] When the TCU 40 is not in a state where it can communicate with the server 10 via fixed communication, the vehicle data 90 obtained during the period T2 at the start of the vehicle 20 is continuously stored in the storage unit 43. And, for example, when the vehicle 20 is parked at home and becomes in a state where it can communicate with the server 10 via Wi-Fi connected to a fixed communication line, the vehicle data 90 stored in the storage unit 43 is uploaded to the server 10 via fixed communication. Thereby, communication costs can be reduced, and in addition, the vehicle data 90 can be stably uploaded to the server 10.

[0077] The vehicle data 90 including start-up information can also be used, for example, to determine the occurrence of an abnormality in the vehicle 20. Specifically, the server 10 communicates with a plurality of vehicles via the network NW, and saves the vehicle data 90 including the start-up information of each vehicle as big data in the storage unit 13. The server 10 determines the vehicle in which an abnormality has occurred based on the start-up information of the plurality of vehicles.

[0078] Figure 6 It is a diagram showing a third example of the upload process of the vehicle data 90. In the third example, the vehicle data 90 is data collected when the vehicle 20 is connected to the charging device 5. That is, the vehicle 20 starts collecting the vehicle data 90 on the occasion of charging by the charging device 5. The vehicle data 90 is information including, for example, the temperature of the aforementioned storage battery 21, the charging state, the information on the change over time of the current, and the information on the change over time of the voltage. In addition, the vehicle data 90 may also include various data stored in each ECU 30 during the running of the vehicle 20. The TCU 40 performs wired communication with the charging device 5 via the communication line of the charging cable provided in the charging device 5, and uploads the vehicle data 90 to the server 10 using the fixed communication line of the charging device 5. In addition, the TCU 40 may communicate with the charging device 5 by wireless communication instead of wired communication, and in this case, the vehicle data 90 is also uploaded to the server 10 using the fixed communication line of the charging device 5.

[0079] In addition, in the third example, when other vehicle data 90 has already been stored in the storage unit 43, in addition to the vehicle data 90 that starts to be collected on the occasion of charging by the charging device 5, the other vehicle data 90 that has already been collected can also be uploaded to the server 10 using the fixed communication line of the charging device 5.

[0080] (Modification example)

[0081] In the above-described embodiment, the TCU 40 uploads the vehicle data 90 to the server 10 only when it is in a state where it can communicate with the server 10 via fixed communication, in principle, based on the data upload conditions defined in the data collection setting file 80, but it is not limited to this.

[0082] For example, when the TCU 40 has not been connected to the fixed communication line for a long time, the state where the vehicle data 90 stored in the storage unit 43 is not uploaded to the server 10 continues for a long time, or the data capacity of the vehicle data 90 stored in the storage unit 43 becomes large. Therefore, it is also possible to define an upper limit value of the connection standby time to the fixed communication line and / or an upper limit value of the cache amount in the data collection setting file 80. When the connection standby time to the fixed communication line and / or the cache amount exceeds the upper limit value, the TCU 40 can also upload the vehicle data 90 to the server 10 via mobile communication.

[0083] In addition, for example, in the data collection setting file 80, information with a capacity smaller than a specified threshold among the information included in the vehicle data 90 can also be defined to be immediately uploaded to the server 10 via mobile communication after being collected.

[0084] In addition, for example, when there is an instruction to immediately collect and / or upload the vehicle data 90 from the server 10 or the like, the TCU 40 can also immediately collect and / or upload the vehicle data 90 to the server 10 via mobile communication.

[0085] As described above, an embodiment of the present invention has been described with reference to the accompanying drawings, but the present invention is of course not limited to this embodiment. Obviously, those skilled in the art can conceive of various modification examples or correction examples within the scope described in the technical solution, and it should be understood that these modification examples and correction examples also of course belong to the technical scope of the present invention. In addition, within the scope not departing from the gist of the invention, the constituent elements in the above-described embodiment can be arbitrarily combined.

[0086] For example, several specific examples of the vehicle data 90 that is uploaded to the server 10 via fixed communication in principle are given in the foregoing embodiment, but in addition to the foregoing specific examples, it can also include various information. For example, the vehicle data 90 can also include information such as image data of an in-vehicle camera and shape positioning data of a radar, which have a large capacity and do not require immediate upload.

[0087] At least the following matters are described in this specification. In parentheses, corresponding constituent elements, etc. in the above-described embodiment are shown as an example, but the present invention is not limited thereto.

[0088] (1) A vehicle communication system (communication system 1), comprising:

[0089] A vehicle (vehicle 20) equipped with a storage battery (storage battery 21) that supplies power to a drive source; and

[0090] A server (server 10) capable of communicating with the vehicle,

[0091] The vehicle has a communication device (TCU 40) that can collect specified vehicle data (vehicle data 90) and upload the vehicle data to the server.

[0092] The server has a server-side storage device (storage unit 13) that stores the vehicle data uploaded from the vehicle.

[0093] The communication device of the vehicle is configured to be able to communicate with the server via mobile communication as pay-per-use data communication and fixed communication as flat-rate data communication.

[0094] When the communication device of the vehicle is in a state where it can communicate with the server via fixed communication, the vehicle data is uploaded to the server via fixed communication.

[0095] According to (1), by uploading vehicle data to the server via fixed communication with flat-rate charging instead of mobile communication with pay-per-use charging, communication costs can be reduced.

[0096] (2) The vehicle communication system according to (1), wherein

[0097] The vehicle further has a vehicle-side storage device (storage unit 43) that stores the vehicle data.

[0098] When the communication device of the vehicle is not in a state where it can communicate with the server via fixed communication, the vehicle data is continuously stored in the vehicle-side storage device.

[0099] According to (2), when not in a state where it can communicate with the server via fixed communication, instead of uploading vehicle data to the server via mobile communication, it is continuously stored in the vehicle-side storage device, so communication costs can be reduced.

[0100] (3) The vehicle communication system according to (2), wherein

[0101] The vehicle data includes driving-related information related to the driving of the vehicle and battery-related information related to the battery during a first period (period T1) including timing when the state of charge (SOC) of the battery changes significantly.

[0102] According to (3), the vehicle data obtained during the first period including timing when the state of charge of the battery changes significantly is stored in the server, so the server can improve the calculation accuracy of the available driving range based on the vehicle data or analyze the location where the state of charge changes.

[0103] (4)The vehicle communication system according to (3), wherein

[0104] the driving-related information includes at least one of information on the change over time of vehicle speed, acceleration, angular acceleration, driving torque, accelerator opening, brake pedal force, and driving location information.

[0105] the battery-related information includes at least information on the change over time of the state of charge of the battery.

[0106] According to (4), even if the vehicle data is large-capacity data including information on the change over time, the communication device uploads the vehicle data to the server through fixed communication with a flat rate instead of mobile communication with a per-volume charge, so the communication cost can be reduced. In addition, when the driving-related information includes driving location information, the server can determine the location where the change in the state of charge of the battery is large and utilize improvement measures at that location.

[0107] (5)The vehicle communication system according to (3) or (4), wherein

[0108] the server learns the calculation logic for calculating the change amount of the state of charge of the battery corresponding to the driving behavior of the user of the vehicle or the driving path of the vehicle based on the vehicle data uploaded from the vehicle.

[0109] the server or the vehicle calculates the remaining travel distance of the vehicle based on the change amount of the state of charge of the battery calculated by the calculation logic.

[0110] According to (5), the server can accurately calculate the remaining travel distance based on the stored information. In addition, the remaining travel distance customized for each user of the vehicle can be calculated.

[0111] (6)The vehicle communication system according to any one of (1) to (5), wherein

[0112] the vehicle data includes start-up information obtained during a second period (period T2) from the start of the vehicle to after a specified time has elapsed.

[0113] According to (6), the information obtained at the start of the vehicle, where behavior changes are likely to be manifested, can be uploaded to the server through fixed communication. Thus, the server can control the vehicle with high precision.

[0114] (7)The vehicle communication system according to (6), wherein

[0115] the start-up information includes at least one of information on the change over time of the temperature, state of charge, current, and voltage of the battery obtained during the second period.

[0116] According to (7), it is possible to upload information related to the battery obtained at the start of the vehicle, where behavior changes are easily manifested, to the server via fixed communication. As a result, the server can control the battery with high precision.

[0117] (8) The vehicle communication system according to (6) or (7), wherein

[0118] the server determines the vehicle in which an abnormality has occurred based on the start-up information uploaded from multiple vehicles.

[0119] According to (8), it is possible to determine the vehicle in which an abnormality has occurred based on big data having start-up information of multiple vehicles.

[0120] (9) The vehicle communication system according to any one of (1) to (8), wherein

[0121] the vehicle data includes diagnostic information for diagnosing the state of equipment provided in the vehicle.

[0122] According to (9), it is possible to upload the diagnostic information, which is non-control data not used for vehicle control actions, to the server via fixed communication.

[0123] (10) The vehicle communication system according to any one of (2) to (9), wherein

[0124] after the communication device uploads the vehicle data stored in the vehicle-side storage device to the server via the fixed communication, it deletes the vehicle data from the vehicle-side storage device.

[0125] According to (10), it is possible to prevent the data capacity of the vehicle-side storage device from being overloaded.

[0126] (11) A vehicle communication device (TCU40) provided in a vehicle (vehicle 20) having a battery (battery 21) that supplies power to a drive source, capable of collecting prescribed vehicle data (vehicle data 90) and uploading the vehicle data to a server (server 10), wherein

[0127] the vehicle communication device is configured to be able to communicate with the server via mobile communication, which is pay-per-use data communication, and fixed communication, which is flat-rate data communication,

[0128] when the vehicle communication device is in a state where it can communicate with the server via the fixed communication, it uploads the vehicle data to the server via the fixed communication.

[0129] According to (11), vehicle data is uploaded to the server through fixed communication with a flat rate rather than mobile communication with a pay-per-use rate, thereby reducing communication costs.

Claims

1. A vehicle communication system comprising: a vehicle equipped with a battery for supplying electric power to a driving source; and A server capable of communicating with the vehicle, wherein The vehicle has a communication device capable of collecting predetermined vehicle data and uploading the vehicle data to the server, The server has a server-side storage device for storing the vehicle data uploaded from the vehicle, The communication device of the vehicle is configured to be able to communicate with the server via mobile communication as a pay-per-use data communication and fixed communication as a flat-rate data communication, When the communication device of the vehicle is in a state capable of communicating with the server through the fixed communication, the communication device of the vehicle uploads the vehicle data to the server through the fixed communication.

2. The vehicle communication system according to claim 1, wherein: The vehicle further comprises a vehicle-side storage device storing the vehicle data. When the communication device of the vehicle is not in a state capable of communicating with the server through the fixed communication, the communication device of the vehicle continues to store the vehicle data in the vehicle-side storage device.

3. The vehicle communication system according to claim 2, wherein: The vehicle data includes travel-related information related to travel of the vehicle in a first period including a timing when a change in the state of charge of the battery is large, and battery-related information related to the battery.

4. The vehicle communication system according to claim 3, wherein: The driving-related information includes at least one of vehicle speed, acceleration, angular acceleration, driving torque, accelerator opening, time-varying information of brake pedal force, and driving location information. The storage battery related information includes at least information on changes over time in the state of charge of the storage battery.

5. The vehicle communication system according to claim 3, wherein: The server learns calculation logic for calculating a change in the state of charge of the battery according to a driving behavior of a user of the vehicle or a travel path of the vehicle based on the vehicle data uploaded from the vehicle, The server or the vehicle calculates a cruising range of the vehicle based on the amount of change in the state of charge of the battery calculated by the calculation logic.

6. The vehicle communication system according to any one of claims 1 to 5, wherein: The vehicle data includes startup information acquired during a second period from startup of the vehicle to a lapse of a predetermined time.

7. The vehicle communication system according to claim 6, wherein: The startup information includes at least one of the temperature, the state of charge, the temporal change information of the current, and the temporal change information of the voltage of the battery acquired during the second period.

8. The vehicle communication system according to claim 6, wherein: The server identifies a vehicle in which an abnormality has occurred based on the startup information uploaded from a plurality of vehicles.

9. The vehicle communication system according to any one of claims 1 to 5, wherein: The vehicle data includes diagnostic information for diagnosing a state of equipment included in the vehicle.

10. The vehicle communication system according to any one of claims 2 to 5, wherein: The communication device deletes the vehicle data stored in the vehicle-side storage device from the vehicle-side storage device after transmitting the vehicle data to the server via the fixed communication.

11. A vehicle communication device, which is provided in a vehicle having a battery for supplying electric power to a driving source, and is capable of collecting predetermined vehicle data and uploading the vehicle data to a server, wherein: The vehicle communication device is configured to be able to communicate with the server via mobile communication as a pay-per-use data communication and fixed communication as a flat-rate data communication, The vehicle communication device uploads the vehicle data to the server through the fixed communication when the vehicle communication device is in a state capable of communicating with the server through the fixed communication.

Images