Function Management System and Function Management Method

Abstract

To smoothly utilize an option function by allowing for quickly presenting whether or not execution of the option function in a vehicle can be prepared to a user.SOLUTION: A function management system comprises: an information collection unit which collects failure information including information about failure of an electronic control device mounted on a vehicle and / or information about failure of devices controlled by the electronic control device; and a determination unit which determines whether or not execution for use start can be prepared for each of option functions.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present invention relates to a function management system and a function management method for managing the use of optional functions in a vehicle.

Background Art

[0002] In recent years, efforts have been actively made to provide access to a sustainable transportation system that takes into account people in vulnerable positions among traffic participants. In order to achieve this, research and development on driving support technologies have been focused on further improving traffic safety and convenience.

[0003] In addition, in recent years, when selling a vehicle, in addition to the devices for realizing the standard functions in the vehicle, devices and equipment capable of realizing optional functions are installed in the vehicle, and after the vehicle is sold, it is possible to execute the optional functions in response to requests from users.

[0004] Patent Document 1 describes an information processing device that changes the usage settings of options installed in a vehicle according to the purpose of use. In this information processing device, when the purpose of using the vehicle is for business, the use of all options is enabled, and when the purpose of using the vehicle is for personal use, the use of at least one option is restricted.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] By the way, in driving support technologies, in order to improve the convenience of vehicle users, it is an issue to appropriately manage the failures of devices and equipment related to the optional functions of the vehicle and smoothly prepare for the execution of those optional functions.

[0007] The present application aims to smooth the use of optional functions by promptly presenting to the user whether the execution preparation of the optional function is possible when a request for using an optional function is received from a vehicle user, thereby contributing to the development of a sustainable transportation system.

Means for Solving the Problems

[0008] One aspect of the present invention is a function management system for managing the use of optional functions in a vehicle, including an information collection unit that collects failure information including information about failures of an electronic control unit mounted on the vehicle and / or information about failures of devices controlled by the electronic control unit, and a determination unit that determines for each of the optional functions whether execution preparation for starting use is possible. A notification unit that presents a list of the optional functions to the user via the terminal device and comprising , based on the failure information, for each of the optional functions, the determination unit determines that the execution preparation of the optional function is possible when no failure is found in the electronic control device and the device required for the execution of the optional function, and determines that the execution preparation of the optional function is not possible when a failure is found in the electronic control device or the device required for the execution of the optional function. The notification unit presents the optional functions determined to be ready for execution in the list a function management system. Another aspect of the present invention is a function management method performed by a computer of a function management system for managing the use of optional functions in a vehicle, including an information collection step of collecting failure information including information about failures of an electronic control unit mounted on the vehicle and / or information about failures of devices controlled by the electronic control unit, and a determination step of determining for each of the optional functions whether execution preparation for starting use is possible. , in the determination step, based on the failure information, for each of the optional functions, the determination unit determines that the execution preparation of the optional function is possible when no failure is found in the electronic control device and the device required for the execution of the optional function, and determines that the execution preparation of the optional function is not possible when a failure is found in the electronic control device or the device required for the execution of the optional function. In the notification step, the optional functions determined to be ready for execution in the list are presented, machine a function management method.

Effects of the Invention

[0009] According to the present invention, when a request for using an optional function is received from a vehicle user, it is possible to promptly present to the user whether the execution preparation of the optional function is possible, thereby smoothing the use of the optional function.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. [1. Configuration of Function Management System] FIG. 1 is a diagram showing the configuration of a function management system 1 according to an embodiment of the present invention. The function management system 1 includes a vehicle management device 3 mounted on a vehicle 2, a management server 4 which is a server device provided outside the vehicle 2, and a terminal device 6 possessed by a user U who uses the vehicle 2. The vehicle management device 3, the management server 4, and the terminal device 6 are communicably connected to each other via a communication network 5 such as the Internet, for example.

[0012] The vehicle 2 is, for example, a vehicle driven by an electric or internal combustion engine. The terminal device 6 may be a portable or mobile terminal device such as a smartphone, a tablet PC, or a notebook PC, or a stationary terminal device such as a desktop PC. In the present embodiment, the terminal device 6 is, for example, a smartphone possessed by the user U.

[0013] User U operates the terminal device 6 to select an option function of the vehicle 2 and transmits a request for starting its use to the management server 4. In response to receiving the request for starting use, the management server 4 instructs the vehicle management device 3 of the vehicle 2 to prepare for executing the option function specified by the above request.

[0014] [2. Operation Overview of the Function Management System] The function management system 1 executes a preparation determination process and a function start process. The preparation determination process is a process of determining whether it is possible to prepare for execution for starting use for each option function. The function start process is a process of preparing so that the option function specified by the request can be executed in the vehicle 2 in response to a request from the user U. Here, the preparation for executing the option function may include installing a software program necessary for executing the option function in a related electronic control device and / or giving permission for executing the option function to the related electronic control device (or setting permission for executing the option function for the related electronic control device).

[0015] In the preparation determination process, the vehicle management device 3 collects failure information including information about failures of the electronic control devices provided in the vehicle 2 and information about failures of the devices controlled by those electronic control devices. The management server 4 acquires the failure information from the vehicle management device 3 and determines, based on the failure information, whether it is possible to prepare for the user U to start using each option function of the vehicle 2. For example, based on the failure information, when a failure is found in an electronic control device or a device necessary for executing an option function for each option function, the management server 4 determines that the preparation for executing the option function is not possible. The management server 4 stores the determination result of whether it is possible to prepare for execution for each option function as management information.

[0016] As a result, in the function management system 1, it is possible to detect, prior to a request from the user U to use an option function, an option function that cannot be prepared for execution due to a failure of the electronic control device or equipment. Therefore, it is possible to quickly inform the user whether or not the option function can be prepared for execution, thereby facilitating the use of the option function.

[0017] In the function start process, the management server 4 displays a list of option functions on the terminal device 6 in response to a request from the user U via the terminal device 6. The user U can select a desired option function from this list and request its start of use. When the management server 4 receives a request for start of use of any option function from the terminal device 6, the management server 4 refers to the determination result of whether or not the option function can be prepared for execution, which was stored in the above-mentioned preparation determination process, and determines whether or not the option function for which start of use is requested can be prepared for execution. Then, when the option function is determined to be unprepared for execution, the management server 4 notifies the user U via the terminal device 6 that the option function cannot be used.

[0018] On the other hand, when the option function for which start of use is requested is determined to be prepared for execution, the management server 4 performs a charging process for the usage fee of the option function, and then instructs the vehicle management device 3 to prepare for execution of the option function. The usage fee may be, for example, a monthly usage fee for each option function. The vehicle management device 3 that has received the instruction to prepare for execution installs the software program required for the execution of the option function for which start of use is requested in the electronic control device related to the option function.

[0019] In the present embodiment, in particular, the vehicle management device 3 installs the software program of the option function determined to be prepared for execution in accordance with the instruction to prepare for execution of the option function, and does not install the software program of the option function determined to be unprepared for execution. This can avoid the installation of unnecessary software programs, thereby reducing the processing load of the vehicle management device 3 and the processing load of the electronic control device.

[0020] Next, the configurations of the vehicle management device 3, the management server 4, and the terminal device 6 will be sequentially described. [3. Configuration of Vehicle Management Device] First, the vehicle management device 3 provided in the vehicle 2 will be described. FIG. 2 is a diagram showing the configuration of the vehicle management device 3. The vehicle management device 3 is communicably connected to an aECU (Electronic Control Unit) 11a, a bECU 11b, a cECU 11c, a dECU 11d, a TCU (Telematics Control Unit) 13, and an IVI (In-Vehicle Infotainment) unit 14 via an in-vehicle network bus 10 provided in the vehicle 2.

[0021] The aECU 11a, bECU 11b, cECU 11c, and dECU 11d are electronic control devices in the present disclosure, and each controls an a device 12a, b device 12b, c device 12c, and d device 12d. Hereinafter, the aECU 11a, bECU 11b, cECU 11c, and dECU 11d will also be collectively referred to as the ECU 11, and the a device 12a, b device 12b, c device 12c, and d device 12d will also be collectively referred to as the device 12. Each ECU 11 can execute various optional functions of the vehicle 2 alone or in cooperation with other ECUs 11.

[0022] Each ECU 11 performs self-diagnosis of its own operation failure and failure diagnosis of the device 12 it controls, for example, periodically at a predetermined timing, during the period when the vehicle power switch 18 is in the on state and power supply is being performed, and generates failure information indicating the diagnosis result. Each ECU 11 transmits the generated failure information to the vehicle management device 3. Here, the above failures may include software abnormalities and / or hardware failures.

[0023] The TCU 13 includes a wireless communication device for communicating with the management server 4 and the terminal device 6 via the communication network 5. The IVI unit 14 displays images and videos on the first touch panel 15 and outputs sound from the first speaker 16 in accordance with an instruction from the user U via the first touch panel 15, thereby providing information such as route guidance and entertainment such as music and videos. The IVI unit 14 may also include a first communication device 17 that communicates with the terminal device 6 brought into the passenger compartment of the vehicle 2 by short-range wireless communication such as Bluetooth (registered trademark) or by wired communication via USB (registered trademark).

[0024] The vehicle management device 3 includes a first processor 20 and a first memory 21. The first memory 21 is constituted by, for example, a volatile and / or non-volatile semiconductor memory, and / or a hard disk device or the like.

[0025] The first processor 20 is a computer including, for example, a CPU or the like. The first processor 20 may have a configuration including a ROM in which a program is written, a RAM for temporarily storing data, and the like. The first processor 20 includes an information collection unit 23 and an installation management unit 24 as functional elements or functional units.

[0026] These functional elements included in the first processor 20 are realized, for example, when the first processor 20, which is a computer, executes the first program 22 stored in the first memory 21. The first program 22 can be stored in any computer-readable storage medium. Alternatively, all or part of the above functional elements included in the first processor 20 can be configured by hardware including one or more electronic circuit components.

[0027] The information collection unit 23 collects failure information from the ECU 11 and transmits it to the management server 4. Specifically, when the vehicle power switch 18 is switched to the on state, the information collection unit 23 collects failure information from the ECU 11 and transmits it to the management server 4. In addition to this, when the information collection unit 23 receives failure information from the ECU 11 in which a failure has been detected during the period in which the vehicle power switch 18 is on, the received failure information may be transmitted to the management server 4.

[0028] The installation management unit 24 manages the installation of software programs to the ECU 11. In the present embodiment, in particular, the installation management unit 24 installs the software programs of the option functions determined to be ready for execution in the management server 4, and does not install the software programs of the option functions determined not to be ready for execution.

[0029] Specifically, when the installation management unit 24 receives an execution preparation instruction from the management server 4, in accordance with the received execution preparation instruction, for the ECU 11 related to the option function determined to be ready for execution and permitted to execute, the software program necessary for the execution of the option function is downloaded from the management server 4 and installed. Further, after the completion of the above installation, the installation management unit 24 permits the execution of the above option function for the above related ECU 11.

[0030] In addition, when the software program necessary for the execution of the option function has already been installed in the ECU 11 related to the option function for which execution is not permitted in the received execution preparation instruction, the installation management unit 24 prohibits the execution of the option function for the ECU 11. For example, when the user U has finished using an option function after using it, an option function for which execution is not permitted may be notified to the vehicle management device 3 in the execution preparation instruction.

[0031] In addition, when the installation management unit 24 determines that execution preparation is possible and execution of an option function is permitted in the ECU 11 related to the option function, if the software program necessary for execution of the option function has already been installed in the ECU 11, the installation management unit 24 only permits execution of the option function for the ECU 11 and does not install the software program redundantly. For example, when the user U has finished using an option function after using it, the software program for the option function may remain installed in the ECU 11.

[0032] In addition, in the present embodiment, the installation management unit 24 performs installation of the software program for the ECU 11 during a period when the vehicle power switch 18 is turned off. Thereby, for example, a situation can be prevented in which, for any ECU 11 that performs processing necessary for traveling of the vehicle 2, installation processing of a software program for an option function is performed during traveling of the vehicle 2, and the safety of vehicle traveling deteriorates.

[0033] For example, when receiving an execution preparation instruction, the installation management unit 24 downloads the software program to be installed in the ECU 11 from the management server 4 and stores it in the first memory 21 or stores it in the corresponding ECU 11. Then, the installation management unit 24 installs the downloaded software program in the corresponding ECU 11 during a period when the vehicle power switch 18 is turned off.

[0034] [4. Configuration of Management Server] Next, the management server 4 will be described. FIG. 4 is a diagram showing the configuration of the management server 4. The management server 4 includes a second processor 30, a second memory 31, and a second communication device 32. The second communication device 32 is a communication device for the management server 4 to communicate with the vehicle management device 3 and the terminal device 6 via the communication network 5.

[0035] The second memory 31 is constituted by, for example, a volatile and / or non-volatile semiconductor memory, and / or a hard disk device or the like. Management information 33 is stored in the second memory 31. The management information 33 includes a user ID for identifying the user U, a vehicle ID for identifying the vehicle 2, access information for communicating with the vehicle management device 3 of the vehicle 2, charging information (for example, bank account information or credit card information) for receiving payment of fees related to the option function from the user U, and information about the option function of the vehicle 2.

[0036] FIG. 7 is a diagram showing an example of the management information 33 stored in the second memory 31. In the illustrated example, the management information 33 is shown in tabular form. From the left of the illustrated table, the first column is the user ID, the second column is the vehicle ID, the third column is the access information, and the fourth column is the charging information.

[0037] The fifth to ninth columns of the illustrated table are information about the option function of the vehicle 2. The fifth column is the name of the option function, and the sixth and seventh columns are lists of the ECUs 11 (related ECUs) and devices 12 (related devices) involved in the operation of each option function, respectively. The eighth column shows information on whether the execution preparation of each option function is possible (information on execution preparation availability), and the ninth column shows information on whether the execution of each option function is permitted (information on execution permission).

[0038] For example, when there are a plurality of vehicles 2 that are shared cars and a plurality of users U can use their respective vehicles 2, the management information 33 can hold the information from the first column to the ninth column for each combination of the user U and the vehicle 2, for example.

[0039] Here, the user ID, vehicle ID, access information, and charging information can be obtained from the user U in advance via the terminal device 6 according to the prior art and stored in the management information 33.

[0040] In addition, the name of the option function in the fifth column, the list of related ECUs in the sixth column, and the list of related devices in the seventh column are preset according to the specifications of the vehicle 2. The information regarding whether execution is ready in the eighth column is stored or updated by the determination unit 36 of the management server 4 described later. The information regarding whether execution is permitted in the ninth column is all "prohibited" by default and is updated by the permission unit 38 described later.

[0041] Referring to FIG. 3, the second processor 30 is a computer including, for example, a CPU or the like. The second processor 30 may have a configuration including a ROM in which a program is written, a RAM for temporarily storing data, and the like. And the second processor 30 includes, as functional elements or functional units, a reception unit 35, a determination unit 36, a notification unit 37, a permission unit 38, and a distribution unit 39.

[0042] These functional elements included in the second processor 30 are realized, for example, when the second processor 30, which is a computer, executes the second program 34 stored in the second memory 31. Note that the second program 34 can be stored in any computer-readable storage medium. Alternatively, all or part of the above functional elements included in the second processor 30 can also be configured by hardware including one or more electronic circuit components.

[0043] The reception unit 35 receives a function list request and a function start request from the terminal device 6 described later. When the reception unit 35 receives a function list request and when it receives a function start request, it refers to the management information 33 in the second memory 31 respectively, and authenticates the validity of the function list request and the function start request based on the user ID included in the function list request and the function start request. For example, when the user ID included in the received function list request and function start request is included in the management information 33, the reception unit 35 determines that the function list request and the function start request are valid.

[0044] When the received function list request is legitimate, the reception unit 35 sends the received function list request to the determination unit 36 and the notification unit 37. Also, when the received function start request is legitimate, the reception unit 35 sends the received function start request to the notification unit 37 and the permission unit 38.

[0045] The determination unit 36 determines, for each of the optional functions of the vehicle 2, whether execution preparation for use start is possible. In the present embodiment, in particular, the determination unit 36 determines, for each of the optional functions, that execution preparation of the optional function is possible when no failure is found in the ECU 11 and the device 12 necessary for the execution of the optional function based on the failure information transmitted from the information collection unit 23 of the vehicle management device 3 provided in the vehicle 2. Also, when a failure is found in the necessary ECU 11 or device 12, the determination unit 36 determines that execution preparation of the optional function is impossible.

[0046] Specifically, the determination unit 36 determines the possibility or impossibility of execution preparation for each of the optional functions based on the failure information transmitted from the information collection unit 23 of the vehicle management device 3 when the vehicle power switch 18 of the vehicle 2 is turned on. Thereby, the determination unit 36 can determine the possibility or impossibility of execution preparation of the optional function based on the latest failure information even during a period in which the communication state between the vehicle management device 3 and the management server 4 changes, such as when the vehicle 2 is running.

[0047] Also, when the determination unit 36 receives, from the vehicle management device 3, failure information from the ECU 11 in which a failure has been found during the period in which the vehicle power switch 18 of the vehicle 2 is turned on, the determination unit 36 also determines the possibility or impossibility of execution preparation for each of the optional functions based on the received failure information. Thereby, the determination unit 36 can make a determination on the possibility or impossibility of execution preparation for the optional function by reflecting the most recent failure situation in any of the ECUs 11 or any of the devices 12.

[0048] The determination unit 36 updates the management information 33 stored in the second memory 31 based on the determination result of the possibility or impossibility of execution preparation for each of the optional functions.

[0049] The notification unit 37 notifies the user U via the terminal device 6. When the notification unit 37 receives a function list request from the terminal device 6 via the reception unit 35, based on the management information 33 in the second memory 31, it transmits a function list, which is a list of optional functions of the vehicle 2, to the terminal device 6. The terminal device 6 displays the received function list. The user U can select an optional function for which utilization is to be started from the function list displayed on the terminal device 6. The terminal device 6 transmits a function start request for the optional function selected by the user to the management server 4.

[0050] When the notification unit 37 receives a function start request from the terminal device 6 via the reception unit 35, if the optional function requested by the function start request is not determined to be ready for execution, it notifies the user U via the terminal device 6 that the said optional function cannot be used. Specifically, when the notification unit 37 receives a function start request, it refers to the management information 33 in the second memory 31 and obtains a determination result on whether the optional function requested by the function start request is ready for execution. Then, when it is determined that the optional function is not ready for execution, the notification unit 37 instructs the terminal device 6 to send a preparation unavailable notification, which is a notification that the said optional function cannot be used. The preparation unavailable notification can be, for example, a text message and / or an audio message such as "Currently, that function cannot be used. Please consult the nearest dealer."

[0051] When the permission unit 38 receives a function start request from the terminal device 6 via the reception unit 35, if the optional function requested by the function start request is ready for execution, it performs a charging process on the user U for the fee related to the utilization of the said optional function. The fee to be charged can be, for example, the monthly usage fee of the said optional function. When the charging process on the user U is completed, the permission unit 38 updates the execution permission information for the corresponding optional function stored in the management information 33 in the second memory 31 to "permitted" and transmits an execution preparation instruction for the said optional function to the vehicle 2.

[0052] In response to a request from the vehicle management device 3 of the vehicle 2, the distribution unit 39 transmits to the vehicle management device 3 the software program required by the vehicle management device 3. Note that the software program can be stored, for example, in the second memory 31 (not shown in FIG. 3).

[0053] [5. Configuration of the terminal device] Next, the terminal device 6 held by the user U of the vehicle 2 will be described. As described above, in this embodiment, the terminal device 6 is, for example, a smartphone.

[0054] FIG. 4 is a diagram showing the configuration of the terminal device 6. The terminal device 6 includes a third communication device 46, a second touch panel 47, and a second speaker 48. The third communication device 46 is a wireless communication device for the terminal device 6 to communicate with the management server 4 via the communication network 5. In addition to this, the third communication device 46 may include a wireless communication device that performs short-range wireless communication such as Bluetooth communication and a wired communication device that communicates by wired communication via USB.

[0055] The terminal device 6 also includes a third processor 40 and a third memory 41. The third memory 41 is configured by, for example, a volatile and / or non-volatile semiconductor memory or the like.

[0056] The third processor 40 is, for example, a computer including a CPU or the like. The third processor 40 may have a configuration including a ROM in which a program is written, a RAM for temporarily storing data, and the like. And the third processor 40 includes, as functional elements or functional units, a request unit 43, a display control unit 44, and a notification output unit 45.

[0057] These functional elements provided by the third processor 40 are realized, for example, when the third processor 40, which is a computer, executes a third program 42 stored in a third memory 41. The third program 42 is, for example, an application program, and can be downloaded from a program distribution server (not shown) connected to the communication network 5 or the like, or can be read from and used from an arbitrary computer-readable storage medium in which it is pre-stored. Alternatively, all or part of the above functional elements provided by the third processor 40 can also be configured by hardware including one or more electronic circuit components respectively.

[0058] The request unit 43 transmits a function list request for requesting a function list including a list of option functions of the vehicle 2 to the management server 4 according to an instruction from the user U input via the second touch panel 47. The function list request may include the user ID of the user U and the vehicle ID of the vehicle 2. As described above, the management server 4 transmits the function list to the terminal device 6 in response to receiving the function list request. The display control unit 44 (described later) of the terminal device 6 displays the transmitted function list on the second touch panel 47.

[0059] The request unit 43 also transmits a function start request for requesting the start of use of any of the option functions that can be added to the vehicle 2 to the management server 4 according to an instruction from the user U input via the second touch panel 47 on which the function list is displayed.

[0060] The display control unit 44 displays the function list and various other information received from the management server 4 on the second touch panel 47.

[0061] The notification output unit 45 displays and / or outputs various messages including a message of a preparation unavailable notification received from the management server 4 on the second touch panel 47 and / or from the second speaker 48 according to an instruction from the management server 4.

[0062] FIG. 8 is an example of a function list displayed on the second touch panel 47 by the display control unit 44. This function list is displayed on the second touch panel 47 as one of the screens when the third program 42, which is an application program, is executed. In the illustrated example, the function list is displayed in the list display area 50. The left column of this function list is a list of optional functions of the vehicle 2 (corresponding to the fifth column of the table in FIG. 7), and the right column shows information on whether execution is permitted for each optional function (corresponding to the ninth column of the table in FIG. 7). In this right column, for the optional functions for which the "Execution Permitted / Not" column in the ninth column of FIG. 7 is set to "Permitted" (i.e., the optional functions that the user U has already started using), "In Use" is displayed, and for the optional functions for which the "Execution Permitted / Not" column in FIG. 7 is "Prohibited", a check box is displayed.

[0063] Seven optional functions from function A to function G are displayed in the list display area 50 shown in FIG. 8. The user U can cause the terminal device 6 to display other optional functions by performing a swipe operation or a flick operation in the list display area 50.

[0064] When the user U touches the check box of the desired optional function that the user wants to newly start using, checks it, and presses the selection button 52, the request unit 43 transmits a function start request for the corresponding optional function to the management server 4. As described above, when the notification unit 37 of the management server 4 determines that the optional function requested by the function start request is not ready for execution, it transmits a not-ready notification to the terminal device 6. The notification output unit 45 of the terminal device 6 displays the not-ready notification received from the management server 4 in the message area 51 of the second touch panel 47. In addition to this, the notification output unit 45 may output the not-ready notification as an audio message from the second speaker 48.

[0065] The user U can end this application by pressing the end button 53.

[0066] [Processing in the Function Management System] Next, the processing procedure of the function management method performed by the function management system 1 will be described. The function management system 1 executes the function management method through a preparation determination process for determining whether the execution of an optional function is ready and a function start process for performing processing for starting the use of the optional function in response to a request from the user U.

[0067] [6.1 Preparation Determination Process] FIG. 5 is a flowchart showing the procedure of the preparation determination process. The preparation determination process is executed by the first processor 20 of the vehicle management device 3, which is a computer of the function management system 1, and the second processor 30 of the management server 4. The process shown in FIG. 5 is repeatedly executed.

[0068] In the preparation determination process, first, the information collection unit 23 of the vehicle management device 3 determines whether the vehicle power switch 18 of the vehicle 2 has been turned on (that is, whether it has been switched from the off state to the on state) (S100). When the vehicle power switch 18 is turned on (S100, YES), the information collection unit 23 collects failure information from each of the ECUs 11 (S102). The information collection unit 23 transmits the collected failure information to the management server 4 (S104).

[0069] Next, the determination unit 36 of the management server 4 that has received the failure information determines whether the execution of each optional function of the vehicle 2 is ready based on the failure information received from the vehicle management device 3 (S106). Subsequently, based on the determination result, the determination unit 36 updates the management information 33 stored in the second memory 31 (S108) and ends the preparation determination process.

[0070] On the other hand, in step S100, when the vehicle power switch is not turned on (S100, NO), the information collection unit 23 determines whether it has received failure information indicating the occurrence of a failure from any of the ECUs 11 (S110). As described above, each ECU 11 performs a failure diagnosis, for example, periodically when the vehicle power switch 18 is in the on state, and transmits the failure information to the vehicle management device 3.

[0071] When the information collection unit 23 receives failure information indicating the occurrence of a failure from any of the ECUs 11 (S110, YES), it transfers the process to step S104 and transmits the received failure information to the management server 4. On the other hand, when it does not receive failure information indicating the occurrence of a failure (S110, NO), the information collection unit 23 ends the preparation determination process.

[0072] Here, steps S102 and S104 shown in FIG. 5 correspond to the information collection steps in the present disclosure. Also, step S106 shown in FIG. 5 corresponds to the determination step in the present disclosure.

[0073] [6.2 Function start process] FIG. 6 is a flowchart showing the procedure of the function start process. The function start process is executed by the first processor 20 of the vehicle management device 3 which is a computer of the function management system 1, the second processor 30 of the management server 4, and the third processor 40 of the terminal device 6. The process shown in FIG. 6 is repeatedly executed.

[0074] In the function start process, first, the reception unit 35 of the management server 4 determines whether it has received a legitimate function list request from the terminal device 6 (S200). When it does not receive a legitimate function list request (S200, NO), the reception unit 35 returns to step S200 and repeats the process, waiting to receive a legitimate function list request.

[0075] On the other hand, when it receives a legitimate function list request (S200, YES), the notification unit 37 of the management server 4 transmits a function list to the terminal device 6 which is the transmission source of the function list request. The display control unit 44 of the terminal device 6 that has received the function list displays the function list on the second touch panel 47 (S202).

[0076] Next, the request unit 43 of the terminal device 6 determines whether or not an end operation has been performed by the user U (S204). The end operation of the user U may be, for example, pressing an end button 53 displayed together with the function list on the second touch panel 47. When the end operation is performed (S204, YES), the request unit 43 ends the function start process.

[0077] On the other hand, when the end operation is not performed (S204, NO), the request unit 43 determines whether or not a start request for any of the optional functions has been input from the user U (S206). As described above, the user U can input a start request for the optional function by selecting the optional function to be used from the function list displayed on the second touch panel 47 using a check box and pressing the selection button 52.

[0078] When the start request for the optional function is not input (S206, NO), the request unit 43 returns the process to step S204 and repeats steps S204 and S206, waiting for the end operation to be performed or for a start request for any of the optional functions to be input.

[0079] On the other hand, when a start request for any of the optional functions is input (S206, YES), the request unit 43 transmits a function start request for that optional function to the management server 4. The notification unit 37 and the permission unit 38 of the management server 4 that have received the function start request determine whether or not it is possible to prepare for the execution of the optional function requested by the function start request based on the management information 33 stored in the second memory 31 (S208).

[0080] When the preparation for executing the requested optional function becomes possible (S208, YES), the permission unit 38 updates the information on whether to permit the execution of the requested optional function in the management information 33 to "permit" on the condition that the charging process for the user U has been performed normally. Further, the permission unit 38 transmits an execution preparation instruction for the requested optional function to the vehicle 2. Then, when the installation management unit 24 of the vehicle management device 3 of the vehicle 2 that has received the execution preparation instruction determines that the software program necessary for executing the optional function is not installed in the related ECU 11, it downloads the necessary software program from the management server 4 and stores it in the second memory 31 (S210).

[0081] Next, the installation management unit 24 determines whether the vehicle power switch 18 of the vehicle 2 is in the off state (S212). When the vehicle power switch 18 is not in the off state (S212, NO), the installation management unit 24 returns to step S212 and repeats the process, waiting for the vehicle power switch 18 to be turned off. On the other hand, when the vehicle power switch 18 is in the off state (S212, YES), the installation management unit 24 instructs the ECU 11 related to the optional function instructed by the execution preparation instruction to perform the execution preparation for the optional function (that is, make it in an executable state) (S214).

[0082] At that time, when the software program necessary for executing the requested optional function is not installed in the related ECU 11, the installation management unit 24 installs the software program downloaded in step S210 in the related ECU 11. After preparing for the execution of the requested optional function, the installation management unit 24 ends the function start process.

[0083] On the other hand, in step S208, when it is determined that the preparation for executing the requested optional function is not possible (S208, NO), the notification unit 37 instructs the terminal device 6 to output a notification of unpreparedness for the requested optional function (S216), and the process proceeds to step S204.

[0084] [7. Other Embodiments] In the above-described embodiment, when the notification unit 37 of the management server 4 receives a function list request from the terminal device 6, it transmits a function list including all optional functions to the terminal device 6, and presents all optional functions to the user U via the terminal device 6. Instead, the notification unit 37 of the management server 4 may present the optional functions determined to be ready for execution in the function list and not present the optional functions determined to be not ready for execution. Specifically, for example, in response to receiving a function list request from the terminal device 6, the notification unit 37 refers to the management information 33, creates a function list including only the optional functions determined to be ready for execution, and transmits the created function list to the terminal device 6.

[0085] In the above-described embodiment, the failure information collected by the information collection unit 23 of the vehicle management device 3 includes information about the failures of the ECU 11 and the device 12, but the failure information may include at least information about the failure of the ECU 11 or the device 12.

[0086] In the above-described embodiment, the software program necessary for realizing the optional function is downloaded from the management server 4 to the vehicle management device 3, but it may be downloaded from another server device such as a program distribution server (not shown) connected to the communication network 5.

[0087] In the above-described embodiment, when the option function for which the function start request is transmitted by the terminal device 6 is not ready for execution, it is assumed that no charging process or usage permission is performed for that option function. However, with the consent of the user U via the terminal device 6, charging process and usage permission may be performed for the option function. In this case, the user U can immediately use the option function after performing necessary repairs on the vehicle 2 and the like.

[0088] In the above-described embodiment, the charging process performed by the permission unit 38 of the management server 4 is assumed to be the monthly usage fee of the option function, but it may be the purchase fee of the option function.

[0089] In the above-described embodiment, the user U is assumed to request the start of using the option function by the terminal device 6. In addition to this, the user U may request the terminal device 6 to stop using the option function that has already started being used. The permission unit 38 of the management server 4 that has received the stop usage request stops charging for the option function, and in the management information 33, after updating the execution permission / denial information (the rightmost column of the table in FIG. 7) for the option function to "prohibited", it can instruct the vehicle management device 3 to prohibit the execution of the option function. The installation management unit 24 of the vehicle management device 3 prohibits the execution of the option function for the related ECU 11 according to the above instruction.

[0090] In the above-described embodiment, the terminal device 6 is assumed to be a terminal device such as a smartphone owned by the user U, but the terminal device 6 may be the IVI unit 14 provided in the vehicle 2. In this case, when the user U gets in the vehicle 2, the user U can browse the function list via the first touch panel 15 connected to the IVI unit 14 and select the option function for which the user wants to start using.

[0091] The management server 4 may have other functional elements and management information 33 other than the distribution unit 39 provided in the vehicle management device 3. In this case, for example, the terminal device 6 and the vehicle management device 3 can communicate via the communication device of the IVI unit 14 without going through the communication network 5 to execute the function management method.

[0092] Note that the present invention is not limited to the configuration of the above-described embodiment, and can be implemented in various aspects without departing from the gist thereof.

[0093] [8. Configuration Supported by the Above Embodiment] The above-described embodiment supports the following configuration.

[0094] (Configuration 1) A function management system for managing the use of optional functions in a vehicle, comprising an information collection unit that collects failure information including information about failures of electronic control devices mounted on the vehicle and / or information about failures of devices controlled by the electronic control devices, and a determination unit that determines, for each of the optional functions, whether execution preparation for use start is possible. The determination unit determines, based on the failure information, that for each of the optional functions, when a failure is found in the electronic control device or the device necessary for the execution of the optional function, the execution preparation of the optional function is not possible. According to the function management system of Configuration 1, an optional function that cannot be prepared for execution due to a failure of an electronic control device or a device can be detected prior to a user's request to use the optional function. Therefore, at the time of the use request, it is possible to quickly present to the user whether the execution preparation of the requested optional function is possible, and to facilitate the use of the optional function.

[0095] (Configuration 2) A reception unit that receives a request to start using the option function from a terminal device, and a notification unit that notifies a user via the terminal device, wherein when the reception unit receives a request to start using any of the option functions, and when it is determined that the option function is not ready for execution, the notification unit outputs a notification to the user via the terminal device that the option function cannot be used, the function management system according to Configuration 1. According to the function management system of Configuration 2, when a user requests to start using an option function, if the option function cannot be prepared for execution due to equipment failure or the like, the user is notified of this, so the user can take measures such as considering other alternative option functions, and the smooth use of the option function can be achieved.

[0096] (Configuration 3) A notification unit that presents a list of the option functions to the user via the terminal device, wherein the notification unit presents the option functions determined to be ready for execution in the list and does not present the option functions determined not to be ready for execution, the function management system according to Configuration 1. According to the function management system of Configuration 3, since the option functions that are not ready for execution are not presented to the user, the user can select a desired option function from the presented option functions that are ready for execution, and the smooth use of the option function can be achieved.

[0097] (Configuration 4) The electronic control device performs self-diagnosis of an operation failure of the electronic control device and / or failure diagnosis of the equipment controlled by the electronic control device to generate the failure information, and the information collection unit collects the failure information from the electronic control device when the power switch of the vehicle is switched on and transmits it to the determination unit, the function management system according to any one of Configurations 1 to 3. According to the function management system of Configuration 4, since the failure information collected when the vehicle power switch is switched on is used, even during a period when the communication state between the information collection unit and the vehicle can change, such as when the vehicle is running, the latest failure information can be used to appropriately determine whether the execution preparation of the optional function is possible.

[0098] (Configuration 5) The information collection unit further transmits the failure information received from the electronic control unit that has detected a failure of the electronic control unit and / or the device during the period when the vehicle power switch is on to the determination unit. The function management system according to Configuration 4. According to the function management system of Configuration 5, it is possible to determine whether the execution preparation of the optional function is possible by reflecting the most recently occurred failure situation.

[0099] (Configuration 6) An installation management unit that manages the installation of the software program necessary for the execution of the optional function to the electronic control unit is provided. The installation management unit installs the software program of the optional function for which execution preparation is determined to be possible, and does not install the software program of the optional function for which execution preparation is determined to be impossible. The function management system according to any one of Configurations 1 to 5. According to the function management system of Configuration 6, it is possible to avoid installing unnecessary software programs and reduce the processing load.

[0100] (Configuration 7) The installation management unit installs the software program necessary for the execution of the optional function in the electronic control unit during the period when the vehicle power switch is off. The function management system according to Configuration 6. According to the function management system of Configuration 7, for example, it is possible to prevent a situation where the installation process of the software program for the optional function is performed during vehicle running and the safety of vehicle running is reduced for the electronic control unit necessary for vehicle running.

[0101] (Configuration 8) A vehicle management device including the information collection unit mounted on the vehicle, and a management server which is a server device including the determination unit provided outside the vehicle, the functional management system according to any one of Configurations 1 to 7. According to the functional management system of Configuration 8, since the determination of the availability of the execution preparation for the optional function is processed in the server device outside the vehicle, the processing in the vehicle management device which is an in-vehicle device can be reduced.

[0102] (Configuration 9) A functional management method performed by a computer of a functional management system for managing the use of an optional function in a vehicle, the method including an information collection step of collecting failure information including information about a failure of an electronic control unit mounted on the vehicle and / or information about a failure of a device controlled by the electronic control unit, and a determination step of determining, for each of the optional functions, whether execution preparation for use start is possible, wherein in the determination step, based on the failure information, for each of the optional functions, when a failure is found in the electronic control unit or the device necessary for the execution of the optional function, it is determined that the execution preparation of the optional function is not available. According to the functional management method of Configuration 9, since an optional function that cannot be prepared for execution due to a failure of an electronic control unit or a device can be detected prior to a user's request for using the optional function, at the time of the use request, it is possible to promptly present to the user whether the execution preparation of the requested optional function is available or not, and to facilitate the use of the optional function.

Description of Reference Numerals

[0103] 1... Function management system, 2... Vehicle, 3... Vehicle management device, 4... Management server, 5... Communication network, 6... Terminal device, 10... In-vehicle network bus, 11... ECU, 11a... aECU, 11b... bECU, 11c... cECU, 11d... dECU, 12... Device, 12a... aDevice, 12b... bDevice, 12c... cDevice, 12d... dDevice, 13... TCU, 14... IVI unit, 15... First touch panel, 16... First speaker, 17... First communication device, 18... Vehicle power switch, 20... First processor, 21... First memory, 22... First program, 23... Information collection unit, 24... Installation management unit, 30... Second processor, 31... Second memory, 32... Second communication device, 33... Management information, 34... Second program, 35... Reception unit, 36... Judgment unit, 37... Notification unit, 38... Permission unit, 39... Distribution unit, 40... Third processor, 41... Third memory, 42... Third program, 43... Request unit, 44... Display control unit, 45... Notification output unit, 46... Third communication device, 47... Second touch panel, 48... Second speaker, 50... List display area, 51... Message area, 52... Selection button, 53... End button.

Claims

1. A function management system for managing the use of optional functions in a vehicle, an information collection unit that collects failure information including information about a failure of an electronic control unit mounted on the vehicle and / or information about a failure of a device controlled by the electronic control unit, a determination unit that determines, for each of the optional functions, whether execution preparation for use start is possible, a notification unit that presents a list of the optional functions to a user via a terminal device, comprising: Based on the failure information, the determination unit, for each of the optional functions, determines that execution preparation of the optional function is possible when no failure is found in the electronic control unit and the device necessary for execution of the optional function, determines that execution preparation of the optional function is not possible when a failure is found in the electronic control unit or the device necessary for execution of the optional function, The notification unit presents, in the list, the optional functions determined to be ready for execution. Function management system.

2. The notification unit presents, in the list, the optional functions determined to be not ready for execution together with the optional functions determined to be ready for execution. The function management system according to claim 1.

3. having a reception unit that receives a request for starting use of the optional function from a terminal device, When the reception unit receives a request for starting use of any of the optional functions, the notification unit outputs, via the terminal device, a notification indicating that the optional function cannot be used when the optional function is determined to be not ready for execution. The function management system according to claim 2.

4. The notification unit does not present the optional functions determined to be not ready for execution in the list. The function management system according to claim 1.

5. The electronic control unit performs self-diagnosis of an operation failure of the electronic control unit and / or failure diagnosis of the device controlled by the electronic control unit to generate the failure information, The information collection unit collects the failure information from the electronic control unit when the power switch of the vehicle is switched on and transmits it to the determination unit. The function management system according to claim 1.

6. The information collection unit further transmits the failure information received from the electronic control unit that has detected a failure of the electronic control unit and / or the device during the period when the power switch of the vehicle is turned on, to the determination unit. The function management system according to claim 5.

7. It includes an installation management unit that manages the installation of software programs necessary for executing the optional function in the electronic control unit. The installation management unit installs the software program of the optional function for which execution preparation has been determined to be possible. The function management system according to claim 1.

8. It includes an installation management unit that manages the installation of software programs necessary for executing the optional function in the electronic control unit. The installation management unit does not install the software program of the optional function for which execution preparation has been determined to be impossible. The function management system according to claim 1.

9. The installation management unit installs the software program necessary for executing the optional function in the electronic control unit during the period when the power switch of the vehicle is turned off. The function management system according to claim 7.

10. A vehicle management device including the information collection unit mounted on the vehicle, A management server which is a server device including the determination unit provided outside the vehicle. Including The function management system according to any one of claims 1 to 9.

11. A function management method performed by a computer of a function management system that manages the use of optional functions in a vehicle, An information collection step of collecting failure information including information about a failure of an electronic control unit mounted on the vehicle and / or information about a failure of a device controlled by the electronic control unit, A determination step of determining, for each of the optional functions, whether execution preparation for starting use is possible, A notification step of presenting a list of the optional functions to the user via a terminal device. Having In the determination step, based on the failure information, for each of the optional functions, when no failure is found in the electronic control device and the equipment necessary for the execution of the optional function, it is determined that the execution preparation of the optional function is possible, and when a failure is found in the electronic control device or the equipment necessary for the execution of the optional function, it is determined that the execution preparation of the optional function is not possible. In the notification step, in the list, the optional functions determined to be ready for execution are presented. Function management method.

Images