WO2023074904A1

WO2023074904A1 - Software management system

Info

Publication number: WO2023074904A1
Application number: PCT/JP2022/040811
Authority: WO
Inventors: 武直服部
Original assignee: 株式会社アドヴィックス
Priority date: 2021-11-01
Filing date: 2022-10-31
Publication date: 2023-05-04
Also published as: JP2023067569A

Abstract

A software management system 10 comprises: a necessary information acquisition unit 222 that acquires, for each piece of software, a type of necessary information that is necessary for the software to function in a vehicle 30; a provision information acquisition unit 223 that acquires a type of provision information to be provided to the vehicle 30; and an applicable software identification unit 224 that identifies, on the basis of the type of necessary information and the type of provision information, a type of applicable software, from among a plurality of pieces of software, that can be applied to the vehicle 30.

Description

Software management system

The present invention relates to software management systems.

Patent Document 1 discloses a vehicle system that includes a vehicle and a server device installed outside the vehicle. The vehicle is equipped with a human-machine interface and an expansion module. In this vehicle system, when the expansion module is replaced in the vehicle, the user information is sent from the human-machine interface, and the specification information is sent from the replacement expansion module to the server device. Then, when the server device receives the user information and the specification information, an application list is generated based on the information, and this list is transmitted to the vehicle. Then, in the vehicle, when the application list is received, the application is downloaded from the server device based on this list. As described above, in the vehicle system of Patent Document 1, the function of the vehicle system is expanded by exchanging the extension module.

Japanese Patent Application Laid-Open No. 2021-5218

However, in the vehicle system of Patent Document 1, it is not assumed that the vehicle on which the expansion module is mounted will be changed. An object of the present invention is to provide a software management system that enhances convenience when using software that provides added value to a vehicle.

A software management system for solving the above problems is a system that identifies software to be applied to the vehicle from multiple software that provides added value to the vehicle. The software management system includes a necessary information acquisition unit that acquires the type of necessary information required for the software to function in the vehicle for each piece of software, and a provision that acquires the type of information to be provided to the vehicle. an information acquisition unit, and based on the type of the necessary information acquired by the necessary information acquisition unit and the type of the provided information acquired by the provided information acquisition unit, a plurality of the software can be applied to the vehicle. and an applicable software identification unit that identifies the type of applicable software.

According to the above software management system, the type of applicable software is specified based on the type of necessary information required for the software to function in the vehicle and the type of provided information provided to the vehicle. Even if the type of information provided by the vehicle is different, the type of software applicable to the vehicle can be identified. Therefore, it is possible to apply software selected from the applicable software to the vehicle, or apply all of the applicable software to the vehicle. As described above, according to the software management system, it is possible to enhance convenience when using software that provides added value to the vehicle.

FIG. 1 is a schematic diagram showing the software management system of the first embodiment. FIG. 2 is a flow chart showing the flow of processing for providing predetermined information to the server device. FIG. 3 is a flow chart showing the flow of processing for identifying applicable software. FIG. 4 is a flow chart showing the flow of processing for applying application software to a vehicle. FIG. 5 is a schematic diagram showing the software management system of the second embodiment. FIG. 6 is a flow chart showing the flow of processing for providing predetermined information to the server device. FIG. 7 is a schematic diagram showing a modified software management system. FIG. 8 is a schematic diagram showing a modified software management system.

(First embodiment)
A first embodiment of the software management system will be described below with reference to FIGS. 1 to 4. FIG.
FIG. 1 is a block diagram showing an overview of the software management system 10 of this embodiment. The software management system 10 includes a server device 20, a vehicle 30 and a portable device 40. FIG. The server device 20 and the vehicle 30 are communicably connected to each other via a mobile communication network NT. The vehicle 30 and the portable device 40 are communicably connected to each other by wire or short-range wireless.

The server device 20 is installed outside the vehicle 30, for example, at the facility of a service company that provides software to users. The server device 20 manages the use of software by users.

Here, the software provides added value to the vehicle 30. For example, the software includes software for assisting the running of the vehicle 30 , software for changing the control mode of the vehicle 30 according to the situation outside the vehicle, and software for automatically parking the vehicle 30 .

A user is a person who has a contract with a service company regarding the use of software.
In this embodiment, it is assumed that the type of software that a user is permitted to use under the contract differs from user to user. Hereinafter, software that is permitted to be used by the user will be referred to as "permitted software".

The vehicle 30 is a shared vehicle of a car sharing service. A driver of the vehicle 30 is the above-mentioned user and a user of the car sharing service. As the mobile device 40, a smart phone carried by the user, a tablet terminal, and a card with an integrated circuit are conceivable.

In this embodiment, the information provided to the vehicle 30 , in other words, the information that can be used by the vehicle 30 differs depending on the vehicle 30 . Hereinafter, the information provided to the vehicle 30 will be referred to as "provided information". It is conceivable that the provided information varies depending on the detection device and communication device mounted on the vehicle 30 .

For example, the provided information is imaging information outside the vehicle 30, radar information around the vehicle 30, pedestrian-to-vehicle communication information, vehicle-to-vehicle communication information, road-to-vehicle communication information, and satellite communication information. Depending on the vehicle 30, it is conceivable that one of these pieces of information is not provided to the vehicle 30, or that the information provided to the vehicle 30 regarding each piece of information is limited.

For example, with respect to imaging information, depending on the vehicle 30, it may not be provided because it is not equipped with an imaging device. Regarding road-to-vehicle communication information, it is conceivable that different vehicles 30 have different communicable infrastructures. Regarding the satellite communication information, it is conceivable that the types of satellites that can be communicated with and the number of satellites differ depending on the vehicle 30 .

Also, in this embodiment, as described above, the type of provided information differs depending on the vehicle 30 , so the software that can be made to function in the vehicle 30 differs depending on the vehicle 30 .

For example, it is conceivable that software that changes the control mode of the vehicle 30 according to the situation outside the vehicle can be applied to the vehicle 30 to which imaging information is provided. Software that automatically parks a vehicle 30 may be applicable to vehicles 30 for which radar information is provided. It is conceivable that software that warns of the presence of pedestrians that cannot be confirmed by the vehicle 30 can be applied to the vehicle 30 provided with pedestrian-to-vehicle communication information. It is conceivable that software that assists entering or merging onto roads with poor visibility can be applied to vehicles 30 to which vehicle-to-vehicle communication information is provided. It is conceivable that software that assists the vehicle 30 in stopping in response to a traffic signal signal is applicable to the vehicle 30 provided with road-to-vehicle communication information from the traffic signal. It is conceivable that software that assists the vehicle 30 in traveling according to the lane in which the vehicle 30 is traveling is applicable to the vehicle 30 provided with satellite communication information regarding the position of the vehicle 30 from multiple satellites.

<Vehicle>
The vehicle 30 includes a first vehicle communication device 31 , a second vehicle communication device 32 , an in-vehicle device 33 and a vehicle display device 34 . The first vehicle communication device 31 , the second vehicle communication device 32 , and the vehicle display device 34 are each connected to the in-vehicle device 33 .

The first vehicle communication device 31 receives information transmitted from the server device 20 via the mobile communication network NT, and outputs the information to the vehicle-mounted device 33 . The first vehicle communication device 31 also transmits the information output from the in-vehicle device 33 to the server device 20 via the mobile communication network NT.

The second vehicle communication device 32 receives information transmitted from the portable device 40 and outputs the information to the in-vehicle device 33 . The second vehicle communication device 32 also transmits information output from the in-vehicle device 33 to the portable device 40 .

The vehicle display device 34 displays information output from the vehicle-mounted device 33 .
The in-vehicle device 33 includes a control section and a storage section. The storage unit stores a control program executed by the control unit.

The in-vehicle device 33 functions as a user information providing unit 331, a provided information providing unit 332, an applicable software transmitting unit 333, and a software applying unit 334 by the control unit executing the control program.

The user information providing unit 331 acquires information specifying the user who is the driver of the vehicle 30 from the mobile device 40 and provides the server device 20 with the information. Hereinafter, information that identifies a user will be referred to as "user information". The user information corresponds to "driver information" in the claims. For example, the user information providing unit 331 transmits user information received by the second vehicle communication device 32 from the first vehicle communication device 31 to the server device 20 .

The provided information providing unit 332 provides the type of provided information to the server device 20 . For example, the provided information providing unit 332 transmits the type of provided information stored in the storage unit of the in-vehicle device 33 from the first vehicle communication device 31 to the server device 20 .

The applicable software transmission unit 333 transmits the type of applicable software acquired from the server device 20 to the mobile device 40 . For example, the applicable software transmission unit 333 transmits the type of applicable software received by the first vehicle communication device 31 from the second vehicle communication device 32 to the portable device 40 . Applicable software is described later.

The software application unit 334 acquires the type of software to be applied to the vehicle 30 from the portable device 40 and applies the software to the vehicle 30 . Hereinafter, the software applied to the vehicle 30 will be referred to as "applied software". For example, the software application unit 334 applies application software to the vehicle 30 based on the type of application software received by the second vehicle communication device 32 .

Here, the application of the applicable software to the vehicle 30 may be the execution of the applicable software pre-stored in the storage unit of the in-vehicle device 33, or the execution of the applicable software downloaded from the server device 20. Alternatively, it may be reception of the execution result of the application software executed by the server device 20 .

<Server device>
The server device 20 includes a server communication device 21 and a software management device 22 .
The server communication device 21 receives information transmitted from the vehicle 30 via the mobile communication network NT and outputs the information to the software management device 22 . The server communication device 21 also transmits the information output from the software management device 22 to the vehicle 30 via the mobile communication network NT.

The software management device 22 has a control section and a storage section. The storage unit stores a control program executed by the control unit.
The software management device 22 functions as a permitted software identification unit 221, a necessary information acquisition unit 222, a provided information acquisition unit 223, an applicable software identification unit 224, and an applicable software provision unit 225 by the control unit executing the control program. do.

The permitted software identification unit 221 identifies the type of permitted software based on the user information acquired from the vehicle 30. For example, the permitted software identification unit 221 inputs the user information received by the server communication device 21 into a database in which the user information and the type of permitted software are associated, and identifies the type of software output from the database as the type of the permitted software. identified as a type of In this case, the database may be stored in the storage unit of the software management device 22, for example.

The necessary information acquisition unit 222 acquires the type of information required for executing the permitted software for each piece of permitted software identified by the permitted software identification unit 221 . Hereinafter, information required for software execution will be referred to as "required information".

For example, the necessary information acquisition unit 222 inputs the type of permitted software acquired by the permitted software identification unit 221 into a database that associates the type of permitted software with the type of necessary information, and outputs the type of information output from the database. is acquired as the type of required information. In this case, the database may be stored in the storage unit of the software management device 22, for example.

The provided information acquisition unit 223 acquires the type of provided information from the vehicle 30 . For example, the provided information acquisition unit 223 acquires the type of provided information received by the server communication device 21 .
The applicable software identification unit 224 identifies the type of applicable software based on the type of necessary information acquired by the necessary information acquisition unit 222 and the type of provided information acquired by the provided information acquisition unit 223 . More specifically, the applicable software identification unit 224 determines the type of software that is permitted to be used by the user who is the driver of the vehicle 30 and that can function in the vehicle 30. Identify as Hereinafter, the software specified by the applicable software specifying unit 224 will be referred to as "applicable software".

For example, the applicable software identification unit 224 compares the type of necessary information acquired by the necessary information acquisition unit 222 with the type of provided information acquired by the provided information acquisition unit 223 for each piece of permitted software, and determines the type of required information for the permitted software. Identify the licensed software as applicable software if all of the information types are included in the provided information types.

The applicable software providing unit 225 provides the vehicle 30 with the types of functionable software identified by the applicable software identifying unit 224 . For example, the applicable software provider 225 transmits the type of applicable software from the server communication device 21 to the vehicle 30 .

<Portable device>
The mobile device 40 includes a display section 41 , an operation section 42 , a communication section 43 and a control device 44 . The display unit 41 , the operation unit 42 and the communication unit 43 are each connected to the control device 44 .

The display unit 41 displays information output from the control device 44 .
The operation unit 42 receives an operation by the user and outputs the content of the operation to the control device 44 . Hereinafter, the operation of the operation unit 42 by the user will be referred to as "user operation".

The communication unit 43 receives information transmitted from the vehicle 30 and outputs the information to the control device 44 . The communication unit 43 also transmits information output from the control device 44 to the vehicle 30 .
The control device 44 has a control section and a storage section. The storage unit stores a control program executed by the control unit.

The control device 44 functions as a user information transmission section 441, an applicable software acquisition section 442, an application software setting section 443, and a software application instruction section 444 by the control section executing the control program.

The user information transmission unit 441 transmits user information to the vehicle 30 . For example, the user information transmission unit 441 transmits user information stored in the storage unit of the control device 44 from the communication unit 43 to the vehicle 30 .

The applicable software acquisition unit 442 acquires the type of applicable software from the vehicle 30 . For example, the applicable software acquisition unit 442 acquires the type of applicable software received by the communication unit 43 .

The applicable software setting unit 443 sets the type of applicable software based on the type of applicable software acquired by the applicable software acquiring unit 442 .
For example, the applicable software setting unit 443 presents the types of applicable software to the user who is the driver of the vehicle 30 and accepts the user's intention to select the applicable software from the applicable software. Hereinafter, the user's intention to select applicable software from applicable software will be referred to as "user intention". The user's intention may be an intention not to select any applicable software as applicable software, an intention to select one applicable software, or an intention to select a plurality of applicable software. The applied software setting unit 443 sets the type of applied software based on the user's intention. For example, a screen display by the display unit 41 is conceivable for presenting the types of applicable software to the user. Receipt of a user's intention by the operation unit 42 may be considered as acceptance of a user's intention.

The software application instruction unit 444 instructs the vehicle 30 to apply software included in the type of application software set by the application software setting unit 443 to the vehicle 30 . For example, the software application instruction section 444 transmits the type of application software from the communication section 43 to the vehicle 30 .

The configuration of the software management system 10 has been described above with reference to FIG.
<Software management process flow>
Next, the flow of processing for managing software applied to the vehicle 30 by the software management system 10 will be described with reference to FIGS. 2 to 4. FIG. Henceforth, the process which manages the software applied to the vehicle 30 is called "software management process." The software management processing includes information provision processing executed in portable device 40 and vehicle 30, applicable software identification processing executed in server device 20, and software application processing executed in portable device 40 and vehicle 30. consists of

Here, the information providing process is a process of providing the server device 20 with user information and types of provided information. The applicable software identifying process is a process of identifying the type of applicable software based on the user information and the type of provided information and providing the type of applicable software to vehicle 30 . The software application process is a process of setting application software based on applicable software and applying the application software to vehicle 30 .

In this embodiment, it is assumed that an application for software management processing has been activated in the mobile device 40 .
FIG. 2 is a flowchart showing the flow of information providing processing.

In step S10, the control device 44 of the mobile device 40 determines whether or not the software management process has started. For example, the control device 44 determines whether or not an operation to start the software management process has been accepted on the application for the software management process. If the control device 44 determines that the software management process has not started (S10: NO), it ends the current process, and if it determines that the software management process has started (S10: YES), the process of step S11. transition to

In step S11 , the control device 44 transmits user information to the vehicle 30 by the user information transmitting section 441 .
In step S20 , the in-vehicle device 33 of the vehicle 30 acquires the user information transmitted from the mobile device 40 in step S11 by the user information provision unit 331 .

In step S21 , the in-vehicle device 33 acquires the type of provided information by the provided information providing unit 332 .
In step S22, the in-vehicle device 33 transmits the user information acquired in step S20 and the type of provided information acquired in step S21 to the server device 20 by the user information providing unit 331 and the provided information providing unit 332. do.

FIG. 3 is a flowchart showing the flow of applicable software identification processing.
In step S30 , the software management device 22 of the server device 20 acquires the user information transmitted from the vehicle 30 in step S22 by using the permitted software identification unit 221 .

In step S31, the software management device 22 uses the permitted software identification unit 221 to identify the type of permitted software based on the user information acquired in step S30.

In step S32, the software management device 22 acquires the type of necessary information regarding the permitted software by the necessary information acquisition unit 222 based on the type of permitted software identified in step S31.

In step S33 , the software management device 22 uses the provided information acquisition unit 223 to acquire the type of provided information transmitted from the vehicle 30 in step S22 .
In step S34, the software management apparatus 22 causes the applicable software identification unit 224 to identify the type of applicable software based on the type of necessary information obtained in step S32 and the type of provided information obtained in step S33. .

In step S35, the software management device 22 causes the applicable software providing unit 225 to transmit the type of applicable software identified in step S34 to the vehicle 30.

FIG. 4 is a flowchart showing the flow of software application processing.
In step S40 , the in-vehicle device 33 of the vehicle 30 receives the applicable software type transmitted from the server device 20 in step S35 by the applicable software transmission unit 333 .

In step S41, the in-vehicle device 33 uses the applicable software transmission unit 333 to transmit the type of applicable software received in step S40 to the portable device 40.

In step S50, the control device 44 of the portable device 40 uses the applicable software acquisition unit 442 to acquire the type of applicable software transmitted from the vehicle 30 in step S41.

In step S51, the control device 44 uses the applicable software setting unit 443 to present the type of applicable software acquired in step S50 to the user who is the driver of the vehicle 30.

In step S52 , the control device 44 uses the applicable software setting unit 443 to accept the user's intention to select the applicable software from the applicable software.
In step S53, the control device 44 sets the type of application software by the application software setting unit 443 based on the user's intention received in step S52.

In step S54 , the control device 44 causes the software application instructing section 444 to transmit the type of application software specified in step S53 to the vehicle 30 .
In step S42, the in-vehicle device 33 of the vehicle 30 acquires the type of application software transmitted from the portable device 40 in step S54.

In step S43, the in-vehicle device 33 applies the application software to the vehicle 30 based on the type of application software acquired in step S42.
<Effects of this embodiment>
(1-1) In this embodiment, the type of applicable software is specified based on the type of required information and the type of provided information. Therefore, it is possible to apply software selected from applicable software to the vehicle 30 or apply all of the applicable software to the vehicle 30 . As a result, it is possible to enhance convenience when using software that provides added value to the vehicle 30 .

(1-2) In this embodiment, applicable software is selected from applicable software. Therefore, software necessary for driving the vehicle 30 can be applied to the vehicle 30 as appropriate.

(1-3) In the present embodiment, the type of necessary information regarding permitted software is acquired. Thereby, the processing for acquiring the type of necessary information can be reduced.
(1-4) In the present embodiment, the server device 20 and the vehicle 30 are communicably connected. This makes it possible to improve the security of communication. Therefore, for example, when the applicable software has not been downloaded to the vehicle 30 , it is possible to adopt a specification in which the applicable software is downloaded from the server device 20 to the vehicle 30 .

(Second embodiment)
A second embodiment of the software management system will be described below with reference to FIGS. 5 and 6. FIG.
FIG. 5 is a block diagram showing an overview of the software management system 11 of this embodiment. In the second embodiment, the server device 20 and the vehicle 30 are communicably connected to each other in that the server device 20 and the mobile device 40 are communicably connected to each other via the mobile communication network NT. It differs from the first embodiment.

In the following description, configurations of the second embodiment that are the same as or correspond to configurations of the first embodiment are denoted by the same reference numerals as those of the first embodiment, and descriptions of the configurations are omitted.
<Vehicle>
The vehicle 30 includes a second vehicle communication device 32 , an in-vehicle device 33 and a vehicle display device 34 . The in-vehicle device 33 functions as a provided information transmission unit 335 and a software application unit 334 by the control unit executing a control program.

The provided information transmission unit 335 transmits the type of provided information to the mobile device 40 . For example, the provided information transmission unit 335 transmits the type of provided information stored in the storage unit of the in-vehicle device 33 from the second vehicle communication device 32 to the portable device 40 in response to a transmission request for the type of provided information from the portable device 40 . Send to

<Portable device>
The mobile device 40 includes a first communication section 45 and a second communication section 43 . The first communication unit 45 receives information transmitted from the server device 20 via the mobile communication network NT, and outputs the information to the control device 44 . The first communication unit 45 also transmits information output from the control device 44 to the server device 20 via the mobile communication network NT. The second communication section 43 is substantially the same as the communication section 43 of the first embodiment.

The control unit 44 of the mobile device 40 executes the control program, so that the user information providing unit 445, the provided information providing unit 446, the applicable software acquisition unit 442, the applicable software setting unit 443, and the software application instructing unit 444 function as

The user information providing unit 445 provides the server device 20 with user information. For example, the user information providing unit 445 transmits user information stored in the storage unit of the control device 44 from the first communication unit 45 to the server device 20 .

The provided information providing unit 446 acquires the type of provided information from the vehicle 30 and provides the information to the server device 20 . For example, the provided information providing unit 446 transmits a transmission request for the type of provided information from the second communication unit 43 to the vehicle 30, receives the type of provided information transmitted from the vehicle 30 at the second communication unit 43, The type of the provided information is transmitted from the first communication unit 45 .

The configuration of the software management system 11 has been described above with reference to FIG.
<Software management process flow>
Next, the flow of software management processing will be described with reference to FIG.

FIG. 6 is a flowchart showing the flow of information providing processing.
In step S211 , the control device 44 of the portable device 40 requests the vehicle 30 to transmit the type of provided information through the provided information providing unit 446 .

In step S220 , the in-vehicle device 33 of the vehicle 30 acquires the type of provided information by the provided information transmission unit 335 in response to the request in step S211 .
In step S221 , the in-vehicle device 33 transmits the type of provided information acquired in step S220 to the portable device 40 by the provided information transmission unit 335 .

In step S212, the control device 44 of the portable device 40 acquires the type of provided information transmitted from the vehicle 30 in step S221 by the provided information provision unit 446. FIG.
In step S213 , the control device 44 acquires user information through the user information providing unit 445 .

In step S214, the control device 44 causes the user information providing unit 445 and the provided information providing unit 446 to send the user information acquired in step S213 and the type of provided information acquired in step S212 to the server device 20. .

The applicable software identifying process of the second embodiment is different in that the transmission source of the types of user information and provided information is the mobile device 40, and the transmission destination of the type of applicable software is the mobile device 40. This is substantially the same as the applicable software identifying process of the first embodiment.

The software application process of the second embodiment is substantially the same as the software application process of the first embodiment, except that the mobile device 40 acquires the type of applicable software from the server device 20 without going through the vehicle 30. be.

Specifically, in the process corresponding to step S50 in FIG. 4, the control device 44 of the mobile device 40 uses the applicable software acquisition section 442 to acquire the type of applicable software transmitted from the server device 20. FIG.

<Effects of this embodiment>
The second embodiment has the following effect (2-1) in addition to the effects (1-1) to (1-3) of the first embodiment.

(2-1) In the present embodiment, the server device 20 and the mobile device 40 are communicably connected. This eliminates the need to transmit the user information to the vehicle 30, so that leakage of personal information can be suppressed.

(Change example)
The multiple embodiments described above can be implemented with the following modifications. Each of the above-described embodiments and the following modifications can be implemented in combination with each other within a technically consistent range.

- In the above embodiments, the application software is set in the portable device 40, but the application software may be set in the vehicle 30 as well.
For example, in the first embodiment, as shown in FIG. 7, a function 336 corresponding to the applicable software acquisition unit 442 and a function 337 corresponding to the applicable software setting unit 443 of the portable device 40 are implemented in the vehicle 30. good too.

In this case, the function 336 corresponding to the applicable software acquisition unit 442 acquires the type of applicable software received by the first vehicle communication device 31 . A function 337 corresponding to the applicable software setting unit 443 displays the type of applicable software on the vehicle display device 34, receives the user's intention at the operation unit of the vehicle 30 (not shown), and sets the type of applicable software based on the user's intention. set. Software application unit 334 of vehicle 30 applies the application software specified by function 336 corresponding to application software setting unit 443 to vehicle 30 .

Further, in the second embodiment, the function of transmitting the type of applicable software to the vehicle 30 is implemented in the portable device 40, and the functions corresponding to the applicable software acquisition unit 442 and the applicable software setting unit 443 of the portable device 40 are It may be mounted on the vehicle 30 .

In this case, the function of transmitting the type of applicable software to the vehicle 30 transmits the type of applicable software received by the first communication unit 45 from the second communication unit 43 to the vehicle 30 . A function corresponding to the applicable software acquisition unit 442 acquires the type of applicable software received by the second vehicle communication device 32 . A function corresponding to the applied software setting unit 443, a function corresponding to the applied software setting unit 443, and a function of the software application unit 334 of the vehicle 30 are substantially the same as those of this modification according to the first embodiment.

In this modified example, the display unit 41 and the operation unit 42 of the mobile device 40 can be eliminated. Therefore, the portable device 40 may be a card containing an integrated circuit.
- In the above embodiments, the server device 20 identifies the applicable software, but the vehicle 30 may identify the applicable software.

For example, in the first embodiment, as shown in FIG. A function 339 corresponding to the applicable software identification unit 224 may be implemented in the vehicle 30 .

In this case, the function 226 for providing the type of necessary information to the vehicle 30 identifies the type of necessary information in the same manner as the necessary information acquisition unit 222 of the first embodiment, and receives the type of necessary information from the server communication device 21. Send. A function 338 corresponding to the provided information acquisition unit 223 acquires the type of provided information stored in the storage unit of the in-vehicle device 33 . A function 339 corresponding to the applicable software identification unit 224 is a function 226 for providing the type of necessary information to the vehicle 30, and a function 338 corresponding to the provided information obtaining unit 223. Identify the types of applicable software based on the type of information.

Further, in the second embodiment, the function of transmitting the type of necessary information to the portable device 40 is implemented in the server device 20, the function of transmitting the type of necessary information to the vehicle 30 is implemented in the portable device 40, and the server device 20 may be implemented in the vehicle 30 .

In this case, the function of transmitting the type of necessary information to the portable device 40 transmits the type of necessary information from the server communication device 21 . The function of transmitting the type of necessary information to the vehicle 30 transmits the type of necessary information from the second communication unit 43 . A function corresponding to the provided information acquisition unit 223 acquires the type of provided information stored in the storage unit of the in-vehicle device 33 . The function corresponding to the applicable software specifying unit 224 is to identify the type of necessary information transmitted by the function of transmitting the type of necessary information to the vehicle 30 and the type of provided information acquired by the function corresponding to the provided information acquiring unit 223. Identify the types of applicable software based on

- In the above embodiments, the server device 20 identifies the applicable software, but the mobile device 40 may identify the applicable software.
For example, in the second embodiment, the function of transmitting the type of necessary information to the portable device 40 is implemented in the server device 20, the function of transmitting the type of provided information to the portable device 40 is implemented in the vehicle 30, and the server device 20 The functions corresponding to the necessary information acquisition unit 222 , the provided information acquisition unit 223 , and the applicable software identification unit 224 may be implemented in the portable device 40 .

In this case, the function of transmitting the type of necessary information to the portable device 40 transmits the type of necessary information acquired by the necessary information acquisition unit 222 from the server communication device 21 . The function of transmitting the type of provided information to the portable device 40 transmits the type of provided information stored in the storage unit of the in-vehicle device 33 from the second vehicle communication device 32 . A function corresponding to the necessary information acquisition unit 222 acquires the type of necessary information received by the first communication unit 45 . A function corresponding to the provided information acquisition unit 223 acquires the type of provided information received by the second communication unit 43 . The function corresponding to the applicable software identification unit 224 is to determine the type of required information acquired by the function corresponding to the required information acquisition unit 222 and the type of provided information acquired by the function equivalent to the provided information acquisition unit 223. Identify the types of applicable software based on

Further, in the first embodiment, the function of transmitting the type of necessary information to the vehicle 30 is implemented in the server device 20, and the function of transmitting the type of required information and the type of provided information to the portable device 40 is implemented in the vehicle 30. , functions corresponding to the necessary information acquisition unit 222 , the provided information acquisition unit 223 , and the applicable software identification unit 224 of the server device 20 may be implemented in the portable device 40 .

In this case, the function of transmitting the type of necessary information to the vehicle 30 transmits the type of necessary information from the server communication device 21 . The function of transmitting the type of necessary information to the portable device 40 transmits the type of necessary information received by the first vehicle communication device 31 from the second vehicle communication device 32 . The function of transmitting the type of provided information to the portable device 40 transmits the type of provided information stored in the storage unit of the in-vehicle device 33 from the second vehicle communication device 32 . A function corresponding to the necessary information acquisition unit 222 acquires the type of necessary information received by the communication unit 43 . A function corresponding to the provided information acquisition unit 223 acquires the type of provided information received by the communication unit 43 . A function corresponding to the applicable software identification unit 224 is substantially the same as that of this modification according to the second embodiment.

- In the above embodiments, the server device 20 acquires the necessary information, but the vehicle 30 may acquire the necessary information.
For example, in the first embodiment, the server device 20 may have a function of transmitting the type of permitted software to the vehicle 30 , and the vehicle 30 may have a function corresponding to the necessary information acquisition unit 222 of the server device 20 .

In this case, the function for transmitting the type of permitted software to the vehicle 30 transmits the type of permitted software identified by the permitted software identification unit 221 from the server communication device 21 . A function corresponding to the necessary information acquisition unit 222 acquires necessary information based on the type of permitted software received by the first vehicle communication device 31 .

Further, in the second embodiment, the function of transmitting the type of permitted software to the portable device 40 is implemented in the server device 20, the function of transmitting the type of permitted software to the vehicle 30 is implemented into the portable device 40, and the server device 20 may be implemented in the vehicle 30.

In this case, the function for transmitting the type of permitted software to the portable device 40 transmits the type of permitted software from the server communication device 21 . The function of transmitting the type of permitted software to vehicle 30 transmits the type of permitted software received by first communication unit 45 from second communication unit 43 to vehicle 30 . A function corresponding to the necessary information acquisition unit 222 acquires necessary information based on the type of permitted software received by the second vehicle communication device 32 .

- In the above embodiments, the server device 20 acquires the necessary information, but the portable device 40 may acquire the necessary information.
For example, in the second embodiment, even if the function of transmitting the type of permitted software to the mobile device 40 is implemented in the server device 20 and the function corresponding to the necessary information acquisition unit 222 of the server device 20 is implemented in the mobile device 40, good.

In this case, the function for transmitting the type of permitted software to the portable device 40 transmits the type of permitted software identified by the permitted software identification unit 221 from the server communication device 21 . A function corresponding to the necessary information acquisition unit 222 acquires the type of necessary information based on the type of permitted software received by the first communication unit 45 .

Further, in the first embodiment, the function of transmitting the type of permitted software to the vehicle 30 is implemented in the server device 20, the function of transmitting the type of permitted software to the mobile device 40 is implemented in the vehicle 30, and the necessary information acquisition unit 222 may be implemented in the mobile device 40 .

In this case, the function for transmitting the type of permitted software to the vehicle 30 transmits the type of permitted software from the server communication device 21 . The function of transmitting the type of permitted software to the portable device 40 transmits the type of permitted software received by the first vehicle communication device 31 from the second vehicle communication device 32 . A function corresponding to the necessary information acquisition unit 222 acquires the type of necessary information based on the type of permitted software received by the communication unit 43 .

· In the above embodiments, the user's intention to select applicable software from applicable software is accepted, but the type of applicable software may be automatically set based on the type of applicable software. For example, in the above embodiments, the applicable software setting unit 443 may set all applicable software as applicable software.

- In the above multiple embodiments, applicable software is identified by comparing the type of required information and the type of provided information regarding licensed software. However, if all users are permitted to use all software, or if there are only a few types of software managed by the software management system, the types of required information and the types of provided information regarding all software You may make it compare.

· In the above embodiments, the type of provided information is acquired from the vehicle 30 , but information related to the type of provided information may be acquired from the vehicle 30 . Here, as the information related to the type of provided information, information identifying an individual vehicle 30, information indicating whether or not a predetermined device is mounted on the vehicle 30, information indicating whether or not a predetermined device is mounted on the vehicle 30, and information on a predetermined device mounted on the vehicle 30. Information indicating the type of clothing may be considered. Here, the predetermined device may be a sensor that detects the state of the vehicle 30, an image capturing device that captures images of the inside and outside of the vehicle, a radar device that measures the distance and direction to surrounding objects of the vehicle 30, and a communication device.

For example, in the first embodiment, the provided information providing unit 332 of the vehicle 30 transmits information related to the type of provided information stored in the storage unit of the in-vehicle device 33 from the first vehicle communication device 31 to the server device 20. Send. The provided information acquisition unit 223 of the server device 20 acquires the type of provided information based on the information related to the type of provided information received by the server communication device 21 .

Further, in the second embodiment, the provided information transmitting unit 335 of the vehicle 30 transmits information related to the type of provided information stored in the storage unit of the in-vehicle device 33 from the second vehicle communication device 32 to the portable device 40. Send. The provided information providing unit 446 of the mobile device 40 transmits information related to the type of provided information received by the second communication unit 43 from the first communication unit 45 to the server device 20 . The provided information acquisition unit 223 of the server device 20 acquires the type of provided information based on the information related to the type of provided information received by the server communication device 21 .

· A dedicated hardware circuit may be provided for hardware processing at least a part of what is software-processed in each of the above embodiments. An example of a dedicated hardware circuit is an ASIC.

Next, technical ideas that can be grasped from the above-described multiple embodiments and modified examples will be described.
(a) It is preferable to include a permitted software identification unit that identifies the permitted software based on driver information that identifies the driver of the vehicle.

(b) Preferably, the provided information acquisition unit acquires the type of provided information based on information related to the type of provided information.
(c) The provided information acquisition unit indicates whether or not a predetermined detection device or a predetermined communication device is installed in the vehicle, as information indicating the type of the provided information. It is preferable to obtain at least one of information and information indicating the type of a predetermined detection device or the type of a predetermined communication device installed in the vehicle.

(2) A software management system comprising the vehicle, a server device installed outside the vehicle, and a portable device carried by the driver of the vehicle, wherein the necessary information acquisition unit is provided in the server device, preferably a software management system.

Here, the type of required information is information that is more relevant to software than other information. Therefore, the software management system can be simplified by providing the necessary information acquisition unit in the server device.

(e) In the software management system, it is preferable that the applicable software identifying unit is provided in the server device. This allows simplification of the vehicle and portable device.

(f) In the software management system, it is preferable that the provided information acquisition unit and the applicable software identification unit are provided in the vehicle. Here, the type of provided information has a stronger relationship with the vehicle than other information. Therefore, the software management system can be simplified by providing the provided information acquisition section and the applicable software identification section in the vehicle.

(g) In the software management system, it is preferable that the applicable software setting section is provided in the portable device. This makes it possible to improve the user interface when selecting applicable software.

(h) In the software management system, it is preferable that the applicable software setting section is provided in the vehicle. As a result, a mobile device that does not have a display unit or an operation unit can be used in the software management system.

(i) The software management system includes a provided information providing unit provided in the vehicle for providing information related to the type of the provided information to the server device or the portable device, wherein the provided information acquisition unit It is preferable to acquire the type of the provided information based on the information provided by the information providing unit.

(j) In the software management system, the vehicle or the portable device includes a driver information providing unit that provides the driver information to the server device, and the permitted software identification unit is provided in the server device. preferably.

(i) A software management device that identifies software to be applied to the vehicle from a plurality of software that provides added value to the vehicle, wherein the types of necessary information necessary for the software to function in the vehicle are: a necessary information acquisition unit that acquires each software; a provided information acquisition unit that acquires a type of provided information provided to the vehicle; and a type of the required information acquired by the necessary information acquisition unit and the provided information acquisition. and an applicable software identification unit that identifies the type of applicable software applicable to the vehicle from the plurality of software based on the type of the provided information acquired by the unit. .

(l) A software management program that identifies software to be applied to the vehicle from a plurality of software that provides added value to the vehicle. a necessary information obtaining step for obtaining each piece of software; a provided information obtaining step for obtaining a type of provided information provided to the vehicle; and a type of the necessary information obtained by the necessary information obtaining unit and the provided information obtaining. and an applicable software identification step of identifying the type of applicable software applicable to the vehicle from the plurality of software based on the type of the provided information acquired by a unit. .

Claims

A software management system that identifies software to be applied to the vehicle from among a plurality of software that provides added value to the vehicle,
a necessary information acquisition unit that acquires, for each piece of software, a type of necessary information necessary for the software to function in the vehicle;
a provided information acquisition unit that acquires a type of provided information provided to the vehicle;
Types of applicable software that can be applied to the vehicle from a plurality of pieces of software based on the type of the necessary information acquired by the necessary information acquisition unit and the type of the provided information acquired by the provided information acquisition unit an applicable software identification portion that identifies
A software management system characterized by:
2. The software management system according to claim 1, wherein said necessary information acquisition unit acquires the type of said necessary information relating to permitted software that is permitted to be used by a driver of said vehicle among said plurality of pieces of software.
an applicable software setting unit configured to set a type of applicable software to be applied to the vehicle based on the type of applicable software identified by the applicable software identifying unit;
3. The software management system according to claim 1 or 2.
The applicable software setting unit presents the types of the applicable software specified by the applicable software specifying unit to the driver of the vehicle, and selects the type of the applicable software from the types of the applicable software. receiving the intention of the driver and setting the application software based on the intention of the driver;
A software management system according to claim 3.