Function management system and function management method

The function management system addresses the challenge of managing optional vehicle functions by collecting failure information, determining readiness, and notifying users, enhancing convenience and efficiency in function execution.

JP2024161178AActive Publication Date: 2024-11-15HONDA MOTOR CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2024147578
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-08-29
Publication Date
2024-11-15
Estimated Expiration
2043-01-26

AI Technical Summary

Technical Problem

Existing systems fail to effectively manage and prepare for the execution of optional vehicle functions due to device and equipment failures, leading to inconvenience for users.

Method used

A function management system and method that includes an information collection unit to gather failure information from electronic control devices, a determination unit to assess readiness for optional function execution, and a notification unit to inform users of preparation status, ensuring smooth execution of functions.

Benefits of technology

Facilitates the use of optional vehicle functions by promptly informing users of preparation readiness, reducing unnecessary software installations, and optimizing processing loads.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024161178000001_ABST
    Figure 2024161178000001_ABST
Patent Text Reader

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
Need to check novelty before this filing date? Find Prior Art

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 technology]

[0002] In recent years, efforts to provide access to sustainable transport systems that take into consideration vulnerable transport participants have been gaining momentum. To achieve this, we are focusing on research and development into driver assistance technologies to further improve road safety and convenience.

[0003] Moreover, in recent years, when a vehicle is sold, in addition to devices for realizing standard functions, devices and equipment that can realize optional functions are installed in the vehicle, and after the sale of the vehicle, it is possible to execute optional functions upon request from the user.

[0004] Patent Document 1 describes an information processing device that changes the usage settings of options installed in a vehicle depending on the purpose of use. In this information processing device, when the purpose of use of the vehicle is business, the usage of all options is permitted, and when the purpose of use of the vehicle is personal, the usage of at least one option is restricted. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2021-189491 A Summary of the Invention [Problem to be solved by the invention]

[0006] Incidentally, in driving assistance technology, in order to improve the convenience of vehicle users, it is necessary to appropriately manage failures of devices and equipment related to optional vehicle functions and smoothly prepare to execute these optional functions.

[0007] In order to solve the above problems, the present application aims to facilitate the use of optional functions by quickly notifying a vehicle user of whether or not the optional function is ready to be executed when the vehicle user requests the use of the optional function, thereby contributing to the development of a sustainable transportation system. [Means for solving the problem]

[0008] One aspect of the present invention is a function management system that manages the use of optional functions in a vehicle, and includes an information collection unit that collects failure information including information about failures of an electronic control unit installed in the vehicle and / or information about failures of equipment controlled by the electronic control unit, and a judgment unit that judges whether each of the optional functions is ready to be executed so that it can be used. Another aspect of the present invention is a function management method performed by a computer of a function management system that manages the use of optional functions in a vehicle, the function management method having an information collection step of collecting failure information including information about a failure of an electronic control device installed in the vehicle and / or information about a failure of equipment controlled by the electronic control device, and a judgment step of judging whether each of the optional functions is ready to be executed so that it can be started to be used. Effect of the Invention

[0009] According to the present invention, when a vehicle user requests the use of an optional function, whether or not the optional function is ready to be executed can be quickly presented to the user, thereby facilitating the use of the optional function. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing a configuration of a function management system according to an embodiment of the present invention; [Diagram 2] 1 is a diagram showing a configuration of a vehicle management device constituting a function management system; [Diagram 3] FIG. 2 is a diagram illustrating a configuration of a management server that constitutes the function management system. [Figure 4] FIG. 2 is a diagram showing the configuration of a terminal device constituting the function management system. [Diagram 5] FIG. 11 is a flowchart showing the procedure of a preparation determination process executed by the function management system. [Figure 6] 11 is a flowchart showing the procedure of a function start process executed by the function management system. [Figure 7] FIG. 4 is a diagram illustrating an example of management information. [Figure 8] 13 is a display example of a function list on a terminal device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. [1. Configuration of the application management system] 1 is a diagram showing the configuration of a function management system 1 according to one 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 carried by a user U who uses the vehicle 2. The vehicle management device 3, the management server 4, and the terminal device 6 are connected to each other so as to be able to communicate with each other via a communication network 5 such as the Internet.

[0012] The vehicle 2 is, for example, an electric vehicle or a vehicle driven by an 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 this embodiment, the terminal device 6 is, for example, a smartphone carried by the user U.

[0013] The user U operates the terminal device 6 to select an optional function of the vehicle 2 and transmits a request to start using the selected optional function to the management server 4. In response to receiving the request to start using the selected optional function, the management server 4 instructs the vehicle management device 3 of the vehicle 2 to prepare for execution of the optional function specified by the request.

[0014] [2. Overview of Application Management System Operation] Function management system 1 executes a readiness determination process and a function start process. The preparation determination process is a process for determining whether or not each optional function is ready to be executed in order to start using it. The function start process is a process for preparing an optional function designated by a request from a user U so that the optional function can be executed in the vehicle 2. Here, preparation for execution of an optional function may include installing a software program required for executing the optional function in an associated electronic control device, and / or giving permission to execute the optional function to the associated electronic control device (or setting permission to execute the optional function in the associated electronic control device).

[0015] In the preparation determination process, the vehicle management device 3 collects failure information including information on failures of electronic control devices equipped in the vehicle 2 and information on failures of 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 or not each of the optional functions of the vehicle 2 is ready to be executed so that the user U can start using it. For example, when, based on the failure information, a failure is found in an electronic control device or device required to execute each optional function, the management server 4 determines that the optional function is not ready to be executed. The management server 4 stores the determination result of whether or not each optional function is ready to be executed as management information.

[0016] As a result, the function management system 1 can detect optional functions that cannot be prepared for execution due to a malfunction of the electronic control device or equipment prior to a request from user U to use the optional function, and can quickly inform the user whether or not the optional function is ready for execution, facilitating the use of the optional function.

[0017] In the function start process, the management server 4 displays a list of optional 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 optional function from this list and request to start using it. In response to receiving a request to start using any optional function from the terminal device 6, the management server 4 refers to the determination result of whether or not the optional function is ready for execution stored in the above-mentioned preparation determination process, and determines whether or not the optional function requested to start using can be prepared for execution. If the optional function is not ready for execution, the management server 4 notifies the user U via the terminal device 6 that the optional function cannot be used.

[0018] On the other hand, if the optional function requested to be started is one that can be prepared for execution, the management server 4 performs a billing process for the usage fee of the optional function, and then instructs the vehicle management device 3 to prepare for execution of the optional function. The usage fee may be, for example, a monthly usage fee for each optional function. The vehicle management device 3 that has received the preparation for execution instruction installs a software program required to execute the optional function requested to be started in the electronic control device associated with that optional function.

[0019] In particular, in this embodiment, the vehicle management device 3 installs software programs for optional functions that are determined to be ready for execution in accordance with the execution preparation instructions for the above-mentioned optional functions, and does not install software programs for optional functions that are determined to be not ready for execution. This makes it possible to avoid the installation of unnecessary software programs and reduce the processing load on the vehicle management device 3 and the processing load on the electronic control device.

[0020] The configurations of the vehicle management device 3, management server 4, and terminal device 6 will be described below in order. [3. Configuration of vehicle management device] First, the vehicle management device 3 provided in the vehicle 2 will be described. 2 is a diagram showing a 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 control the a device 12a, the b device 12b, the c device 12c, and the d device 12d, respectively. Hereinafter, the aECU 11a, bECU 11b, cECU 11c, and dECU 11d are collectively referred to as ECUs 11, and the a device 12a, the b device 12b, the c device 12c, and the d device 12d are collectively referred to as devices 12. Each ECU 11 can execute various optional functions of the vehicle 2, either alone or in cooperation with other ECUs 11.

[0022] While the vehicle power switch 18 is on and power is being supplied, the ECUs 11 each perform self-diagnosis for operational malfunctions of themselves and malfunction diagnosis for the devices 12 that they control, for example, periodically at a predetermined timing, and generate malfunction information indicating the diagnosis results. Each ECU 11 transmits the generated malfunction information to the vehicle management device 3. Here, the malfunction may include software anomalies and / or hardware malfunctions.

[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 sounds from the first speaker 16 in response to instructions 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 for communicating with the terminal device 6 brought into the cabin 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 configured, for example, by a volatile and / or non-volatile semiconductor memory and / or a hard disk device.

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

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

[0027] The information collecting unit 23 collects malfunction information from the ECU 11 and transmits it to the management server 4. Specifically, when the vehicle power switch 18 is switched on, the information collecting unit 23 collects malfunction information from the ECU 11 and transmits it to the management server 4. In addition, when the information collecting unit 23 receives malfunction information from the ECU 11 that has discovered a malfunction while the vehicle power switch 18 is on, the information collecting unit 23 may transmit the received malfunction information to the management server 4.

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

[0029] Specifically, when the installation management unit 24 receives an execution preparation instruction from the management server 4, the installation management unit 24 downloads from the management server 4 a software program required for executing an optional function that has been determined to be ready for execution and whose execution has been permitted, and installs the software program in the ECU 11 related to the optional function, in accordance with the received execution preparation instruction. After completing the installation, the installation management unit 24 permits the relevant ECU 11 to execute the optional function.

[0030] When a software program required for executing an optional function that is not permitted to be executed in the received execution preparation instruction is already installed in the ECU 11 related to the optional function, the installation management unit 24 prohibits the execution of the optional function in the ECU 11. For example, when the user U uses an optional function and then ends the use of the optional function, the vehicle management device 3 may be notified of the optional function that is not permitted to be executed in the execution preparation instruction.

[0031] In addition, when a software program required for executing an optional function that is determined to be ready for execution and whose execution has been permitted is already installed in an ECU 11, the installation management unit 24 only permits the ECU 11 to execute the optional function, and does not install the software program redundantly. For example, when the user U uses one optional function and then ends the use of the optional function, the software program of the optional function may remain installed in the ECU 11.

[0032] In this embodiment, the installation management unit 24 installs the software program in the ECU 11 while the vehicle power switch 18 is off. This can prevent, for example, a situation in which a software program for an optional function is installed in any of the ECUs 11 that performs processing necessary for the vehicle 2 to run while the vehicle 2 is running, thereby reducing the safety of the vehicle running.

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

[0034] [4. Configuring the 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 that enables 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 configured, for example, by a volatile and / or non-volatile semiconductor memory and / or a hard disk device, etc. 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, billing information for receiving payment of fees for optional functions from the user U (for example, bank account information and credit card information), and information about the optional functions of the vehicle 2.

[0036] 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 a table format. From the left in the illustrated table, the first column shows a user ID, the second column shows a vehicle ID, the third column shows access information, and the fourth column shows billing information.

[0037] Columns 5 to 9 of the illustrated table are information about optional functions of the vehicle 2. Column 5 is the name of the optional function, and columns 6 and 7 are lists of the ECU 11 (associated ECU) and device 12 (associated device) involved in the operation of each optional function, respectively. Column 8 shows information on whether or not each optional function is ready to be executed (information on whether or not execution is ready), and column 9 shows information on whether or not execution of each optional function is permitted (information on whether or not execution is permitted).

[0038] For example, when there are multiple vehicles 2 that are shared cars and multiple users U can use each vehicle 2, the management information 33 may hold, for example, the information in columns 1 to 9 for each combination of user U and vehicle 2.

[0039] Here, the user ID, vehicle ID, access information, and billing information may be acquired in advance from the user U via the terminal device 6 and stored in the management information 33 according to, for example, conventional techniques.

[0040] In addition, the names of optional functions in the fifth column, the list of related ECUs in the sixth column, and the list of related devices in the seventh column are set in advance according to the specifications of the vehicle 2. Information on whether or not execution is ready in the eighth column is stored or updated by a determination unit 36 ​​of the management server 4, which will be described later. Information on whether or not execution is permitted in the ninth column is all "prohibited" by default, and is updated by a permission unit 38, which will be described later.

[0041] 3, the second processor 30 is, for example, a computer including a CPU, etc. The second processor 30 may have a configuration including a ROM in which a program is written, a RAM for temporarily storing data, etc. The second processor 30 includes, as functional elements or functional units, a receiving unit 35, a determining unit 36, a notifying unit 37, a permitting unit 38, and a distributing unit 39.

[0042] These functional elements of the second processor 30 are realized, for example, by the second processor 30, which is a computer, executing a second program 34 stored in the second memory 31. The second program 34 can be stored in any computer-readable storage medium. Alternatively, all or part of the above-mentioned functional elements of the second processor 30 can 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, which will be described later. When the reception unit 35 receives a function list request and a function start request, the reception unit 35 refers to the management information 33 in the second memory 31, 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 valid, the receiving unit 35 sends the received function list request to the determination unit 36 ​​and the notification unit 37. When the received function start request is valid, the receiving unit 35 sends the received function start request to the notification unit 37 and the permission unit 38.

[0045] The determination unit 36 ​​determines whether or not each of the optional functions of the vehicle 2 can be prepared for execution to start using the optional functions. In this embodiment, particularly, when no malfunction is found in the ECU 11 and the device 12 required for executing each optional function based on malfunction information transmitted from the information collection unit 23 of the vehicle management device 3 provided in the vehicle 2, the determination unit 36 ​​determines that the optional function can be prepared for execution. Furthermore, when a malfunction is found in the necessary ECU 11 or device 12, the determination unit 36 ​​determines that the optional function cannot be prepared for execution.

[0046] Specifically, the determination unit 36 ​​determines whether or not each of the optional functions is ready for execution 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. This allows the determination unit 36 ​​to determine whether or not the optional functions are ready for execution 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 traveling.

[0047] Furthermore, when the determination unit 36 ​​receives from the vehicle management device 3 failure information from the ECU 11 that has discovered a failure while the vehicle power switch 18 of the vehicle 2 is on, the determination unit 36 ​​determines whether or not each optional function is ready for execution based on the received failure information as well. This allows the determination unit 36 ​​to determine whether or not an optional function is ready for execution, reflecting the most recent failure state that has occurred 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 as to whether or not each of the optional functions is ready for execution.

[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, it transmits a function list, which is a list of optional functions of the vehicle 2, to the terminal device 6 based on the management information 33 in the second memory 31. The terminal device 6 displays the received function list. The user U can select an optional function that the user wishes to start using 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 and the optional function requested by the function start request is not judged to be ready for execution, the notification unit 37 notifies the user U via the terminal device 6 that the optional function cannot be used. Specifically, when the notification unit 37 receives a function start request, the notification unit 37 refers to the management information 33 in the second memory 31 and acquires the judgment result of whether the optional function requested by the function start request is ready for execution. Then, when the notification unit 37 does not judge that the optional function is ready for execution, the notification unit 37 instructs the terminal device 6 to issue a preparation not possible notification that the optional function cannot be used. The preparation not possible notification may be, for example, a text message and / or a voice message such as "Currently, the function is not available. Please consult your nearest dealer."

[0051] When the permission unit 38 receives a function start request from the terminal device 6 via the reception unit 35, and if the optional function requested by the function start request is ready for execution, the permission unit 38 performs a billing process for the user U for the fee for using the optional function. The fee to be billed may be, for example, a monthly usage fee for the optional function. When the billing process for 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 of the second memory 31 to "permitted" and transmits an execution preparation instruction for the 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 a software program required by the vehicle management device 3 to the vehicle management device 3. Note that the software program may be stored in, for example, the second memory 31 (not shown in FIG. 3).

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

[0054] 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, 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 performs communication 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, for example, by a volatile and / or non-volatile semiconductor memory or the like.

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

[0057] These functional elements of the third processor 40 are realized, for example, by the third processor 40 being a computer executing 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) or the like connected to the communication network 5, or can be stored in advance in any computer-readable storage medium and then read out from the storage medium for use. Alternatively, all or part of the above-mentioned functional elements of the third processor 40 can be configured by hardware each including one or more electronic circuit components.

[0058] In response to an instruction from user U inputted via the second touch panel 47, the request unit 43 transmits a function list request to the management server 4 to request a function list including a list of optional functions of the vehicle 2. The function list request may include the user ID of the user U and the vehicle ID of the vehicle 2. As described above, in response to receiving the function list request, the management server 4 transmits the function list to the terminal device 6. 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 sends a function start request to the management server 4, requesting the start of use of any of the optional functions that can be added to the vehicle 2, in response to instructions from the user U inputted via the second touch panel 47 on which the function list is displayed.

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

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

[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 a 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 each optional function is permitted to be executed (corresponding to the ninth column of the table in FIG. 7). In this right column, "In use" is displayed for optional functions for which the "Execution permission" column in the ninth column of FIG. 7 is set to "Permitted" (i.e., optional functions that the user U has already started using), and a check box is displayed for optional functions for which the "Execution permission" column in FIG. 7 is set to "Prohibited".

[0063] 8 displays seven optional functions from function A to function G. 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 and checks the check box of a desired optional function that the user U wants to newly start using, 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, in response to this, the notification unit 37 of the management server 4 transmits a preparation impossible notification to the terminal device 6 when the optional function requested by the function start request is not determined to be ready for execution. The notification output unit 45 of the terminal device 6 displays the preparation impossible 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 preparation impossible notification as a voice message from the second speaker 48.

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

[0066] [6. Processing in the Application Management System] Next, we will explain the procedure of the function management method performed by the function management system 1. The function management system 1 executes the function management method by a preparation determination process that determines whether or not an optional function is ready to be executed, and a function start process that performs processing to start using the optional function in response to a request from the user U.

[0067] [6.1 Readiness Judgment Processing] Fig. 5 is a flow diagram 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 executed repeatedly.

[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 (i.e., whether it has been switched from an off state to an on state) (S100). Then, when the vehicle power switch 18 has been turned on (S100, YES), the information collection unit 23 collects fault information from each of the ECUs 11 (S102). The information collection unit 23 transmits the collected fault information to the management server 4 (S104).

[0069] Next, the determination unit 36 ​​of the management server 4 that has received the malfunction information determines whether or not each optional function of the vehicle 2 is ready to be executed based on the malfunction information received from the vehicle management device 3 (S106). Next, the determination unit 36 ​​updates the management information 33 stored in the second memory 31 based on the determination result (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 collecting unit 23 judges whether or not fault information indicating the occurrence of a fault has been received from any of the ECUs 11 (S110). As described above, when the vehicle power switch 18 is in the on state, each ECU 11 performs a fault diagnosis, for example, periodically, and transmits the fault information to the vehicle management device 3.

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

[0072] Here, steps S102 and S104 shown in Fig. 5 correspond to the information gathering step in this disclosure, and step S106 shown in Fig. 5 corresponds to the determination step in this disclosure.

[0073] [6.2 Function Start Processing] Fig. 6 is a flow diagram 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 executed repeatedly.

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

[0075] On the other hand, when a valid function list request is received (S200, YES), notification unit 37 of management server 4 transmits the function list to terminal device 6 which is the sender of the function list request. Having received the function list, display control unit 44 of terminal device 6 displays the function list on 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 by the user U may be, for example, pressing the end button 53 displayed together with the function list on the second touch panel 47. Then, when the end operation has been 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 judges whether or not a request to start any optional function has been input from the user U (S206). As described above, the user U can input a request to start an optional function by selecting the optional function that the user U wishes to start using by checking the check box from the function list displayed on the second touch panel 47 and pressing the selection button 52.

[0078] Then, when a request to start an 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 an end operation to be performed or for a request to start 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 received the function start request determine, based on the management information 33 stored in the second memory 31, whether or not the optional function requested by the function start request can be prepared for execution (S208).

[0080] Then, when the requested optional function can be prepared for execution (S208, YES), the permission unit 38 updates the information on whether or not the requested optional function can be executed in the management information 33 to "permitted", on the condition that the billing process for the user U has been normally performed. The permission unit 38 also transmits an execution preparation instruction for the requested optional function to the vehicle 2. Then, when a software program required for executing the optional function is not installed in the associated ECU 11, the installation management unit 24 of the vehicle management device 3 of the vehicle 2 that has received the execution preparation instruction downloads the required 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 an OFF state (S212). If the vehicle power switch 18 is not in an OFF state (S212, NO), the installation management unit 24 returns to step S212 to repeat the process and waits for the vehicle power switch 18 to be in an OFF state. On the other hand, if the vehicle power switch 18 is in an OFF state (S212, YES), the installation management unit 24 instructs the ECU 11 associated with the optional function instructed by the execution preparation instruction to prepare for execution of the optional function (i.e., to make the optional function executable) (S214).

[0082] At that time, if the software program required to execute the requested optional function is not installed in the associated ECU 11, the installation management unit 24 installs the software program downloaded in step S210 in the associated ECU 11. After preparing to execute the requested optional function, the installation management unit 24 ends the function start process.

[0083] On the other hand, when it is determined in step S208 that the preparation for execution of the requested optional function is not possible (S208, NO), the notification unit 37 instructs the terminal device 6 to output a notification that preparation for the requested optional function is not possible (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. Alternatively, the notification unit 37 of the management server 4 may present, in the function list, optional functions determined to be ready for execution and not present optional functions determined to be not ready for execution. Specifically, the notification unit 37 may, for example, refer to the management information 33 in response to receiving a function list request from the terminal device 6, create a function list including only optional functions determined to be ready for execution, and transmit 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 failures of the ECU 11 and the equipment 12, but the failure information can include at least information about failures of the ECU 11 or the equipment 12.

[0086] In the above-described embodiment, the software programs necessary to realize the optional functions are downloaded from the management server 4 to the vehicle management device 3, but they may also 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, if the optional function for which the terminal device 6 has sent a function start request is not ready for execution, no billing process or permission to use the optional function is performed, but billing process and permission to use the optional function may be performed with the consent of the user U via the terminal device 6. In this case, the user U can immediately use the optional function after carrying out necessary repairs or the like on the vehicle 2.

[0088] In the above embodiment, the billing process performed by the permission unit 38 of the management server 4 is the monthly usage fee for the optional function, but it may be the purchase fee for the optional function.

[0089] In the above-described embodiment, the user U makes a request to start using an optional function through the terminal device 6. In addition, the user U may also make a request to stop using an optional function that has already been started through the terminal device 6. The permission unit 38 of the management server 4 that receives the request to stop using the optional function can stop charging for the optional function and update the information on whether or not execution of the optional function is permitted (the rightmost column of the table in FIG. 7) in the management information 33 to "prohibited", and then instruct the vehicle management device 3 to prohibit execution of the optional function. The installation management unit 24 of the vehicle management device 3 follows the instruction and prohibits the associated ECU 11 from executing the optional function.

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

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

[0092] The present invention is not limited to the configurations of the above-described embodiments, and can be embodied in various forms without departing from the spirit and scope of the present invention.

[0093] [8. Configuration supported by the above embodiment] The above-described embodiment supports the following configurations.

[0094] (Configuration 1) A function management system that manages the use of optional functions in a vehicle, comprising: an information collection unit that collects failure information including information about failures of an electronic control device installed in the vehicle and / or information about failures of equipment controlled by the electronic control device; and a judgment unit that judges whether or not each of the optional functions can be prepared for execution to start using the optional function, wherein, based on the failure information, when a failure is found in the electronic control device or the equipment required to execute the optional function, the judgment unit judges that the optional function cannot be prepared for execution. 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 equipment can be detected prior to a user requesting the use of the optional function. Therefore, at the time of the request, the user can be quickly informed of whether the requested optional function is ready for execution, thereby facilitating the use of the optional function.

[0095] (Configuration 2) A function management system as described in configuration 1, comprising a reception unit that receives a request to start using the optional functions 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 optional functions and the optional function is determined to be not ready for execution, the notification unit outputs a notification to the user via the terminal device that the optional function cannot be used. According to the function management system of configuration 2, when a user requests to start using an optional function, if the optional function cannot be prepared for execution due to equipment failure or the like, the user is notified of this fact, so that the user can take measures such as considering other alternative optional functions, thereby facilitating the use of the optional function.

[0096] (Configuration 3) A function management system as described in Configuration 1, further comprising a notification unit that presents a list of the optional functions to a user via a terminal device, wherein the notification unit presents the optional functions in the list that are determined to be ready for execution, and does not present the optional functions that are determined not to be ready for execution. According to the function management system of configuration 3, optional functions that cannot be prepared for execution are not presented to the user, so that the user can select a desired optional function from among the presented optional functions that can be prepared for execution, thereby facilitating the use of optional functions.

[0097] (Configuration 4) A function management system described in any one of configurations 1 to 3, wherein the electronic control device performs self-diagnosis for operational malfunctions of the electronic control device and / or fault diagnosis for the equipment controlled by the electronic control device to generate the malfunction information, and the information collection unit collects the malfunction information from the electronic control device when a power switch of the vehicle is turned on and transmits it to the judgment unit. According to the function management system of configuration 4, the failure information collected when the vehicle's power switch is turned on is used, so even during a period when the communication state between the information collection unit and the vehicle may change, such as when the vehicle is traveling, the latest failure information can be used to appropriately determine whether or not an optional function is ready to be executed.

[0098] (Configuration 5) The function management system described in Configuration 4, wherein the information collection unit further transmits to the judgment unit the fault information received from the electronic control unit that discovers a fault in the electronic control unit and / or the equipment during a period when the power switch of the vehicle is turned on. According to the function management system of configuration 5, it is possible to determine whether or not an optional function is ready to be executed by reflecting the most recent failure condition.

[0099] (Configuration 6) A function management system as described in any of configurations 1 to 5, further comprising an installation management unit that manages the installation of software programs required to execute the optional functions on the electronic control device, the installation management unit installing software programs for the optional functions that are determined to be ready for execution, and not installing software programs for the optional functions that are determined to be not ready for execution. According to the function management system of configuration 6, the installation of unnecessary software programs can be avoided, thereby reducing the processing load.

[0100] (Configuration 7) The function management system according to configuration 6, wherein the installation management unit installs a software program required for executing the optional function into the electronic control device while a power switch of the vehicle is turned off. According to the function management system of configuration 7, for example, it is possible to prevent a situation in which the safety of the vehicle is reduced when the installation process of a software program for an optional function is performed on an electronic control device required for vehicle driving while the vehicle is driving.

[0101] (Configuration 8) A function management system described in any of configurations 1 to 7, including a vehicle management device having the information collection unit mounted on the vehicle, and a management server which is a server device having the judgment unit provided outside the vehicle. According to the function management system of configuration 8, the determination of whether or not an optional function is ready to be executed is processed in a server device outside the vehicle, so that the processing in the vehicle management device, which is an in-vehicle device, can be reduced.

[0102] (Configuration 9) A function management method performed by a computer of a function management system that manages the use of optional functions in a vehicle, the function management method comprising: an information collection step of collecting failure information including information about failures of an electronic control device installed in the vehicle and / or information about failures of equipment controlled by the electronic control device; and a judgment step of judging whether or not each of the optional functions is ready to be executed to start using it, wherein in the judgment step, based on the failure information, when a failure is found in the electronic control device or the equipment required to execute each of the optional functions, it is judged that the optional function is not ready to be executed. According to the function management method of configuration 9, an optional function that cannot be prepared for execution due to a failure of the electronic control device or equipment can be detected prior to a user request for use of the optional function. Therefore, at the time of the request for use, the user can be quickly informed of whether the requested optional function is ready for execution, thereby facilitating the use of the optional function. [Explanation of symbols]

[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...equipment, 12a...a equipment, 12b...b equipment, 12c...c equipment, 12d...d equipment, 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 RAM, 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...exit button.

Claims

1. A function management system for managing the use of optional functions in a vehicle, an information collecting unit that collects failure information including information on a failure of an electronic control device mounted on the vehicle and / or information on a failure of a device controlled by the electronic control device; a determination unit that determines whether or not each of the optional functions is ready for use; A function management system comprising:

2. a reception unit that receives a request to start using the optional function from a terminal device; a notification unit for notifying a user via the terminal device; When the reception unit receives a request to start using any of the optional functions and the optional function is determined to be inoperable, the notification unit outputs a notification to the user via the terminal device that the optional function cannot be used. The function management system according to claim 1 .

3. a notification unit that presents a list of the optional functions to a user via a terminal device; the notification unit presents the optional features in the list that are determined to be ready for execution. The function management system according to claim 1 .

4. a notification unit that presents a list of the optional functions to a user via a terminal device; The notification unit does not present the optional function determined to be inoperable in the list. The function management system according to claim 1 .

5. The electronic control device performs a self-diagnosis for an operational failure of the electronic control device and / or a failure diagnosis for the device controlled by the electronic control device to generate the failure information; the information collecting unit collects the fault information from the electronic control unit when a power switch of the vehicle is turned on, and transmits the fault information to the determining unit; The function management system according to claim 1 .

6. The information collecting unit further transmits to the determining unit the failure information received from the electronic control unit that has discovered a failure in the electronic control unit and / or the device during a period in which a power switch of the vehicle is turned on. The function management system according to claim 5 .

7. an installation management unit that manages installation of a software program required for executing the optional function into the electronic control device; the installation management unit installs software programs of the optional features that are determined to be ready for execution; The function management system according to claim 1 .

8. an installation management unit that manages installation of a software program required for executing the optional function into the electronic control device; the installation management unit does not install the software program of the optional function that is determined to be unprepared for execution; The function management system according to claim 1 .

9. the installation management unit installs a software program required for executing the optional function into the electronic control unit while a 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 that is a server device provided outside the vehicle and that includes the determination unit; 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, comprising: An information collecting step of collecting failure information including information on a failure of an electronic control device mounted on the vehicle and / or information on a failure of a device controlled by the electronic control device; a determination step of determining whether each of the optional functions is ready for use; A function management method having the following features:

Citation Information

Patent Citations

  • Device and system vehicle remote operation

    JP2007015505A

  • Apparatus and methods for providing vehicle driving information

    JP2018140766A

  • Server, update management method, update management program and software update device

    JP2022007618A

  • Device for supporting repair, method for supporting repair, and program for supporting repair

    JP2022073600A

  • Information processing device and method

    JP2021189491A