Function management system, function management method, and server

Abstract

A server (2) compares function status information received from a controller (10) of a vehicle (1) that indicates whether functions provided by ECUs of the vehicle (1) are enabled or disabled with function status information that has been stored in advance at a database (20) of the server (2) and, when a function that is stored as enabled at the database (20) of the server (2) is indicated as disabled by the function status information received from the controller (10), transmits a signal to enable the function indicated as disabled to the controller (10).

Description

Function management system, function management method, and server

[0001] The present invention relates to a function management system, a function management method, and a server.

[0002] A technology is known that, when an external device is connected in a state in which it can execute a function, enables the external device to execute the function and stops at least one of the functions that the vehicle device can execute (Patent Document 1).

[0003] Japanese Patent Application Laid-Open No. 2022-114162

[0004] However, the technology described in Patent Document 1 has the problem that when a function is disabled in a vehicle outside the management of the server that manages the functions that the vehicle can execute, the functions that can actually be executed in the vehicle may not match the status of the function managed by the server.

[0005] The problem that the present invention aims to solve is to provide a function management system, a function management method, and a server that can match functions that can actually be executed in a vehicle with the status of those functions managed by a server.

[0006] The present invention solves the above problem by comparing function status information received from a controller provided in the vehicle, which indicates whether a function provided by the vehicle's ECU is enabled or disabled, with function status information pre-stored in a server database, and if a function stored as enabled in the server database is indicated as disabled in the function status information received from the controller, sending a signal to the controller to enable the function indicated as disabled.

[0007] According to the present invention, it is possible to make the functions that can actually be executed in the vehicle coincide with the status of the functions managed by the server.

[0008] Fig. 1 is a block diagram showing an example of a function management system according to an embodiment of the present invention. Fig. 2 is a diagram showing an example of a flowchart of control processing of a function management method executed by the function management system according to the embodiment. Fig. 3 is a diagram showing an example of function management by the function management system according to the embodiment. Fig. 4 is a diagram showing an example of function management by the function management system according to the embodiment. Fig. 5 is a diagram showing an example of function management by the function management system according to the embodiment.

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of a function management system, a function management method, and a server according to the present invention will be described below with reference to the accompanying drawings.

[0010] FIG. 1 is a block diagram of a function management system according to an embodiment of the present invention. The function management system 100 includes a vehicle 1, a function management server 2, and a purchase management server 3. The function management system 100 is a system for transmitting and receiving data between the vehicle 1 equipped with a controller 10 and the function management server 2 via a network 4 (wireless communication), and manages functions provided by an electronic control unit (ECU) of the vehicle 1. The functions provided by the ECU of the vehicle 1 are functions implemented by software (firmware) of the ECU. The function management system 100 may also include a software update server (not shown) in addition to the function management server 2. The software update server is a server that executes FOTA (Firmware Over The Air), which can update the software of the ECU installed in the vehicle 1 via OTA (Over The Air). The software update server may be the same server as the function management server 2 or a different server.

[0011] The controller 10 manages function information of the ECUs of the vehicle 1. For example, the controller 10 is a master ECU. The controller 10 transmits and receives information between the ECUs and the function management server 2. The number of ECUs to be managed may be multiple. In the example of FIG. 1 , the ECUs include four ECUs: ECU 11, ECU 12, ECU 13, and ECU 14. In this embodiment, the number of ECUs to be managed is four, but this is not limited to four, and any number of ECUs may be managed. The controller 10 and each ECU are connected via a communication network such as CAN or LIN, allowing them to transmit and receive data to and from each other.

[0012] ECU 11, ECU 12, ECU 13, and ECU 14 are ECUs subject to function management. These ECUs include a body system ECU, a driving system ECU, a multimedia system ECU, and a power supply system ECU. Each ECU has functional blocks such as a microcomputer consisting of a CPU, ROM, RAM, and flash memory, a power supply circuit, and a data transfer circuit. The flash memory stores programs for implementing the ECU's software. The microcomputer executes the programs stored in the flash memory to perform various processes, thereby realizing each function of the ECU's software. Each ECU may have one function or multiple functions. Each ECU has function information regarding its own functions. The function information includes function identification information and function status information. Details of this information will be described later. Functions provided in an ECU are set to an enabled or disabled state. When a function provided in an ECU is enabled, the function can be executed. When a function provided in an ECU is disabled, the function cannot be executed.

[0013] The function management server 2 manages function information for multiple vehicles 1. The function management server 2 has a database 20. The database 20 stores, for each vehicle 1, function information related to functions provided by the ECU of the vehicle 1. The vehicle 1 is managed by vehicle identification information that identifies the vehicle 1. The vehicle identification information is, for example, a vehicle ID such as a VIN (Vehicle Identification Number) that indicates the vehicle 1. Each function provided by the ECU of the vehicle 1 is managed by function identification information that identifies the function. The function identification information is, for example, a function ID (hereinafter also referred to as FID). The database 20 stores, for each function, the function identification information and function status information that indicates whether the function is enabled or disabled, in association with each other. The database 20 may also store ECU identification information that identifies the ECU that has the function. The function management server 2 is an example of a "server" as defined in the claims.

[0014] When there are differences in grades of vehicles 1 due to differences in destinations, there are also differences in the functions that can be provided by the vehicles 1. However, it is difficult for the function management server 2 to manage the differences in functions between the vehicles 1. For example, when a function is added to the vehicle 1 by the ECU of the vehicle 1 performing a software update via OTA, it is difficult for the function management server 2 to recognize what functions were added after the OTA. In that case, the vehicle 1 will not be able to provide the new functions to the customer who owns it.

[0015] There are cases where a customer wants to enable a function provided in the ECU of the vehicle 1 after signing a purchase contract for the vehicle 1, or to enable a function in the vehicle 1 if the customer purchases the function separately. The functions that can be provided vary from vehicle to vehicle, and the number of functions provided in the vehicle 1 increases when functions are added to the vehicle 1 through software distribution via FOTA or software updates via a diagnostic device, USB, etc. In such cases, it is difficult for the function management server 2 to manage which functions are enabled in each vehicle 1.

[0016] Furthermore, each ECU may disable its functions due to circumstances outside the control of the function management server 2. For example, circumstances outside the control of the function management server 2 include when a software update such as a configuration update or reprogramming using a diagnostic device is performed, when the ECU is reset, when an IVI (In-Vehicle Infotainment) performs initialization from the Factory Reset menu, or when information is cleared for some reason. To address these cases, in this embodiment, the function management server 2 acquires ECU function information from the controller 10 of the vehicle 1, thereby managing the ECU function information more accurately.

[0017] When function management server 2 receives function information including function identification information and function status information from controller 10, it compares the function status information received from controller 10 with function status information pre-stored for each function in database 20. When a function stored as enabled in database 20 is indicated as disabled in the function status information received from controller 10, function management server 2 transmits a signal to controller 10 to enable the function indicated as disabled.

[0018] The function management server 2 may compare the function identification information when it receives function information including function identification information and function status information from the controller 10. The function management server 2 compares the function identification information received from the controller 10 with function identification information pre-stored in the database 20. If the function identification information received from the controller 10 is not stored in the database 20, the function management server 2 newly adds the function identification information received from the controller 10 and the function status information associated with the function identification information to the database 20.

[0019] The purchase management server 3 is a server that manages customer purchase information. When a customer enters into a purchase contract for a vehicle 1, the customer's purchase information is registered in the purchase management server 3. The purchase information includes customer identification information for identifying the customer, vehicle identification information for the vehicle owned by the customer, and function information for functions provided in the vehicle. The purchase management server 3 has a database 30. The database 30 stores function information for each vehicle 1 purchased by the customer, the function information being related to functions provided by the ECU of the vehicle 1. As with the function management server 2, the vehicle 1 is managed by vehicle identification information that identifies the vehicle 1. The database 30 stores function status information for each function, indicating whether the function is enabled or disabled. The database 30 also stores ECU identification information that identifies the ECU that executes the function. The purchase management server 3 stores the function information for the vehicle 1 owned by the customer in association with the customer identification information according to the customer's purchase. Unlike the function management server 2, the purchase management server 3 stores customer information but does not store ECU identification information that identifies the ECU that executes the function.

[0020] The controller 10 acquires function information of the ECUs of the vehicle 1 from the ECUs of the vehicle 1 and transmits the information to the function management server 2. Specifically, the controller 10 acquires function status information indicating whether the function is enabled or disabled, in association with function identification information for each function. The controller 10 transmits function information including the acquired function status information to the function management server 2. Furthermore, when the controller 10 receives a signal to enable a specific function from the function management server 2, it transmits a signal to enable the function to the ECU that executes the function.

[0021] The controller 10 also acquires function information related to functions provided in the ECU of the vehicle 1 from the ECU of the vehicle 1 at a predetermined timing. The predetermined timing includes the timing when the ignition switch of the vehicle 1 is turned on. That is, the controller 10 acquires function information from the ECU of the vehicle 1 every time the ignition switch of the vehicle 1 is turned on. The predetermined timing may be, for example, when the ECU performs authentication with the function management server 2 when it first connects to the function management server 2. This authentication is also referred to as a bootstrap. For example, when an old ECU is replaced with a new ECU, the ECU connects to the function management server 2 and executes a bootstrap. The predetermined timing may also be a regular interval. The predetermined timing may also be when the ECU software is updated or when the ECU is initialized. Because functions provided by the ECU may be disabled when the ECU software is updated or initialized, the controller 10 acquires function information from the ECU at the corresponding timing.

[0022] The controller 10 may also have a database for managing function information. The database of the controller 10 pre-stores function identification information, function status information, and ECU identification information for each function. When the controller 10 acquires function information including function identification information and function status information from an ECU, the controller 10 compares the function identification information and function status information acquired from the ECU with the function identification information and function status information stored in the database of the controller 10. If there is information that is different between the function identification information and function status information acquired from the ECU and the function identification information and function status information stored in the database of the controller 10, the controller 10 transmits information limited to the different function identification information and / or function status information to the function management server 2. The different information is information, among the function identification information and function status information acquired from the ECU, that differs from the function identification information and function status information stored in the database of the controller 10. For example, if the function identification information acquired from the ECU is not stored in the database of the controller 10, the function identification information corresponds to the different information. Furthermore, when function status information acquired from the ECU is invalid and function status information stored in the database of the controller 10 is valid, the function status information corresponds to the differential information. Note that in this embodiment, when there is differential information between the function identification information and function status information acquired from the ECU and the function identification information and function status information stored in the database of the controller 10, the controller 10 may transmit all of the function identification information and / or function status information including the differential function identification information and / or function status information to the function management server 2.

[0023] In the present embodiment, the ECU may store a predetermined flag indicating on or off. The predetermined flag is set to on when the ECU has transmitted function identification information and function status information to the controller 10 at least once. The ECU checks the predetermined flag, and when the predetermined flag indicates off, determines that the ECU has been replaced with the vehicle 1. When the ECU determines that the ECU has been replaced with the vehicle 1, the ECU transmits the function identification information and function status information to the controller 10. When the ECU has transmitted the function identification information and function status information to the controller 10, the ECU sets the flag to on.

[0024] Furthermore, a function may have version information of the function in addition to the function identification information.

[0025] Here, the control procedure of the function management method executed by the function management system according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of a flowchart of the control process of the function management method executed by the function management system according to this embodiment.

[0026] In step S101, the controller 10 acquires function status information. The function status information is information indicating whether a function is enabled or disabled, and is associated with function identification information for identifying each function provided by the ECU of the vehicle 1. In step S102, the controller 10 transmits the function status information to the function management server 2. In step S103, the function management server 2 compares the function status information received from the controller 10 with function status information previously stored in the database 20. In step S104, the function management server 2 determines whether a function stored as enabled in the database of the function management server 2 is indicated as disabled in the function status information received from the controller 10. If the function management server 2 determines that a function stored as enabled in the database of the function management server 2 is indicated as disabled in the function status information received from the controller 10, the function management server 2 proceeds to step S105. If the function management server 2 determines that a function stored as enabled in the database of the function management server 2 is not indicated as disabled in the function status information received from the controller 10, i.e., is indicated as enabled, the function management server 2 terminates the control flow. In step S105, the function management server 2 transmits a signal to the controller 10 to enable the function indicated as disabled. The controller 10, upon receiving the signal, transmits a signal to enable the function to the ECU that implements the function. The ECU that receives the signal enables the function.

[0027] <<Example 1>> Here, an example (Example 1) of function management by the function management system according to this embodiment will be described using FIG. 3 . FIG. 3 is a diagram illustrating an example of function management by the function management system according to this embodiment. In FIG. 3 , Table (A) is an example of function information stored in database 30 of purchase management server 3. Database 30 of purchase management server 3 includes function information related to functions provided by the ECU of customer A's vehicle (VIN: XXX). The function information includes function status information for each function (function identification information). Table (B) is an example of function information stored in database 20 of function management server 2. Database 20 of function management server 2 includes function information related to functions provided by the ECU of customer A's vehicle (VIN: XXX). The function information includes function status information and ECU identification information that implements the function for each function (function identification information). Tables (C) to (F) are examples of function information stored in the databases of ECUs 11, 12, 13, and 14. The database for each ECU contains function status information for each function (function identification information) implemented by that ECU. In these tables, the enabled and disabled states of functions are indicated by ON and OFF.

[0028] In the first embodiment, function management is described in a case where a function executable by an ECU differs from the function status stored in the function management server 2. In the first embodiment, a customer purchases a new function. When the customer purchases a function for each function ID (FID), the purchase management server 3 transmits a signal to the function management server 2 to enable the function. In the example of FIG. 3 , the customer purchases a function with function ID FID2 (hereinafter also referred to as the second function). The purchase management server 3 transmits a signal to the function management server 2 to enable the newly purchased second function (FID2). Furthermore, if the function is provided by subscription, the purchase management server 3 may transmit a signal to the function management server 2 to enable all disabled functions provided by the subscription associated with the vehicle contracted by the customer. When the function management server 2 receives a signal to enable the second function from the purchase management server 3, it first obtains function status information of the second function from the controller 10. Specifically, the function management server 2 transmits a signal to the controller 10 requesting transmission of function status information of the second function. The controller 10 acquires function status information from the ECU that is the target of the query. Specifically, the controller 10 transmits a signal to the ECU 12 requesting the ECU 12 to transmit function status information for each function. When the controller 10 acquires function status information for the second function from the ECU 12, the controller 10 transmits the acquired function status information to the function management server 2.

[0029] When the function management server 2 acquires function status information indicating that the second function is disabled, it transmits a signal to the controller 10 to enable the second function. The signal includes, for example, the second function (the function whose function ID is FID2), function status information for the second function (in this case, a signal to enable the function), and ECU identification information of the ECU that executes the second function (in this case, ECU 12). Note that in this embodiment, when the function management server 2 receives a signal to enable the second function from the purchase management server 3, it may transmit the signal to the controller 10 without acquiring function status information for the second function from the controller 10. In this case, the function management server 2 references the database 20 of the function management server 2 at the time the signal to enable the second function is received from the purchase management server 3, and if the second function is stored as disabled, it transmits a signal to the controller 10 to enable the second function. When the controller 10 receives a signal to enable the second function from the function management server 2, it transmits a signal to the ECU 12 to enable the second function. When the ECU 12 receives a signal from the controller 10 to enable the second function, the ECU 12 enables the second function (process (1) in FIG. 3 ). When the ECU 12 enables the second function, it sends a completion signal to the controller 10 indicating that the second function has been enabled. When the controller 10 receives the completion signal, it sends a completion signal to the function management server 2 indicating that the second function has been enabled. The function management server 2 enables the function status information of the second function stored in the database 20 (process (2) in FIG. 3 ). The function management server 2 sends a completion signal to the purchase management server 3 indicating that the second function has been enabled. The purchase management server 3 enables the function status information of the second function stored in the database 30 (process (3) in FIG. 3 ). Thereafter, the purchase management server 3 may notify the customer that the purchased second function has been enabled.

[0030] <<Example 2>> Next, an example (Example 2) of function management by the function management system according to this embodiment will be described with reference to FIG. 4 . FIG. 4 is a diagram illustrating an example of function management by the function management system according to this embodiment. The function management server 2 and the purchase management server 3 may store in advance in a database function information regarding functions that are estimated to be provided by the vehicle 1 based on the specifications of the vehicle 1. Based on the function identification information of each function transmitted from the vehicle 1, if function identification information not registered in the database is transmitted from the controller 10, the function management server 2 and the purchase management server 3 newly register the function identification information of the function in the database. The function management server 2 and the purchase management server 3 may store in the database not only function status information but also information such as whether the function is a trial version with some limited functions or an unpaid status, a low-cost version or a high-cost version, a time limit if the function is available for a limited period of time, whether the customer is confirmed to be a student in the case of a student version, the maximum number of simultaneous users, and a time limit if the use is temporarily prohibited for another reason (such as hardware).

[0031] In the second embodiment, function management is described for a case where a new function is added to an ECU by software or the like outside the management of the function management server 2. In the example of FIG. 4 , a fifth function (function with function ID FID5) is added to the ECU 12 (process (1) in FIG. 4 ). When the fifth function is added, the fifth function is disabled (OFF). When the ignition of the vehicle 1 is turned on, the controller 10 transmits a signal to each ECU included in the vehicle 1 requesting that the ECU transmit function status information. Each ECU transmits function identification information and function status information of the functions included in the ECU to the controller 10. The controller 10 transmits the received function information, including the function identification information of each function, to the function management server 2. The function management server 2 adds function information for the fifth function not stored in the database 20 (process (2) in FIG. 4 ). The function information includes function identification information, function status information, and ECU identification information. The function management server 2 transmits a signal indicating that the function information for the fifth function has been added to the purchase management server 3. The purchase management server 3 newly adds the fifth function to the database 30 (process (3) in FIG. 4 ). When a function is added, the function status information is stored in the databases of the function management server 2 and the purchase management server 3 in a disabled (OFF) state. Note that the controller 10 may acquire and transmit not only the identification information and function status information of each function but also the ECU identification information of the ECU that provides the function, but this is not limited to this embodiment. If the function identification information and the ECU identification information of the ECU that provides the function are stored in advance in the databases of the purchase management server 3 and the function management server 2, the controller 10 does not need to transmit the ECU identification information of the ECU that provides the function.

[0032] Furthermore, when adding a new function to the database 30, the purchase management server 3 may inquire of the customer whether or not to purchase the function. In this case, if the customer decides to purchase the function, the purchase management server 3 sends a signal to the function management server 2 to enable (ON) the purchased function. An example will be described below in which a fifth function (FID5) is purchased. The purchase management server 3 sends a signal to the function management server 2 to enable (ON) the fifth function. When the function management server 2 receives a signal to enable the fifth function from the purchase management server 3, it sends a signal to the controller 10 to enable the fifth function of the ECU 12. When the controller 10 receives a signal to enable the fifth function of the ECU 12 from the function management server 2, it sends a signal to the ECU 12 to enable the fifth function. When the ECU 12 receives a signal to enable the fifth function from the controller 10, it enables (ON) the fifth function.

[0033] When the ECU 12 has enabled the fifth function, it transmits a completion signal to the controller 10 indicating that the fifth function of the ECU 12 has been enabled. The controller 10 enables (ON) the fifth function stored in the database of the controller 10 and transmits a completion signal to the function management server 2 indicating that the fifth function of the ECU 12 in the vehicle 1 has been enabled. When the function management server 2 receives the completion signal from the controller 10, it enables (ON) the fifth function stored in the database 20 and transmits a completion signal to the purchase management server 3 indicating that the fifth function of the ECU 12 in the vehicle 1 has been enabled. When the purchase management server 3 receives the completion signal from the function management server 2, it enables (ON) the fifth function stored in the database 30.

[0034] In this embodiment, when the function management server 2 receives information indicating that function identification information not stored in the function management server 2 has been added to the vehicle 1, the function management server 2 stores the newly added function identification information and function status information for the vehicle 1. For example, a newly added function to the vehicle 1 is a function newly added through a software update using FOTA. The function management server 2 does not update the function status information corresponding to the function identification information of a function already registered in the database 20 of the function management server 2. If the function status information corresponding to the function identification information already registered in the database 20 of the function management server 2 differs from the information sent from the controller 10, the function management server 2 sends a signal to the controller 10 to enable the function in order to change it to match the information stored in the function management server 2. For example, this may be the case when the function status information is disabled in the vehicle 1 and enabled in the function management server 2.

[0035] The function management server 2 does not store accurate information regarding which functions are enabled for each vehicle 1. Therefore, the timing of acquiring function status information from the controller 10 is important. The timing of acquiring function status information will be described below. As a preprocessing step before an ECU of the vehicle 1 communicates with the function management server 2, the function management server 2 performs an ECU registration process to determine whether the communicating ECU is trustworthy. This process involves a bootstrap. For example, a case in which the ECU 11 performs a bootstrap will be described. When the ECU 11 performs a bootstrap, the ECU 11 transmits a signal to the controller 10 requesting acquisition of function status information. When the controller 10 receives this signal, it transmits a signal to all ECUs requesting transmission of function status information. The controller 10 transmits the information received from the ECUs to the function management server 2. In this case, the controller 10 may acquire function status information only from the ECU that sent the request (in this case, the ECU 11) rather than from all ECUs. Furthermore, since Bootstrap is a process performed by ECU 11 together with function management server 2, function management server 2 may send a signal to controller 10 requesting acquisition of function status information, and controller 10, upon receiving the signal, may acquire function status information of the functions from each ECU.

[0036] Furthermore, when the ECU undergoes a software update, new functions may be added. Therefore, when the software update is complete and the ECU is able to start up with the new software, the ECU sends a signal to the controller 10 requesting that function status information be obtained from the ECU. By obtaining the function status information, the controller 10 can notify the function management server 2 not only of the current function information but also of the addition of new functions.

[0037] Furthermore, when a malfunction occurs, each ECU may reset parameters to return to an initial state and resolve the malfunction. In this case, the function of the ECU may have returned to a default value rather than an expected value. This may result in the function status indicated in the function status information managed by the function management server 2 differing from the actual function status of the ECU. When each ECU detects a reset, the ECU sends a signal to the controller 10 requesting that the function status information be acquired from the ECU. The subsequent flow is the same as described above. The ECU may have a flag to detect that a parameter has been reset. When the ECU is reset, the ECU sets the flag to 0, determining that the function status information of the function has been reset and returned to the default, and then sends a signal to the controller 10 requesting that the function status information be acquired. When the ECU has completed transmitting the function status information to the controller 10, the ECU sets the flag to 1.

[0038] When the controller 10 transmits all information to the function management server 2 each time it acquires function status information from each ECU, in many cases the controller 10 transmits the same information to the function management server 2 as the information stored in the database 20 of the function management server 2. In this case, unnecessary communication costs are incurred, and as the number of vehicles from which the function management server 2 transmits function status information increases, the function management server 2 also has to compare the received information with the information stored in the database 20, update if there is an update target, and not update if there is no update target, even though updating the database is not actually necessary, resulting in an unnecessary workload. Therefore, when the controller 10 acquires function information related to functions from each ECU, it stores the acquired information in its database. Then, the next time function status information is acquired, the controller 10 updates the database by limiting the function status information stored in the database to functions that have changed or been added, and transmits function information to the function management server 2 limited to the changed or added functions. This reduces communication costs and the load on the server side by transmitting information only when there is a change and only function status information that has changed.

[0039] <<Example 3>> Next, an example (Example 3) of function management by the function management system according to this embodiment will be described with reference to FIG. 5 . FIG. 5 is a diagram illustrating an example of function management by the function management system according to this embodiment. In FIG. 5 , the controller 10 includes a database (Table (G)) managed by the controller 10. The database of the controller 10 includes, for each function, function identification information, function status information, and ECU identification information of the corresponding ECU. Example 3 describes function management when the functions executable by the ECU differ from the functions stored in the database of the controller 10. The example of FIG. 5 is an example of function management when the function status in the ECU differs from the function status in the databases of the function management server 2 and the controller 10. Specifically, this is a case where the fifth function of the ECU 12 is actually enabled (ON) as shown in Table (D), but the fifth function is disabled (OFF) in the databases of the function management server 2 and the controller 10 as shown in Tables (B) and (G). In such a case, when the controller 10 acquires function information from each ECU, it compares the acquired information with the information stored in the database to identify the difference. In the example of FIG. 5 , the controller 10 determines that the function status information of the fifth function is the difference, and enables the function status information of the fifth function stored in the controller 10's database. The purchase management server 3 transmits only the function status information of the fifth function to the function management server 2 and the purchase management server 3. The purchase management server 3 compares the function status information of the fifth function received from the controller 10 with the function status information of the fifth function stored in the database 30 of the purchase management server 3. Since the fifth function is disabled (OFF) in the database 30 of the purchase management server 3, the purchase management server 3 transmits a signal to the ECU 12 via the function management server 2 and the controller 10 to disable (OFF) the fifth function. Upon receiving this signal, the ECU 12 disables (OFF) the fifth function.

[0040] As described above, in the function management system and function management method according to this embodiment, a controller provided in a vehicle acquires, for each function provided by the vehicle's ECU, function status information indicating whether the function is enabled or disabled, in association with function identification information for identifying the function, and transmits the acquired function status information to a server. The server compares the function status information received from the controller with function status information pre-stored for each function in the server's database, and if a function stored as enabled in the server's database is indicated as disabled in the function status information received from the controller, transmits a signal to the controller to enable the disabled function. This allows the functions that can actually be executed in the vehicle to match the status of the function managed by the server.

[0041] In the function management system and function management method according to the present embodiment, the server compares the function identification information received from the controller with the function identification information previously stored in the server's database, and if the function identification information received from the controller is not stored in the server's database, the server newly adds the function identification information received from the controller and the function status information associated with the function identification information to the server's database. This makes it possible to match the status of functions that can actually be executed in the vehicle with the status of the functions stored in the database, even when a new function is added to the vehicle.

[0042] In the function management system and function management method according to this embodiment, the controller acquires function status information when the ECU authenticates with the server at the time of initial connection, thereby obtaining the status of functions that can actually be executed in the vehicle at the time of initial connection.

[0043] In the function management system and function management method according to this embodiment, the controller periodically acquires function status information, so that even if the status of a function that can actually be executed by the vehicle changes for some reason, the changed function status can be acquired.

[0044] In the function management system and function management method according to the present embodiment, the controller acquires function status information when the ECU software is updated, so that even if the status of the functions that can actually be executed in the vehicle changes due to the software update, the changed function status can be acquired.

[0045] In the function management system and function management method according to the present embodiment, the controller acquires function status information when the ECU is initialized, so that even if the status of the functions that can actually be executed in the vehicle changes as a result of the ECU being initialized, the controller can acquire the changed function status.

[0046] Furthermore, in the function management system and function management method according to this embodiment, the controller stores function identification information and function status information for each function in its database in advance, compares the function identification information and function status information acquired from the ECU with the function identification information and function status information stored in the controller's database, and if there is information that is different between the function identification information and function status information acquired from the ECU and the function identification information and function status information stored in the controller's database, transmits only the function identification information and / or function status information that is different to the server. In this way, by transmitting only information that needs to be updated to the server, it is possible to shorten communication time with the server and reduce the amount of transmitted data.

[0047] In the function management system and function management method according to this embodiment, the ECU stores a predetermined flag indicating on or off, checks the predetermined flag, and if the predetermined flag indicates off, determines that the ECU has been replaced with a vehicle, and if it determines that the ECU has been replaced with a vehicle, transmits function identification information and function status information to the controller, and the predetermined flag is set to on if the ECU has transmitted the function identification information and function status information to the controller at least once. This makes it possible to obtain the changed function status even if the state of the functions that can actually be executed in the vehicle changes due to the ECU replacement.

[0048] Furthermore, in this embodiment, the server that manages the functions provided by the vehicle's ECU receives, from the controller provided in the vehicle, function status information indicating whether the function is enabled or disabled, for each function, in association with function identification information for identifying the function, compares the function status information received from the controller with function status information that is pre-stored for each function in the server's database, and, if a function that is stored as enabled in the server's database is indicated as disabled in the function status information received from the controller, sends a signal to the controller to enable the function that is indicated as disabled.

[0049] It should be noted that the above-described embodiments have been described to facilitate understanding of the present invention, and are not intended to limit the present invention. Therefore, each element disclosed in the above-described embodiments is intended to include all design modifications and equivalents that fall within the technical scope of the present invention.

[0050] 100... function management system 1... vehicle 10... controller 11, 12, 13, 14... ECU 2... function management server 3... purchase management server

Claims

1. A function management system comprising a controller provided in a vehicle and a server, wherein the controller: for each function provided by an ECU of the vehicle, obtains function status information indicating whether the function is enabled or disabled, in association with function identification information for identifying the function, and transmits the obtained function status information to the server, and the server: compares the function status information received from the controller with function status information pre-stored for each function in the server's database, and when a function stored as enabled in the server's database is indicated as disabled in the function status information received from the controller, transmits a signal to the controller to enable the function indicated as disabled.

2. A function management system as described in claim 1, wherein the server compares the function identification information received from the controller with the function identification information pre-stored in the server's database, and if the function identification information received from the controller is not stored in the server's database, newly adds the function identification information received from the controller and the function status information associated with the function identification information to the server's database.

3. A function management system according to claim 1 or 2, wherein the controller acquires the function status information when the ECU performs authentication with the server when connecting to the server for the first time.

4. A function management system according to any one of claims 1 to 3, wherein the controller acquires the function status information at regular intervals.

5. A function management system according to any one of claims 1 to 4, wherein the controller acquires the function status information when the software of the ECU is updated.

6. A function management system according to any one of claims 1 to 5, wherein the controller acquires the function status information when the ECU is initialized.

7. A function management system according to any one of claims 1 to 6, wherein the controller: pre-stores the function identification information and the function status information for each function in the controller's database; compares the function identification information and the function status information acquired from the ECU with the function identification information and the function status information stored in the controller's database; and, if there is information that is different between the function identification information and the function status information acquired from the ECU and the function identification information and the function status information stored in the controller's database, transmits to the server only the function identification information and / or the function status information that is different.

8. A function management system as claimed in any one of claims 1 to 7, wherein the ECU stores a predetermined flag indicating on or off, checks the predetermined flag, and if the predetermined flag indicates off, determines that the ECU has been replaced with the vehicle, and if it is determined that the ECU has been replaced with the vehicle, transmits the function identification information and the function status information to the controller, and the predetermined flag is set to on if the ECU has transmitted the function identification information and the function status information to the controller at least once.

9. A function management method executed by a function management system comprising a controller provided in a vehicle and a server, wherein the controller: for each function provided by an ECU of the vehicle, obtains function status information indicating whether the function is enabled or disabled, in association with function identification information for identifying the function; transmits the obtained function status information to the server; and the server: compares the function status information received from the controller with the function status information pre-stored for each function in the server's database; and, if a function stored as enabled in the server's database is indicated as disabled in the function status information received from the controller, transmits a signal to the controller to enable the function indicated as disabled.

10. A server that manages functions provided by an ECU of a vehicle, which receives, from a controller provided in the vehicle, function status information indicating whether the function is enabled or disabled for each function, in association with function identification information for identifying the function; compares the function status information received from the controller with function status information pre-stored for each function in the server's database; and, when a function stored as enabled in the server's database is indicated as disabled in the function status information received from the controller, sends a signal to the controller to enable the function indicated as disabled.

Images