Vehicle communication system and vehicle communication apparatus

Abstract

To provide a vehicle communication system and a vehicle communication apparatus which can reduce communication costs upon transmitting prescribed vehicle data to a server.SOLUTION: A communication system 1 comprises a vehicle 20 and a server 10 which can communicate with the vehicle 20. The vehicle 20 includes a TCU 40 which can collect prescribed vehicle data 90 and upload the same to the server 10. The server 10 includes a storage unit 13 which stores the vehicle data 90 uploaded from the vehicle 20. The TCU 40 of the vehicle 20 is configured to communicate with the server 10 by mobile communication as metered-rate data communication and fixed-line communication as fixed-rate data communication, and uploads the vehicle data 90 to the server 10 by the fixed-line communication when it is in a communicable state with the server 10 by the fixed-line communication.SELECTED DRAWING: Figure 2

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 enable more people to access affordable, reliable, sustainable, and advanced energy, research and development on secondary batteries that contribute to energy efficiency have been carried out. Secondary batteries are mounted, for example, on vehicles and supply power to motors that are drive sources.

[0003] Also, conventionally, a system for transmitting and receiving data between a communication device provided in a vehicle and a device outside the vehicle is known. For example, Patent Document 1 discloses a charging system that performs wireless communication between an electric vehicle equipped with a battery and a charging stand, and the vehicle receives diagnostic information of the charging stand.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] By the way, a vehicle communication device may collect data such as driving data and battery-related data for managing the vehicle state including, for example, fault diagnosis, and upload it to an external server. These data are large in volume. For example, when uploaded from the vehicle to the server by mobile communication, which is usage-based data communication during vehicle travel, the communication cost increases and the burden on the vehicle user increases, so there is room for improvement.

[0006] The present invention provides a vehicle communication system and a vehicle communication device that can reduce communication costs when transmitting predetermined vehicle data to a server.

Means for Solving the Problem

[0007] The present invention relates to a vehicle communication system including a vehicle equipped with a battery that supplies power to a drive 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 it 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 by mobile communication which is metered data communication and fixed communication which is flat-rate data communication, and when it is in a state where it can communicate with the server by the fixed communication, uploads the vehicle data to the server by the fixed communication.

[0008] Also, the present invention relates to a vehicle communication device provided in a vehicle having a battery that supplies power to a drive source, capable of collecting predetermined vehicle data and uploading it to a server, is configured to be able to communicate with the server by mobile communication which is metered data communication and fixed communication which is flat-rate data communication, and when it is in a state where it can communicate with the server by the fixed communication, uploads the vehicle data to the server by the fixed communication.

Advantages of the Invention

[0009] According to the present invention, communication costs can be reduced when transmitting predetermined vehicle data to a server.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Embodiments for Carrying Out the Invention

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

[0012] (Overall Configuration of Vehicle Communication System) FIG. 1 is a configuration 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 communicable via a network NW.

[0013] 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 device via the network NW and transmits and receives predetermined data, a control unit 12 that executes predetermined processing such as analysis on the received data, and a storage unit 13 that stores the received data. The control unit 12 may be realized by a computer including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), an I / O, and a bus. The storage unit 13 is realized by including, for example, a non-volatile storage medium and stores various data and programs. The control unit 12 reads, for example, a program stored in the storage unit 13 and performs predetermined processing.

[0014] The vehicle 20 is an electric vehicle equipped with a battery 21 that supplies power to an electric motor serving as a drive source. The vehicle 20 is, for example, a battery electric vehicle or a plug-in hybrid vehicle, and is configured such that the battery 21 can be charged by being supplied with power from a charging facility 5 serving as an external power source. The charging facility 5 is provided, for example, in a parking lot of a commercial facility, a charging spot, a home, or the like.

[0015] The vehicle 20 is configured to be able to communicate with the server 10 by mobile communication, which is metered 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., and wirelessly communicates with the server 10 via a base station (not shown) while the vehicle 20 is running, for example. The fixed communication is a communication method using a flat-rate fixed communication line. For example, when the vehicle 20 is connected to the charging facility 5 via a charging cable and being charged, it wirelessly connects to the server 10 using the fixed communication line of the charging facility 5. Also, 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 a fixed communication line contracted at home.

[0016] (Configuration of the vehicle) FIG. 2 is a block diagram showing the configuration 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, and these are configured to be able to communicate with each other via an in-vehicle network 28. The in-vehicle network 28 is, for example, a multiplex communication line such as a CAN (Controller Area Network) communication line, a serial communication line, or a wireless communication network.

[0017] The HMI 22 presents various information to the passengers of the vehicle 20 and accepts input operations by the passengers. The HMI 22 includes various display devices, speakers, buzzers, touch panels, switches, keys, etc.

[0018] 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 identifies the position of the vehicle 20 based on signals received from GNSS satellites. The navigation HMI 23b includes a display device, a speaker, a touch panel, keys, etc. The navigation HMI 23b may be partially or fully shared with the aforementioned HMI 22.

[0019] 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 predetermined ECU 30.

[0020] The vehicle sensor 25 includes a vehicle speed sensor that detects the traveling speed (also referred to as "vehicle speed") of the vehicle 20, an acceleration sensor that detects acceleration, an angular velocity sensor that detects the angular velocity around the vertical axis, a direction sensor that detects the direction of the vehicle 20, etc. The vehicle sensor 25 also includes sensors that detect drive torque, accelerator opening, brake pedal force, etc.

[0021] The battery sensor 26 includes a current sensor that detects the current flowing from the battery 21, a voltage sensor that detects the voltage of the battery 21, etc. The detection values by the current sensor and the voltage sensor are used, for example, for calculating the state of charge (hereinafter referred to as SOC) of the battery 21. The battery sensor 26 may also include a temperature sensor that detects the temperature of the battery 21.

[0022] 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 detection results from an ignition sensor 24, a vehicle sensor 25, a battery sensor 26, etc., and stores them in the storage unit 33. Specifically, the data acquisition unit 32a acquires ON / OFF of ignition, vehicle speed, acceleration, angular acceleration, drive torque, accelerator opening, brake pedal force, and SOC of the battery 21, etc., based on the detection results of the respective sensors 24 to 26. The data output unit 32b transmits various data stored in the storage unit 33 to the TCU 40 via the in-vehicle network 28 based on a command from the TCU 40.

[0023] 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.

[0024] The communication unit 41 has a mobile communication unit 41a and a fixed communication unit 41b. The mobile communication unit 41a includes communication hardware related to the communication method of mobile communication, which is the above-mentioned per-volume data communication, and performs wireless communication with the server 10 via the network NW according to the control of the processing unit. The fixed communication unit 41b includes 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 according to the control of the processing unit 42.

[0025] 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 predetermined vehicle data 90 from each ECU 30 based on the data collection setting file 80, and uploads it to the server 10 at a predetermined timing.

[0026] The data collection setting file 80 is a file that defines the types 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 with each other, and is stored, for example, in the storage unit 43 of the TCU 40.

[0027] In this embodiment, the vehicle data 90 refers to non-control data that is not used for the control operation of the vehicle 20, and is data that does not need to be immediately uploaded to the server 10 after being collected by the collection unit 42b in principle. The vehicle data 90 is relatively large-capacity data. The vehicle data 90 may 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.

[0028] The storage unit 43 has a non-volatile storage area for storing programs and data in a non-volatile manner. The storage unit 43 stores programs executed by the processing unit 42, the vehicle data 90 and the data collection setting file 80 described above, etc. in a non-volatile manner. Further, the storage unit 43 may include a non-volatile storage device such as an HDD or an SSD (Solid State Drive).

[0029] (Upload processing to the server) As described above, since the vehicle data 90 is relatively large-capacity data, when the TCU 40 uploads the vehicle data 90 collected by the collection unit 42b to the server 10 by mobile communication, the communication cost increases compared to fixed communication. Further, when the vehicle 20 is running, the communication state of mobile communication can change moment by moment, so the upload of the vehicle data 90 by mobile communication is likely to become unstable.

[0030] Therefore, when the TCU 40 is in a state where it can communicate with the server 10 via fixed communication, the vehicle data 90 is transmitted to the server 10 via fixed communication. Specifically, in the data collection setting file 80 transmitted from the server 10, as an upload condition for data, it is defined that the vehicle data 90 is uploaded to the server 10 only when it is in a state where it can communicate with the server 10 via fixed communication in principle. The TCU 40 uploads the vehicle data 90 to the server 10 via fixed communication according to the upload condition defined in the data collection setting file 80 when it is in a state where it can communicate with the server 10 via fixed communication. Thereby, the communication cost can be reduced. Also, the vehicle data 90 can be stably uploaded to the server 10.

[0031] FIG. 3 shows an example of a flowchart of an upload process for uploading vehicle data 90 to the server 10 by the TCU 40. The TCU 40 repeats the execution of this flowchart, for example, at a predetermined control cycle.

[0032] The TCU 40 determines whether fixed communication is possible (step S11). If fixed communication is not possible (step S11: NO), the TCU 40 ends this flowchart. At this time, if there is collected vehicle data 90, the TCU 40 continues to store the vehicle data 90 in the storage unit 43.

[0033] If fixed communication is possible (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.

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

[0035] 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 suppress a large amount of vehicle data from being continuously stored in the storage unit 43 and the capacity of the storage unit 43 from being compressed.

[0036] FIG. 4 is a diagram showing a first example of the upload process of the vehicle data 90 to the server 10. In the first example, the vehicle data 90 is data collected around the timing t1 when the change in the SOC of the battery 21 is large. When there is a timing t1 during which the vehicle 20 is running and the change in the SOC of the battery 21 is larger compared to other times, the TCU 40 collects, as the vehicle data 90, data including battery-related information and driving-related information in a predetermined period T1 including the timing t1. Here, the predetermined 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]. Note that various data constituting the vehicle data 90 are constantly acquired by the data acquisition unit 32a of the ECU 30 at a predetermined time interval during the startup of the vehicle 20 and are stored for at least a predetermined period. Therefore, the TCU 40 can also collect the vehicle data 90 before the timing t1.

[0037] The driving-related information is information including at least one of, for example, the change over time of the vehicle speed, acceleration, angular acceleration, drive torque, accelerator opening, and brake pedal force in the period T1, and the driving location information. The driving-related information may also include information on the outside air temperature. The battery-related information is information including at least the change over time of the SOC of the battery 21 in the period T1. Since the vehicle data 90 including such change over time information is relatively large in volume, for example, if it is uploaded to the server 10 by mobile communication while the vehicle 20 is running, an increase in communication cost and a failure of the upload may occur.

[0038] When the TCU 40 is not in a state where it can communicate with the server 10 via fixed communication, it continues to store the vehicle data 90 collected during the period T1 in the storage unit 43. Then, for example, when the vehicle 20 parks at home and becomes in a state where it can communicate with the server 10 using Wi-Fi connected to a fixed communication line, the TCU 40 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 the vehicle data 90 can be stably uploaded to the server 10.

[0039] The vehicle data 90 in the period T1 may be used to improve the accuracy of calculating the cruising range of the vehicle 20. Specifically, the server 10 learns a calculation logic for calculating the change amount of the SOC of the battery 21 according 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 logic that is finely customized for each user, it is possible to calculate a highly accurate cruising range for each user. Note that the server 10 may transmit the calculation logic obtained by learning to the vehicle 20, and the vehicle 20 may calculate the cruising range.

[0040] The highly accurate cruising range calculated in this way may be displayed on the display device provided in the HMI 22 or the navigation HMI 23b of the vehicle 20, or on a predetermined application screen of the mobile terminal used by the user, or may be displayed on a map. Specifically, it may be displayed on the map as an area with a high possibility of being reachable with the current remaining amount of the battery 21.

[0041] In addition, the vehicle data 90 during the period T1 may be used to improve the points, roads, or facilities that cause a decrease in the SOC of the battery 21. Specifically, the server 10 identifies the location (e.g., road or facility) where the vehicle 20 was traveling at the timing t1 when the SOC significantly decreased based on the vehicle data 90 uploaded from the vehicle 20, and analyzes the trends such as the gradient, curvature, and road surface material at the location where the SOC significantly decreases. As a result, the operator of the server 10 can provide the analysis results to local governments, etc., and contribute to the improvement of roads and facilities where the SOC may significantly decrease.

[0042] FIG. 5 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 is started. Specifically, the vehicle data 90 is data including the startup information acquired during the period T2 from the timing t2 when the ignition of the vehicle 20 is turned ON until the elapse of a predetermined time (e.g., 15 seconds). The TCU 40 collects the vehicle data 90 acquired during the period T2. The time interval for collecting data is, for example, from 10 [ms] to 1 [s].

[0043] The startup information is information including at least one of, for example, the temperature, charge state, elapsed-time change information of current, and elapsed-time change information of voltage of the battery 21 acquired during the period T2. The startup information may also include information regarding the state of the vehicle 20, such as the temperature of the vehicle 20. Since the vehicle data 90 including such elapsed-time change information is relatively large in volume, if it is uploaded to the server 10 via mobile communication, an increase in communication cost or a failure in upload may occur.

[0044] When the TCU 40 is not in a state where it can communicate with the server 10 via fixed communication, it continues to store the vehicle data 90 acquired during the period T2 at the startup of the vehicle 20 in the storage unit 43. Then, when the vehicle 20, for example, parks at home and becomes in a state where it can communicate with the server 10 using Wi-Fi connected to a fixed communication line, the TCU 40 uploads the vehicle data 90 stored in the storage unit 43 to the server 10 via fixed communication. As a result, communication costs can be reduced, and the vehicle data 90 can be stably uploaded to the server 10.

[0045] The vehicle data 90 including startup information may be used, for example, to identify abnormalities in the vehicle 20. Specifically, the server 10 communicates with a plurality of vehicles via the network NW and stores the vehicle data 90 including the startup information of each vehicle in the storage unit 13 as big data. The server 10 identifies a vehicle in which an abnormality has occurred based on the startup information of the plurality of vehicles.

[0046] FIG. 6 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 facility 5. That is, the vehicle 20 starts collecting the vehicle data 90 triggered by charging by the charging facility 5. The vehicle data 90 is information including, for example, the temperature of the battery 21, the state of charge, the change-over-time information of the current, and the change-over-time information of the voltage described above. The vehicle data 90 may also include various data stored in each ECU 30 during the running of the vehicle 20. The TCU 40 communicates with the charging facility 5 via a communication line provided in the charging cable of the charging facility 5 and uploads the vehicle data 90 to the server 10 using the fixed communication line of the charging facility 5. Note that the TCU 40 may communicate with the charging facility 5 by wireless communication instead of wired communication, and in this case as well, the vehicle data 90 is uploaded to the server 10 using the fixed communication line of the charging facility 5.

[0047] 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 started to be collected triggered by charging by the charging facility 5, the other vehicle data 90 that has already been collected may also be uploaded to the server 10 using the fixed communication line of the charging facility 5.

[0048] (Modification example) In the above-described embodiment, the TCU 40 uploads the vehicle data 90 to the server 10 only when it is communicable with the server 10 by fixed communication based on the data upload conditions defined in the data collection setting file 80, but it is not limited to this.

[0049] For example, when the TCU 40 is not 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 increases. Therefore, the data collection setting file 80 may 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. When the connection standby time to the fixed communication line and / or the cache amount exceeds the upper limit value, the TCU 40 may be able to upload the vehicle data 90 to the server 10 by mobile communication.

[0050] Also, for example, in the data collection setting file 80, information among the information included in the vehicle data 90 whose capacity is smaller than a predetermined threshold value may be defined to be immediately uploaded to the server 10 by mobile communication after being collected.

[0051] Also, for example, when an instruction to immediately collect and / or upload the vehicle data 90 is received from the server 10 or the like, the TCU 40 may be able to immediately collect and / or upload the vehicle data 90 to the server 10 by mobile communication.

[0052] As described above, an embodiment of the present invention has been described with reference to the accompanying drawings. Needless to say, the present invention is not limited to such an embodiment. It is obvious that those skilled in the art can conceive of various modifications or corrections within the scope described in the claims, and it is naturally understood that they also belong to the technical scope of the present invention. Also, within the scope not departing from the gist of the invention, the components in the above embodiment may be arbitrarily combined.

[0053] For example, although the vehicle data 90 that is uploaded to the server 10 by fixed communication in principle has been given some specific examples in the above-described embodiment, it may include various information other than the above-described specific examples. For example, the vehicle data 90 may include information such as video data from an in-vehicle camera and shape measurement data by a radar, which is relatively large in volume and does not require immediate uploading.

[0054] The present specification describes at least the following matters. Although the corresponding components and the like in the above-described embodiment are shown as an example in parentheses, the present invention is not limited thereto.

[0055] (1) A vehicle communication system (communication system 1) including a vehicle (vehicle 20) equipped with a battery (battery 21) that supplies power to a drive source, and a server (server 10) that can communicate with the vehicle, wherein the vehicle has a communication device (TCU 40) that can collect predetermined vehicle data (vehicle data 90) and upload it to the server, the server has a server-side storage device (storage unit 13) that stores the vehicle data uploaded from the vehicle, the communication device of the vehicle, is configured to be able to communicate with the server by mobile communication, which is metered data communication, and fixed communication, which is flat-rate data communication, and uploads the vehicle data to the server by the fixed communication when it is in a state where it can communicate with the server by the fixed communication, A vehicle communication system.

[0056] According to (1), by uploading vehicle data to a server by means of flat-rate fixed communication instead of usage-based mobile communication, communication costs can be reduced.

[0057] (2) A vehicle communication system according to (1), wherein the vehicle further includes a vehicle-side storage device (storage unit 43) that stores the vehicle data, and when the communication device of the vehicle is not in a state where it can communicate with the server by the fixed communication, the vehicle data continues to be stored in the vehicle-side storage device. Vehicle communication system.

[0058] (2) According to (2), when the vehicle is not in a state where it can communicate with the server by fixed communication, the vehicle data continues to be stored in the vehicle-side storage device without being uploaded to the server by mobile communication, so that communication costs can be reduced.

[0059] (3) A vehicle communication system according to (2), wherein the vehicle data includes driving-related information related to the running of the vehicle and battery-related information related to the battery in a first period (period T1) including a timing when the change in the state of charge (SOC) of the battery is large. Vehicle communication system.

[0060] (3) According to (3), since the vehicle data obtained in the first period including the timing when the change in the state of charge of the battery is large is stored in the server, the server can improve the calculation accuracy of the cruising range based on the vehicle data or analyze the points that cause the change in the state of charge.

[0061] (4) A vehicle communication system according to (3), wherein the driving-related information includes at least one of the time-dependent change information of vehicle speed, acceleration, angular acceleration, driving torque, accelerator opening, and brake pedal force, and the driving location information, and the battery-related information includes at least the time-dependent change information of the state of charge of the battery. Vehicle communication system.

[0062] According to (4), even if the vehicle data is large-capacity data including time-varying information, the communication device uploads the vehicle data to the server by flat-rate fixed communication instead of usage-based mobile communication, so that the communication cost can be reduced. Further, when the driving-related information includes driving location information, the server can identify a location where the change in the battery charge state is large and utilize improvement measures at the location.

[0063] (5) The vehicle communication system according to (3) or (4), The server learns calculation logic for calculating the amount of change in the charge state of the battery according to the driving behavior of the user of the vehicle or the driving route of the vehicle based on the vehicle data uploaded from the vehicle. The server or the vehicle calculates the cruising range of the vehicle based on the amount of change in the charge state of the battery calculated by the calculation logic. Vehicle communication system.

[0064] According to (5), the server can calculate the cruising range with high accuracy based on the stored information. Also, the cruising range can be calculated for each user of the vehicle customized.

[0065] (6) The vehicle communication system according to any one of (1) to (5), The vehicle data includes startup information acquired during a second period (period T2) from the startup of the vehicle until the elapse of a predetermined time. Vehicle communication system.

[0066] According to (6), the information acquired at the startup of the vehicle where the change in behavior is likely to appear can be uploaded to the server by fixed communication. Thereby, the server can control the vehicle with high accuracy.

[0067] (7) The vehicle communication system according to (6), The startup information includes at least one of the temperature of the battery, the state of charge, the information on the change over time of the current, and the information on the change over time of the voltage, which were acquired during the second period. Vehicle communication system.

[0068] (7) According to this, information related to the battery acquired at the startup of a vehicle where changes in behavior are likely to occur can be uploaded to the server by fixed communication. As a result, the server can control the battery with high precision.

[0069] (8) The vehicle communication system according to (6) or (7), wherein the server identifies a vehicle in which an abnormality has occurred based on the startup information uploaded from a plurality of vehicles. Vehicle communication system.

[0070] (8) According to this, a vehicle in which an abnormality has occurred can be identified from big data having startup information of a plurality of vehicles.

[0071] (9) The vehicle communication system according to any one of (1) to (8), wherein the vehicle data includes diagnostic information for diagnosing the state of equipment provided in the vehicle. Vehicle communication system.

[0072] (9) According to this, diagnostic information, which is non-control data not used for the control operation of the vehicle, can be uploaded to the server by fixed communication.

[0073] (10) The vehicle communication system according to any one of (2) to (9), wherein after uploading the vehicle data stored in the vehicle-side storage device to the server by the fixed communication, the communication device deletes the vehicle data from the vehicle-side storage device. Vehicle communication system.

[0074] (10) According to this, it is possible to suppress the compression of the data capacity of the vehicle-side storage device.

[0075] (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 predetermined vehicle data (vehicle data 90) and uploading it to a server (server 10), configured to be communicable with the server by mobile communication which is metered data communication and fixed communication which is flat-rate data communication, when in a state communicable with the server by the fixed communication, uploading the vehicle data to the server by the fixed communication. Vehicle communication device.

[0076] (11) According to this, by uploading vehicle data to the server by flat-rate fixed communication instead of metered mobile communication, communication costs can be reduced.

Explanation of symbols

[0077] 1 Communication system (vehicle communication system) 10 Server 13 Storage unit (server-side storage device) 20 Vehicle 21 Battery 40 TCU (communication device) 43 Storage unit (vehicle-side storage device) 90 Vehicle data T1 period (first period) T2 period (second period)

Claims

1. A vehicle communication system comprising a vehicle equipped with a battery for supplying power to a drive 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 it 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 by mobile communication which is metered data communication and fixed communication which is flat-rate data communication, and when it is in a state capable of communicating with the server by the fixed communication, the vehicle data is uploaded to the server by the fixed communication. A vehicle communication system.

2. The vehicle communication system according to claim 1, wherein the vehicle further has a vehicle-side storage device for storing the vehicle data, and when the communication device of the vehicle is not in a state capable of communicating with the server by the fixed communication, the vehicle data continues to be stored in the vehicle-side storage device. A vehicle communication system.

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

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

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

6. The vehicle communication system according to any one of claims 1 to 5, wherein the vehicle data includes startup information acquired in a second period until a predetermined time has elapsed after startup of the vehicle. A vehicle communication system.

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

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. Vehicle communication system.

9. The vehicle communication system according to any one of claims 1 to 5, wherein the vehicle data includes diagnostic information for diagnosing the state of devices provided in the vehicle. Vehicle communication system.

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

11. A vehicle communication device provided in a vehicle having a battery that supplies power to a drive source, capable of collecting predetermined vehicle data and uploading it to a server, configured to be communicable with the server by mobile communication that is metered data communication and fixed communication that is flat-rate data communication, and uploading the vehicle data to the server by the fixed communication when in a state communicable with the server by the fixed communication. Vehicle communication device.

Images