Software Management Device

Abstract

To easily carry out update of software incorporated in an on-vehicle device 13 equipped in an own vehicle Vow.SOLUTION: A software management device 11 comprises: an information storage unit 43 which stores SW identification information SW_id related to software in association with version information Ver; a communication unit 31 which performs predetermined two-way communication with the other vehicle Vot present around an own vehicle Vow; a communication control unit 35 which makes the communication unit 31 perform first two-way communication with the other vehicle Vot, which receives first response information from the other vehicle Vot related to an inquiry of the SW identification information SW_id related to the software and the version information Ver; and a determination unit 37 which determines new and old states related to the version information Ver related to the software of each of the own vehicle Vow and the other vehicle Vot. The communication control unit 35 makes the communication unit 31 perform second two-way communication with the other vehicle Vot, which receives second response information from the other vehicle Vot related to download request of the software.SELECTED DRAWING: Figure 1B

Description

[Technical Field]

[0001] The present invention relates to a software management device that manages updates to software installed in an in-vehicle device provided in a vehicle. [Background technology]

[0002] Recent vehicles are equipped with various software programs to realize the functions of the vehicle's onboard devices. With this software program, there are cases where a request arises for subsequent improvements (reprogramming) to be made to parts of the software that were not apparent at the time of vehicle development. Such software updates (version upgrades) are generally carried out by taking the vehicle to a car dealer.

[0003] The applicant of the present application has disclosed an invention of a software update device that can execute software update processing more efficiently (see Patent Document 1). [Prior art documents] [Patent documents]

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

[0005] However, the software update technology disclosed in Patent Document 1 is cumbersome in that it requires communication with a server device each time software installed in an on-board device of a vehicle is updated, making it difficult to easily update the software installed in the on-board device of a vehicle.

[0006] The present invention has been made in view of the above-mentioned circumstances, and has an object to provide a software management device that can easily update software installed in an in-vehicle device provided in a vehicle.

[0007] Another object of the present invention is to provide a software management device that can further improve the smoothness of vehicle traffic and contribute to the development of a sustainable transportation system. [Means for solving the problem]

[0008] In order to achieve the above object, the present invention provides A software management device that manages updates to software related to an in-vehicle device provided in a vehicle, an information storage unit that stores identification information and version information related to the software in association with each other; a communication unit that performs predetermined two-way communication with other vehicles present around the vehicle; a communication control unit that causes the communication unit to perform first bidirectional communication in which an inquiry about identification information and version information about the software is made to other vehicles present around the vehicle, and first response information about the inquiry is received from the other vehicles; a determination unit that, when the identification information related to the software of the host vehicle and the identification information related to the software of the other vehicle match as a result of the comparison based on the first response information from the other vehicle, determines whether the version information related to the software of the host vehicle and the other vehicle is new or old, The communication control unit When the determination unit determines that the version of the software of the other vehicle is newer than the version of the software of the vehicle, the communication unit is caused to perform second two-way communication to send a download request for the software to the other vehicle and receive second response information from the other vehicle regarding the download request, thereby downloading the software held by the other vehicle. death, the communication unit includes a first communication unit that performs first two-way communication with another vehicle using a first communication method, and a second communication unit that performs second two-way communication with another vehicle using a second communication method different from the first communication method, The second two-way communication associated with the second communication unit uses a communication method with higher confidentiality and bit rate than the first two-way communication associated with the first communication unit. This is its most important feature.

[0009] According to the software management device of the present invention, it is possible to easily update software installed in an in-vehicle device provided in a vehicle. [Brief explanation of the drawings]

[0010] [Figure 1A] 1 is an explanatory diagram conceptually illustrating a usage state of a software management device according to an embodiment of the present invention; [Figure 1B] 1 is a block diagram showing an overview of a software management system including a software management device according to an embodiment of the present invention; [Figure 2A] 1 is an explanatory diagram conceptually showing a communication data structure used in a communication unit provided in a software management device. [Figure 2B] 1 is an explanatory diagram conceptually showing, in table format, a combination of SW identification information and version information, which is management information related to software related to an in-vehicle device provided in the vehicle. FIG. [Figure 2C] 1 is an explanatory diagram conceptually showing vehicle identification information for authenticating the authenticity of other vehicles in a table format; [Figure 3] FIG. 10 is a flowchart illustrating the operation of the software management device. [Figure 4] FIG. 1 is an explanatory diagram conceptually illustrating how software updates in a plurality of vehicles are promoted in a chain reaction. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, a software management device according to an embodiment of the present invention will be described in detail with reference to the appropriate drawings. In the drawings shown below, components having a common function or components having corresponding functions are generally designated by the same reference numerals. For the sake of convenience, the size and shape of components may be exaggerated or distorted to show a schematic representation.

[0012] [Overview of Software Management System 10 Including Software Management Device 11] First, an overview of a software management system 10 including a software management device 11 according to an embodiment of the present invention will be described with reference to FIGS. 1A and 1B. 1A is an explanatory diagram conceptually showing a usage state of a software management device 11 according to an embodiment of the present invention. FIG. 1B is a block diagram showing an overview of a software management system 10 including the software management device 11.

[0013] As shown in FIGS. 1A and 1B, the host vehicle Vow has a function of managing updates to software related to the in-vehicle device 13 provided in the host vehicle Vow by performing two-way communication with the other vehicle Vot. The host vehicle Vow is, for example, a two-wheeled, three-wheeled, four-wheeled, or other vehicle, and its drive source is an internal combustion engine such as a diesel engine or a gasoline engine, an electric motor, or a combination of these. The electric motor is driven by electric power generated by a generator connected to the internal combustion engine, or by discharged electric power from a secondary battery such as a lithium-ion battery or a nickel-metal hydride battery, or a fuel cell. In the following description, a four-wheel vehicle using an electric motor as a drive source will be exemplified as the host vehicle Vow.

[0014] In order to realize the function of managing software updates for the on-board device 13 provided in the vehicle Vow, the software management system 10 is configured to include a software management device 11, an on-board device 13, an HMI (Human Machine Interface) 15, and an MID (Multi-Information Display) 17, as shown in Figure 1B.

[0015] The in-vehicle device 13 includes, for example, a driving control device 21, a braking / driving control device 23, a battery management device 25, and a navigation device 27.

[0016] The driving control device 21 has a function of performing driving assistance control including automatic driving (autonomous driving) control of the host vehicle Vow. Automatic driving control means, for example, controlling one or both of the steering and speed of the host vehicle Vow without relying on driving operations by an occupant of the host vehicle Vow. Furthermore, driving assistance control refers to control that assists the driver in driving, such as an adaptive cruise control system (ACC), a lane keeping assistance system (LKAS), and a collision mitigation brake system (CMBS).

[0017] The operation control device 21 is composed of a microcomputer (not shown; hereinafter, sometimes abbreviated as "microcomputer") equipped with a CPU, memory such as RAM and ROM (storage unit 22), and an input / output interface. The microcomputer has built-in software for executing the ACC, LKAS, and CMBS. By executing the software, the microcomputer executes the corresponding control of, for example, the ACC, LKAS, or CMBS.

[0018] Each of the multiple software programs is assigned SW identification information SW_id that can uniquely identify the software. Each of the multiple SW identification information SW_id is also assigned unique version information Ver. In short, each of the multiple software programs is assigned unique SW identification information SW_id and version information Ver.

[0019] Each of the plurality of software programs can be updated to upgrade its version through the operation of the software management device 11.

[0020] The storage unit 22 provided in the operation control device 21 stores a plurality of software programs related to the operation control device 21, as well as unique SW identification information SW_id and version information Ver associated with each of the plurality of software programs.

[0021] The braking / driving control device 23 has a function of performing braking / driving control of the host vehicle Vow by applying braking force, driving force, and steering force to the host vehicle Vow. The braking / driving control device 23 is configured to include, for example, a braking device (not shown) that outputs braking torque to each wheel according to a braking command, a driving device (not shown) that outputs driving force (torque) according to a driving command to the driving wheels, and a steering device (not shown) that steers the front wheels in a direction and angle according to a steering command.

[0022] Like the operation control device 21, the braking / driving control device 23 is configured by a microcomputer having a storage unit 24. Predetermined software for executing braking control, driving control, and steering control is installed in the microcomputer. By executing the predetermined software, the microcomputer executes control related to any one of braking control, driving control, and steering control, or a combination of these.

[0023] The storage unit 24 provided in the braking / driving control device 23 stores a plurality of software programs related to the braking / driving control device 23, as well as unique SW identification information SW_id and version information Ver associated with each of the plurality of software programs.

[0024] The battery management unit 25 manages the battery status, including the state of charge (SOC) of a battery (not shown) mounted on the host vehicle Vow. The battery supplies power to a drive motor (not shown) and the like.

[0025] The storage unit 26 provided in the battery management unit 25 stores a plurality of software programs related to the battery management unit 25, as well as unique SW identification information SW_id and version information Ver associated with each of the plurality of software programs.

[0026] The navigation device 27 includes, for example, a GNSS (Global Navigation Satellite System) receiver (not shown). The GNSS receiver identifies the current position of the vehicle Vow based on signals received from GNSS satellites. The navigation device 27 has a function of providing guidance on a route from the current position to a destination.

[0027] The storage unit 28 provided in the navigation device 27 stores a plurality of software programs related to the navigation device 27, as well as unique software identification information SW_id and version information Ver associated with each of the plurality of software programs.

[0028] The HMI 15 serves to accept various input operations by the occupant of the host vehicle Vow. The HMI 15 includes, for example, a group of various operation switches 45 and a touch panel (not shown). The touch panel may be configured integrally with the MID 17.

[0029] The MID 17 is a display device formed of, for example, an LCD (Liquid Crystal Display) 47. The MID 17 plays a role in displaying an image (for example, a version update status for each of a plurality of software programs) generated by a display control unit (not shown) provided in the software management device 11.

[0030] [Overview of the software management device 11] Next, an overview of software management device 11 will be described with reference to FIGS. 1A, 1B, and 2A to 2C as appropriate. Fig. 2A is an explanatory diagram conceptually showing a communication data structure used by the communication unit 31 provided in the software management device 11. Fig. 2B is an explanatory diagram conceptually showing, in a table format, a combination of SW identification information SW_id and version information Ver, which is management information 51 related to software related to the in-vehicle device 13 provided in the host vehicle Vow. Fig. 2C is an explanatory diagram conceptually showing, in a table format, vehicle identification information 53 for authenticating the authenticity of another vehicle Vot.

[0031] As shown in FIG. 1B, the software management device 11 includes, for example, a communication unit 31, a communication control unit 35, a determination unit 37, an update management unit 39, and an internal memory 41.

[0032] The communication unit 31 has a function of performing predetermined two-way communication with another vehicle Vot present around the host vehicle Vow. The communication unit 31 is configured to include a first communication unit 32 that performs the first two-way communication with the other vehicle Vot using a first communication method, and a second communication unit 33 that performs the second two-way communication with the other vehicle Vot using a second communication method different from the first communication method.

[0033] In the second two-way communication related to the second communication unit 33, a communication method with higher confidentiality and bit rate than the first two-way communication related to the first communication unit 32 is used.

[0034] In the first two-way communication related to the first communication unit 32, the first two-way communication is performed between the vehicle Vow and another vehicle Vot located around the vehicle Vow using a wireless communication method such as a dedicated short range communication (DSRC) function or a cellular communication function.

[0035] In the second two-way communication by the second communication unit 33, for example, a wireless communication method such as Wifi or Bluetooth (registered trademark) is used to perform the second two-way communication with another vehicle Vot existing around the vehicle Vow.

[0036] The communication control unit 35 causes the first communication unit 32 to make an inquiry to another vehicle Vot located around the vehicle Vow about SW identification information SW_id and version information Ver regarding the software, while also causing the first communication unit 32 to perform first two-way communication to receive first response information from the other vehicle Vot regarding the inquiry.

[0037] Furthermore, when the judgment unit 37 (described below) determines that the software version of the other vehicle Vot is newer than the software version of the subject vehicle Vow, the communication control unit 35 causes the second communication unit 33 to perform a second two-way communication to make a software download request to the other vehicle Vot, while receiving second response information from the other vehicle Vot regarding the download request.

[0038] Here, the communication data structure (communication frame 49) used in the first two-way communication and the second two-way communication will be described with reference to FIG. 2A.

[0039] As shown in FIG. 2A, the communication frame 49 includes caller identification information and software information.

[0040] The transmission identification information includes transmission vehicle identification information 1 (the vehicle number of the transmission vehicle Vog), transmission vehicle identification information 2 (the manufacturer identification (manufacturer code) of the transmission vehicle Vog), and transmission time information. A vehicle Vrv that receives a communication frame 49 including the transmission identification information can determine the origin of the transmission vehicle Vog, the time and the date from which the communication frame 49 was received.

[0041] The software information includes SW identification information SW_id and version information Ver relating to the software related to the in-vehicle device 13 provided in the transmitting vehicle Vog. The software information in the communication frame 49 relating to the second response information in the second two-way communication includes a program for updating the version of the software. The vehicle Vrv that receives the communication frame 49 containing the software information can grasp not only the originating vehicle Vog from which and when the communication frame 49 was received, but also the SW identification information SW_id and version information Ver relating to the software related to the on-board device 13 installed in the originating vehicle Vog.

[0042] Based on the first response information received from the other vehicle Vot, the judgment unit 37 checks whether the SW identification information SW_id[Vow] relating to the software of the own vehicle Vow and the SW identification information SW_id[Vot] relating to the software of the other vehicle Vot match. As a result of the comparison based on the first response information from the other vehicle Vot, if the SW identification information SW_id[Vow] regarding the software of the own vehicle Vow and the SW identification information SW_id[Vot] regarding the software of the other vehicle Vot match, the judgment unit 37 judges the newness or oldness of the version information Ver regarding the software of each of the own vehicle Vow and the other vehicle Vot.

[0043] If, as a result of the comparison based on the first response information from the other vehicle Vot, the SW identification information SW_id[Vow] relating to the software of the host vehicle Vow and the SW identification information SW_id[Vot] relating to the software of the other vehicle Vot match, and the judgment unit 37 determines that the version of the software of the other vehicle Vot is newer than the version of the software of the host vehicle Vow, the update management unit 39 applies the software downloaded from the other vehicle Vot to the in-vehicle device 13 provided in the host vehicle Vow, thereby performing an update to upgrade the version of the software.

[0044] The internal memory 41 is configured to include an information storage unit 43 and a vehicle identification database 44 .

[0045] 2B, the information storage unit 43 has a function of storing SW identification information SW_id and version information Ver in association with each other as management information 51 related to software related to the in-vehicle device 13 provided in the host vehicle Vow. Note that the stored contents of the information storage unit 43 are assumed to be updated, for example, when an update process is performed on the software related to the in-vehicle device 13 provided in the host vehicle Vow.

[0046] 2C, the vehicle identification database 44 has a function of storing the vehicle identification number, manufacturer code, and vehicle model code assigned to the vehicle V in association with each other as vehicle identification information 53 for authenticating the authenticity of the other vehicle Vot. Note that the contents stored in the vehicle identification database 44 are updated, for example, with an information management server (not shown) at appropriate times.

[0047] [Operation of the software management device 11] Next, the operation of software management device 11 will be described with reference to FIGS. Fig. 3 is a flowchart illustrating the operation of the software management device 11. Fig. 4 is an explanatory diagram conceptually showing how software updates provided in each of a plurality of vehicles V are promoted in a chain reaction. It is assumed that the software management device 11 has recognized in advance that another vehicle Vot is present around the host vehicle Vow through the function of the ADAS (Advanced Driver-Assistance Systems) provided in the host vehicle Vow.

[0048] In step S11 shown in FIG. 3, the communication control unit 35 sets the first communication mode, thereby causing the first communication unit 32 to perform the first two-way communication.

[0049] In step S12, the communication control unit 35 causes the first communication unit 32 to make an inquiry to another vehicle Vot present around the host vehicle Vow about SW identification information SW_id and version information Ver relating to the software.

[0050] In step S13, the communication control unit 35 uses the first communication unit 32 to perform first two-way communication to receive first response information from the other vehicle Vot regarding the inquiry in step S12. Note that the first response information may include setting information related to the second communication mode in step S18.

[0051] In step S14, the judgment unit 37 checks whether the SW identification information SW_id[Vow] relating to the software of the host vehicle Vow and the SW identification information SW_id[Vot] relating to the software of the other vehicle Vot match based on the first response information received from the other vehicle Vot.

[0052] In step S15, if the result of the comparison in step S14 shows that the SW identification information SW_id[Vow] relating to the software of the host vehicle Vow and the SW identification information SW_id[Vot] relating to the software of the other vehicle Vot match (Yes in step S15), the judgment unit 37 proceeds to step S16. On the other hand, if they do not match (No in step S15), software management apparatus 11 ends the series of processing flows.

[0053] In step S16, the determination unit 37 compares the version information Ver relating to the software of the subject vehicle Vow and the other vehicle Vot to determine whether it is new or old.

[0054] In step S17, if the comparison judgment in step S16 determines that the version of the software of the other vehicle Vot is newer than the version of the software of the subject vehicle Vow (Yes in step S17), the judgment unit 37 determines that the software can be updated and proceeds to step S18. On the other hand, if not (No in step S17), software management apparatus 11 ends the series of processing flows.

[0055] In step S18, the communication control unit 35 sets the second communication mode according to the setting information for the second communication mode included in the first response information, thereby causing the second communication unit 33 to perform the second two-way communication.

[0056] In step S19, the communication control unit 35 causes the second communication unit 33 to make a download request for the software to the other vehicle Vot.

[0057] In step S20, second two-way communication is performed to receive second response information from the other vehicle Vot in response to the download request in step S19.

[0058] In step S21, the update management unit 39 applies the software downloaded from the other vehicle Vot to the in-vehicle device 13 provided in the subject vehicle Vow, thereby performing an update process to upgrade the version of the software. Thereafter, software management device 11 ends the series of processing flows.

[0059] As described above, according to the software management device 11 of an embodiment of the present invention, as shown in Figure 4, software updates installed in each of multiple vehicles V can be promoted in a chain reaction, as if an infection were spreading, anytime and anywhere.

[0060] [Configuration, Functions, and Effects of the Software Management Device 11 According to the Present Invention] Next, the configuration, operation, and effect of the software management device 11 according to the present invention will be described. The software management device 11 based on the first aspect is premised on being a software management device that manages updates to software relating to the in-vehicle device 13 provided in the vehicle Vow. The software management device 11 based on the first aspect includes an information storage unit 43 that stores SW identification information SW_id and version information Ver related to the software in association with each other, a communication unit 31 that performs predetermined two-way communication with other vehicles Vot located around the host vehicle Vow, a communication control unit 35 that causes the communication unit 31 to perform first two-way communication in which an inquiry is made to other vehicles Vot located around the host vehicle Vow for SW identification information SW_id and version information Ver related to the software, while receiving first response information from the other vehicles Vot related to the inquiry, and a determination unit 37 that determines the old / new status of the version information Ver related to the software of the host vehicle Vow and the other vehicles Vot when, as a result of comparison based on the first response information from the other vehicles Vot, the SW identification information SW_id[Vow] related to the software of the host vehicle Vow and the SW identification information SW_id[Vot] related to the software of the other vehicles Vot match. When the judgment unit 37 determines that the software version of the other vehicle Vot is newer than the software version of the vehicle Vow, the communication control unit 35 makes a download request to the other vehicle Vot for the software, and also makes the communication unit 31 perform second two-way communication to receive second response information from the other vehicle Vot regarding the download request, thereby downloading the software possessed by the other vehicle Vot.

[0061] According to the software management device 11 based on the first aspect, it is possible to obtain a software management device 11 that can easily update software installed in the in-vehicle device 13 provided in the vehicle Vow. Furthermore, according to the software management device 11 based on the first aspect, it is possible to provide a software management device 11 that can further improve the smoothness of vehicle traffic and contribute to the development of a sustainable transportation system.

[0062] The software management device 11 based on the second aspect may be the software management device 11 based on the first aspect, and may further include an update management unit 39 that applies the software downloaded from the other vehicle Vot to the in-vehicle device 13 provided in the vehicle Vow, thereby updating the version of the software to upgrade it.

[0063] According to the software management device 11 based on the second aspect, the update management unit 39 applies the software downloaded from the other vehicle Vot to the in-vehicle device 13 provided in the host vehicle Vow, thereby updating the version of the software, thereby making it possible to easily update the software built into the in-vehicle device 13 provided in the host vehicle Vow.

[0064] A software management device 11 based on a third aspect is a software management device 11 based on the first or second aspect, wherein the communication unit 31 includes a first communication unit 32 that performs first two-way communication with another vehicle Vot using a first communication method, and a second communication unit 33 that performs second two-way communication with another vehicle Vot using a second communication method different from the first communication method, and the second two-way communication related to the second communication unit 33 may be configured to use a communication method with higher confidentiality and bit rate than the first two-way communication related to the first communication unit 32.

[0065] According to the software management device 11 based on the third aspect, the second two-way communication related to the second communication unit 33 uses a communication method with higher confidentiality and bit rate than the first two-way communication related to the first communication unit 32, and therefore, it is possible to carry out software update processing more safely and quickly than the software management device 11 based on the first or second aspect.

[0066] The software management device 11 based on the fourth aspect may be the software management device 11 based on the third aspect, and may be configured such that at least the communication data used in the second two-way communication (see communication frame 49 shown in Figure 2A) includes vehicle identification information (see "transmission identification information" in communication frame 49 shown in Figure 2A) that can uniquely identify the subject vehicle Vow and the other vehicle Vot.

[0067] According to the software management device 11 based on the fourth aspect, at least the communication data used in the second two-way communication (see communication frame 49 shown in Figure 2A) includes vehicle identification information (see "transmission identification information" in communication frame 49 shown in Figure 2A) that can uniquely identify the subject vehicle Vow and the other vehicle Vot. Therefore, in addition to the effects of the software management device 11 based on the third aspect, when the second two-way communication is performed between the subject vehicle Vow and the other vehicle Vot, each of the subject vehicle Vow and the other vehicle Vot can understand the identity of the other vehicle. As a result, it is possible to expect the effect of ensuring safety when performing second two-way communication between the subject vehicle Vow and the other vehicle Vot.

[0068] The software management device 11 based on the fifth aspect is the software management device 11 based on the fourth aspect, wherein the vehicle identification information includes the vehicle's chassis number and manufacturer identification, and further includes a vehicle identification database 44 that stores the vehicle identification information of genuine vehicles, and the communication control unit 35 may adopt a configuration in which, at least in the second two-way communication, the vehicle identification information of the other vehicle Vot is used as an authentication key and the authenticity of the software is guaranteed by referring to the vehicle identification database 44.

[0069] According to the software management device 11 based on the fifth aspect, the communication control unit 35 uses the vehicle identification information of the other vehicle Vot as an authentication key, at least in the second two-way communication, and ensures the authenticity of the software by referring to the vehicle identification database 44.Therefore, compared to the effect of the software management device 11 based on the fourth aspect, it is possible to achieve a high level of effect in ensuring safety in the second two-way communication between the vehicle Vow and the other vehicle Vot.

[0070] Other Embodiments The above-described embodiments are merely examples of the present invention, and therefore the technical scope of the present invention should not be construed as being limited by them, as the present invention can be embodied in various forms without departing from the spirit or main characteristics thereof.

[0071] For example, in the description of the software management device 11 according to the embodiment of the present invention, the driving control device 21, braking / driving control device 23, battery management device 25, and navigation device 27 are exemplified as the in-vehicle devices 13 provided in the host vehicle Vow, but the present invention is not limited to this example. The software management device 11 according to the present invention may also be applied to software update management for in-vehicle devices 13 such as audio devices, keyless entry systems, suspension systems, and airbag devices.

[0072] Furthermore, in the explanation of the software management device 11 according to the embodiment of the present invention, a four-wheel vehicle using an electric motor as a drive source has been described as an example of the host vehicle Vow, but the present invention is not limited to this example. It goes without saying that the software management device 11 according to the present invention is applicable to all vehicles that use an internal combustion engine such as a diesel engine or a gasoline engine, an electric motor, or a combination thereof as a drive source. [Explanation of symbols]

[0073] 10 Software Management System 11 Software management device 13 Onboard equipment 31 Communications Department 32 First Communications Department (Communications Department) 33 Second Communication Department (Communication Department) 35 Communication control section 37 Judgment section 39 Update Management Department 41 Internal Memory 43 Information storage section 44 Vehicle Identification Database (Database) 49 Communication Frames 51 Software Management Information 53 Vehicle Identification Information V vehicle Vow Your vehicle Vot other vehicles SW_id SW identification information Ver. Version Information

Claims

1. A software management device that manages updates to software related to an in-vehicle device provided in a vehicle, an information storage unit that stores identification information and version information related to the software in association with each other; a communication unit that performs predetermined two-way communication with other vehicles present around the vehicle; a communication control unit that causes the communication unit to perform first bidirectional communication in which an inquiry about identification information and version information about the software is made to other vehicles present around the vehicle, and first response information about the inquiry is received from the other vehicles; a determination unit that, when the identification information related to the software of the host vehicle and the identification information related to the software of the other vehicle match as a result of the comparison based on the first response information from the other vehicle, determines whether the version information related to the software of the host vehicle and the other vehicle is new or old, The communication control unit If the determination unit determines that the version of the software of the other vehicle is newer than the version of the software of the vehicle, the software of the other vehicle is downloaded by making the communication unit perform second two-way communication to send a download request for the software to the other vehicle and receive second response information from the other vehicle regarding the download request; the communication unit includes a first communication unit that performs first two-way communication with another vehicle using a first communication method, and a second communication unit that performs second two-way communication with another vehicle using a second communication method different from the first communication method, The second two-way communication associated with the second communication unit uses a communication method with higher confidentiality and bit rate than the first two-way communication associated with the first communication unit. A software management device characterized by:

2. 2. The software management device according to claim 1, The vehicle further includes an update management unit that applies the software downloaded from the other vehicle to the in-vehicle device of the vehicle to upgrade the version of the software. A software management device characterized by:

3. 3. The software management device according to claim 1, At least the communication data used in the second two-way communication includes vehicle identification information that can uniquely identify the vehicle and the other vehicle. A software management device characterized by:

4. 4. The software management device according to claim 3, The vehicle identification information includes a vehicle serial number and a manufacturer identification of the vehicle; Further comprising a database storing the vehicle identification information of genuine vehicles; The communication control unit ensures authenticity of the software by using the vehicle identification information of the other vehicle as an authentication key and referring to the database at least in the second two-way communication. A software management device characterized by:

Images