Application execution platform device, management method, and on-board electronic control device

Abstract

An application execution platform device (20), which manages at least one application (11, 12, 13) installed in a vehicle, comprises storage units (S40, S50, S140) and an unusable item deletion unit (S170, S180). Each storage unit acquires data from at least one application, and stores the acquired data as cache data in association with acquisition source information indicating the application that is the acquisition source of the acquired data. When at least one application installed in the vehicle is updated or deleted, the unusable item deletion unit deletes unusable cache data, which is cache data that has become unusable, on the basis of the acquisition source information.

Description

Application Execution Infrastructure Device, Management Method, and In-Vehicle Electronic Control Device Cross-Reference to Related Applications

[0001] This international application claims the benefit of Japanese Patent Application No. 2024-166367, filed with the Japan Patent Office on September 25, 2024, the entire disclosure of which is incorporated herein by reference.

[0002] The present disclosure relates to an application execution infrastructure device, a management method, and an in-vehicle electronic control device for managing applications installed in a vehicle.

[0003] Patent Document 1 describes a technique for updating an application installed in a vehicle by OTA. OTA is an abbreviation for Over The Air.

[0004] Japanese Patent Application Laid-Open No. 2020-27636

[0005] As a result of the inventors' detailed examination, it has been found that there is a problem that when updating or deleting an application installed in a vehicle, it may cause a problem in the processing of another application that uses the data obtained from the application.

[0006] The present disclosure suppresses the occurrence of problems in applications installed in a vehicle.

[0007] One aspect of the present disclosure is an application execution infrastructure device for managing at least one application installed in a vehicle, comprising a storage unit and a non-usable deletion unit.

[0008] The storage unit is configured to obtain data from at least one application and store the obtained data as cache data in association with acquisition source information indicating the application that is the acquisition source of the obtained data.

[0009] The non-usable deletion unit is configured to delete non-usable cache data, which is cache data that cannot be used, based on the acquisition source information when at least one application installed in the vehicle is updated or deleted.

[0010] The application execution platform of this disclosure, configured in this manner, deletes unusable cache data when an application is updated or deleted. This prevents the application execution platform of this disclosure from continuing to use cache data that is no longer updated due to the update or deletion of an application, which could cause malfunctions in the processing of that application. For this reason, the application execution platform of this disclosure can prevent malfunctions in applications installed in vehicles.

[0011] Another aspect of this disclosure is a management method performed by an application execution platform device that manages at least one application installed in a vehicle.

[0012] In the management method disclosed herein, the application execution platform device acquires data from at least one application and stores the acquired data as cached data, linked to source information indicating the application from which the acquired data was obtained.

[0013] The application execution platform device deletes unusable cache data, which is cache data that can no longer be used, based on the source information, when at least one application installed in the vehicle is updated or deleted.

[0014] The management method described herein is a method executed on the application execution platform device described herein, and by executing this method, the same effects as those of the application execution platform device described herein can be obtained.

[0015] Another aspect of this disclosure is an in-vehicle electronic control unit mounted on a vehicle, comprising an application execution platform for managing at least one application installed in the vehicle.

[0016] The application execution platform device for the in-vehicle electronic control unit of this disclosure comprises a storage unit and an unusable deletion unit.

[0017] The in-vehicle electronic control device of this disclosure is a device equipped with the application execution platform device of this disclosure, and can achieve the same effects as the application execution platform device of this disclosure.

[0018] This is a block diagram showing the configuration of a vehicle control system. This is a functional block diagram showing the functional configuration of a vehicle control system. This is a functional block diagram showing the functional configuration of an ECU. This is a block diagram explaining the processes executed by the application execution platform. This is a flowchart showing the installation management process. This is a diagram showing the configuration of the second public API manifest and the first cache data manifest. This is a flowchart showing the update management process. This is a diagram showing the usage data correspondence table. This is a diagram explaining the update of the second public API manifest. This is a flowchart showing the expiration date management process.

[0019] Embodiments of the present disclosure will be described below with reference to the drawings.

[0020] The vehicle control system 1 of this embodiment is mounted on a vehicle. The vehicle may have an automatic driving function in addition to a manual driving function. The vehicle may be a hybrid vehicle having an engine and an electric motor as its driving source. The vehicle is not limited to a vehicle with an automatic driving function or a hybrid vehicle; it may also be a vehicle with only a manual driving function, or a vehicle having only an engine or only an electric motor as its driving source. Hereinafter, a vehicle equipped with the vehicle control system 1 will simply be referred to as a vehicle.

[0021] As shown in Figure 1, the vehicle control system 1 comprises one ECU 2, multiple ECUs 3, multiple ECUs 4, an external communication device 5, and an internal communication network 6. ECU stands for Electronic Control Unit.

[0022] ECU2 integrates multiple ECUs3 to achieve coordinated control for the entire vehicle.

[0023] Each ECU3 is provided for each domain, which is divided according to the vehicle's function, and primarily controls multiple ECU4s that reside within that domain. Each ECU3 is connected to its subordinate ECU4s via a separately provided lower-level network (e.g., CAN). CAN stands for Controller Area Network. Domains include, for example, powertrain, body, chassis, cockpit, collision safety, and driving safety.

[0024] ECUs 4 connected to ECU 3 belonging to the powertrain domain include, for example, an ECU 4 for controlling the engine, an ECU 4 for controlling the motor, and an ECU 4 for controlling the battery.

[0025] ECUs 4 connected to ECU 3 belonging to the body domain include, for example, an ECU 4 that controls the air conditioner and an ECU 4 that controls the doors.

[0026] ECUs 4 connected to ECU 3 belonging to the chassis domain include, for example, an ECU 4 for controlling the brakes and an ECU 4 for controlling the steering.

[0027] ECUs 4 connected to ECU 3 belonging to the cockpit domain include, for example, an ECU 4 that controls the display of meters and navigation, and an ECU 4 that controls input devices operated by the vehicle occupants.

[0028] ECU 4 connected to ECU 3, which belongs to the collision safety domain, includes, for example, an ECU 4 that controls airbags and seat belts.

[0029] ECU4 connected to ECU3, which belongs to the domain of driving safety, includes, for example, an ECU4 that provides driving assistance for collision avoidance based on information from an in-vehicle camera and radar.

[0030] Furthermore, one or more ECUs 4 do not belong to a domain and are directly connected to the in-vehicle communication network 6 without going through the ECU 3.

[0031] The external communication device 5 communicates data with communication devices outside the vehicle via a wide-area wireless communication network.

[0032] The in-vehicle communication network 6 includes CAN FD and Ethernet. Ethernet is a registered trademark. CAN FD is an abbreviation for CAN with Flexible Data Rate. CAN FD bus-connects ECU 4 to each ECU 3 and the external communication device 5. Ethernet connects ECU 4 to each ECU 3 and the external communication device 5 individually.

[0033] The ECU2 is an electronic control unit centered around a microcomputer equipped with a CPU2a, ROM2b, RAM2c, etc. The various functions of the microcomputer are realized by the CPU2a executing a program stored in a non-transitional physical recording medium. In this example, ROM2b corresponds to the non-transitional physical recording medium storing the program. Furthermore, the execution of this program executes the method corresponding to the program. Note that some or all of the functions performed by the CPU2a may be configured hardware-wise using one or more ICs. Also, the number of microcomputers constituting the ECU2 may be one or more.

[0034] ECU3, ECU4, and the external communication device 5 are all electronic control units, similar to ECU2, that are centered around a microcomputer equipped with a CPU, ROM, RAM, etc. The number of microcomputers constituting ECU3, ECU4, and the external communication device 5 may be one or more. ECU3 controls one or more ECU4. ECU2 controls one or more ECU3, or controls all ECU3, ECU4, and the external communication device 5 for the entire vehicle.

[0035] As shown in Figure 2, the vehicle control system 1 comprises a first service application 11, a second service application 12, a third service application 13, a first vehicle function block 14, a second vehicle function block 15, a third vehicle function block 16, a first vehicle function data storage unit 17, a second vehicle function data storage unit 18, a third vehicle function data storage unit 19, and an application execution platform 20.

[0036] The first, second, and third service applications 11, 12, and 13 are applications manufactured to provide services to vehicle users. The first, second, and third service applications 11, 12, and 13 provide vehicle users with different services from each other.

[0037] The first service application 11 in this embodiment is an application that can acquire data from other applications and extend its functionality.

[0038] The first service application 11 is a driving diagnostic application that, for example, acquires vehicle data to detect sudden acceleration and sudden steering by the driver and provides driving advice.

[0039] As an extension of the driving diagnostic application, features such as acquiring daily driving characteristics to provide personalized advice, and utilizing distraction and drowsiness information to provide more accurate driving advice are available.

[0040] The first service application 11 may be, for example, an in-car concierge application that makes suggestions such as air conditioning settings and detours based on the temperature inside the vehicle, navigation settings, and driving time.

[0041] As an extension of the in-car concierge application, features have been added, such as a function that suggests air conditioning settings based on the driver's pre-boarding information (e.g., heart rate, steps taken), and a function that suggests rest stops, air conditioning, and music settings using distraction and drowsiness information.

[0042] The second service application 12 in this embodiment is an application that can publish data generated within its own application.

[0043] The second service application 12 is, for example, a driver monitoring application that detects the driver's usual driving characteristics and instantaneous concentration by extracting the driver's driving characteristics from the images of the in-vehicle camera, steering wheel operation, brake operation, and accelerator operation, and issues warnings to the driver. The data published by the driver monitoring application is, for example, data indicating driving characteristics and data indicating concentration (e.g., distraction, drowsiness).

[0044] The second service application 12 is, for example, a healthcare application that manages the driver's health condition in cooperation with an application on a smartphone or the like, and makes voice calls and proposes breaks to the driver. The data published by the healthcare application is, for example, data indicating the driver's age, data indicating the driver's gender, and data indicating the driver's physical condition during driving (e.g., heart rate, sleep time, number of steps).

[0045] The first, second, and third vehicle function blocks 14, 15, and 16 are applications that collect vehicle data and perform vehicle control in order to provide services to vehicle users.

[0046] The first, second, and third vehicle function data storage units 17, 18, and 19 store the vehicle data collected by the first, second, and third vehicle function blocks 14, 15, and 16, respectively.

[0047] The application execution platform 20 includes an installation management unit 21, a startup management unit 22, an access management unit 23, a cache management unit 24, and a cache data storage unit 25.

[0048] The installation management unit 21 manages the installation and uninstallation of applications on the ECU 2.

[0049] The startup management unit 22 manages the startup of applications installed on the ECU 2.

[0050] The access management unit 23 manages the access of applications installed on the ECU 2 to vehicle data.

[0051] The cache management unit 24 manages the cache data used by the application.

[0052] The cache data storage unit 25 stores cache data used by the application.

[0053] As shown in Figure 3, the first, second, and third service applications 11, 12, and 13, the third vehicle function block 16, the third vehicle function data storage unit 19, and the application execution platform 20 are mounted on the ECU 2.

[0054] The first, second, and third service applications 11, 12, and 13 are downloaded to the ECU 2 by data communication between the server 100, which is installed outside the vehicle, and the external communication device 5.

[0055] The first vehicle function block 14 and the first vehicle function data storage unit 17 are mounted in one of the multiple ECUs 3. The first vehicle function block 14 collects vehicle data from the ECU 3 on which the first vehicle function block 14 is mounted, and from the ECUs 4 connected to this ECU 3.

[0056] The second vehicle function block 15 and the second vehicle function data storage unit 18 are installed in one of the multiple ECUs 3, different from the ECU 3 that is equipped with the first vehicle function block 14 and the first vehicle function data storage unit 17. The second vehicle function block 15 collects vehicle data from the ECU 3 equipped with the second vehicle function block 15 and the ECU 4 connected to this ECU 3.

[0057] The third vehicle function block 16 collects vehicle data from the ECU 2 on which the third vehicle function block 16 is installed, and from the ECU 4 which is directly connected to the in-vehicle communication network 6. The third vehicle function block 16 may also collect vehicle data from the ECU 3.

[0058] Next, we will explain a specific example of the process that the application execution platform 20 executes when the second service application 12 is installed on the ECU 2 while the first service application 11 is already installed on the ECU 2.

[0059] As shown in Figure 4, the cache management unit 24 of the application execution platform 20 has registered the first cache data manifest 61 and the first public API manifest 71. API stands for Application Programming Interface.

[0060] The first cache data manifest 61 associates, for each of the one or more cache data used by the first service application 11, the cache data used identification information that identifies the cache data and the validity period of the cache data.

[0061] The first public API manifest 71 indicates one or more public APIs published by the first service application 11.

[0062] The first service application 11 includes a first cache data manifest 61 and a first public API manifest 71. When the first service application 11 is installed on the ECU 2, the first cache data manifest 61 and the first public API manifest 71 are registered with the cache management unit 24.

[0063] As shown by arrow L1 in Figure 4, the installation management unit 21 of the application execution platform 20 installs the second service application 12 into the ECU 2.

[0064] The second service application 12 includes a second cache data manifest 62 and a second public API manifest 72. The second cache data manifest 62 associates the cache data used identification information and its validity period for each of the one or more cache data used by the second service application 12.

[0065] The second public API manifest 72 indicates one or more public APIs published by the second service application 12.

[0066] As indicated by arrow L2, the installation management unit 21 outputs the second cache data manifest 62 and the second public API manifest 72 included in the installed second service application 12 to the cache management unit 24.

[0067] The cache management unit 24 registers the second cache data manifest 62 and the second public API manifest 72 obtained from the installation management unit 21.

[0068] The cache management unit 24 generates a usage data correspondence table 80, described later, based on the already registered first cache data manifest 61 and first public API manifest 71, and the newly registered second cache data manifest 62 and second public API manifest 72.

[0069] As indicated by arrow L3, the cache management unit 24 obtains data from the second service application 12 that can be provided by the second service application 12 from the usage data used by the first service application 11, based on the first cache data manifest 61 and the second public API manifest 72.

[0070] As indicated by arrow L4, the cache management unit 24 outputs the data acquired from the second service application 12 to the first service application 11.

[0071] As indicated by arrow L5, the cache management unit 24 stores the data acquired from the second service application 12 as cache data in the cache data storage unit 25.

[0072] Cached data is accompanied by expiration information indicating its expiration date. The expiration date is calculated by adding the validity period of the corresponding data to the time the data was acquired.

[0073] For example, if the data was acquired at 12:34:56 PM on March 10, 2024, and the validity period is one month, the expiration date will be 12:34:56 PM on April 10, 2024.

[0074] Furthermore, if the data was acquired at 12:34:56 PM on March 10, 2024, and the validity period is 1 minute, the expiration date will be 12:35:56 PM on April 10, 2024.

[0075] The cache management unit 24 determines the validity period of the corresponding data by referring to the first cache data manifest 61.

[0076] Next, the procedure for the installation management process executed by the application execution platform 20 will be described. The installation management process is a process that is repeatedly executed while the ECU 2 is running.

[0077] When the installation management process is executed, the application execution platform 20 determines in S10 whether or not the application has been installed, as shown in Figure 5.

[0078] If the application is not installed, the application execution platform 20 terminates the installation management process. On the other hand, if the application is installed, the application execution platform 20 registers the cache data manifest and public API manifest included in the application installed in S10 in S20. If the cache data manifest and public API manifest for the same application are already registered, the application execution platform 20 updates the cache data manifest and public API manifest by overwriting the already registered cache data manifest and public API manifest with the cache data manifest and public API manifest for the application installed in S10.

[0079] In S30, the application execution platform 20 generates a data usage table 80 based on one or more registered cache data manifests and one or more registered public API manifests.

[0080] In S40, the application execution platform 20 retrieves the data set in the cache data manifest registered in S20 from an already installed application and stores it as cache data in the cache data storage unit 25.

[0081] For example, suppose the second service application 12 is already installed, and the first service application 11 is not installed. Therefore, suppose the second cache data manifest 62 and the second public API manifest 72 are registered, and the first cache data manifest 61 and the first public API manifest 71 are not registered.

[0082] For example, as shown in Figure 6, the second public API manifest 72 sets up public APIs that include an API that provides data indicating driving characteristics, an API that provides data indicating whether or not the driver is distracted, and an API that provides data indicating whether or not the driver is drowsy.

[0083] The first cache data manifest 61 sets the cache data to be used by the first service application 11 as data indicating driving characteristics, data indicating whether or not the driver is distracted, and data indicating whether or not the driver is drowsy.

[0084] Therefore, when the first service application 11 is installed and the first cache data manifest 61 is registered, the application execution platform 20 obtains data indicating driving characteristics, data indicating whether or not the driver is distracted, and data indicating whether or not the driver is drowsy from the second service application 12 and stores them in the cache data storage unit 25.

[0085] When the processing in S40 is completed, as shown in Figure 5, in S50, the application execution platform 20 retrieves the data set in the cache data manifest that was already registered before the application was installed in S10 from the application installed in S10, and stores it as cache data in the cache data storage unit 25.

[0086] For example, suppose the first service application 11 is already installed, and the second service application 12 is not installed. Therefore, suppose the first cache data manifest 61 and the first public API manifest 71 are registered, and the second cache data manifest 62 and the second public API manifest 72 are not registered.

[0087] Therefore, once the second service application 12 is installed and the second public API manifest 72 is registered, the application execution platform 20 determines, based on the first cache data manifest 61 and the second public API manifest 72, that it can obtain data indicating driving characteristics, data indicating the presence or absence of distraction, and data indicating the presence or absence of drowsiness from the second service application 12. As a result, the application execution platform 20 obtains the data indicating driving characteristics, data indicating the presence or absence of distraction, and data indicating the presence or absence of drowsiness from the second service application 12 and stores them as cache data in the cache data storage unit 25.

[0088] Once the S40 process is complete, the application execution platform 20 terminates the installation management process.

[0089] Next, the procedure for the update management process executed by the application execution platform 20 will be described. The update management process is a process that is repeatedly executed while the ECU 2 is running.

[0090] When the update management process is executed, the application execution platform 20 determines in S110 whether the application has been updated or deleted, as shown in Figure 7. If the application has not been updated and has not been deleted, the application execution platform 20 terminates the update management process.

[0091] On the other hand, if an application is updated or deleted, the application execution platform 20 updates or deletes the cache data manifest and public API manifest of the updated or deleted application in S120. That is, if an application is updated, the application execution platform 20 registers a new cache data manifest and public API manifest for the updated application. Also, if an application is deleted, the application execution platform 20 deletes the cache data manifest and public API manifest of the deleted application.

[0092] In S130, the application execution platform 20 generates a data usage table 80 based on one or more registered cache data manifests and one or more registered public API manifests.

[0093] In step S140, the application execution platform 20 retrieves data that has become available due to the application update from an already installed application and stores it as cache data in the cache data storage unit 25.

[0094] In step S150, the application execution platform 20 determines, based on the data usage table 80, whether or not there is any cached data that has become unnecessary due to the update or deletion of the application.

[0095] As shown in Figure 8, the data usage table 80 associates, for each of the multiple cache data, the cache data usage identification information, one or more application identification information that identifies one or more applications that use the cache data, and source information that indicates the source from which the cache data was obtained.

[0096] For example, the usage data correspondence table 80 shown in Figure 8 indicates that the cached data for "driving characteristics" is used by the first service application 11 and the third service application 13. The usage data correspondence table 80 also indicates that the cached data for "distraction" is used only by the first service application 11.

[0097] If the first service application 11 is deleted, the cached data for "distraction" is determined to be unnecessary cached data. On the other hand, the cached data for "driving characteristics" is used not only by the first service application 11 but also by the third service application 13, so even if the first service application 11 is deleted, it is determined that the cached data for "driving characteristics" is not unnecessary cached data.

[0098] If there is no cache data that is no longer needed in S150, the application execution platform 20 proceeds to S170, as shown in Figure 7.

[0099] On the other hand, if there is cache data that is no longer needed, the application execution platform 20 deletes the cache data that is no longer needed due to the update or deletion of the application from the cache data storage unit 25 in S160 and proceeds to S170.

[0100] When the process moves to S170, the application execution platform 20 determines whether or not there is cache data related to the public API that became unavailable due to the application being updated or deleted in S110.

[0101] For example, as shown in Figure 9, if the second service application 12 is updated and the APIs that provide data indicating whether or not the user is distracted, and the APIs that provide data indicating whether or not the user is drowsy, are removed from the second public API manifest 72, then the cached data indicating whether or not the user is distracted and the cached data indicating whether or not the user is drowsy will correspond to the cached data associated with the public APIs that have become unavailable.

[0102] In S170, if there is no cache data related to the public API that has become unavailable, the application execution platform 20 terminates the update management process, as shown in Figure 7.

[0103] On the other hand, if there is cache data related to a public API that has become unavailable, the application execution platform 20 deletes the cache data related to the public API that has become unavailable from the cache data storage unit 25 in S180.

[0104] In S190, the application execution platform 20 notifies the vehicle driver that the functions related to the deleted cache data will be stopped or modified, and then terminates the update management process.

[0105] Next, the procedure for the deadline management process executed by the application execution platform 20 will be described. The deadline management process is a process that is repeatedly executed while the ECU 2 is running.

[0106] When the expiration management process is executed, the application execution platform 20 determines in S210 whether or not there is any cached data whose expiration date has passed, as shown in Figure 10. If there is no cached data whose expiration date has passed, the application execution platform 20 terminates the expiration management process.

[0107] On the other hand, if there is cached data whose expiration date has passed, the application execution platform 20 determines in S220 whether or not it is possible to update the expired cached data. In other words, the application execution platform 20 determines whether or not it is possible to obtain the data again from the application that was the source of the expired cached data.

[0108] If it is possible to update the expired cache data, the application execution platform 20 updates the cache data in S230 by obtaining the data again from the application that was the source of the expired cache data, and then terminates the expiration management process. This update also updates the expiration information attached to the cache data.

[0109] On the other hand, if the expired cache data cannot be updated in S220, the application execution platform 20 deletes the expired cache data from the cache data storage unit 25 in S240.

[0110] In S250, the application execution platform 20 notifies the vehicle driver that the functions related to the deleted cache data will be stopped or modified, and then terminates the expiration date management process.

[0111] The application execution platform 20 of the ECU2 configured in this way manages the first, second, and third service applications 11, 12, and 13 installed in the vehicle.

[0112] The application execution platform 20 is configured to acquire data from the second service application 12, and to store the acquired data as cached data, linked to source information indicating the application from which the acquired data was obtained.

[0113] The application execution platform 20 is configured to delete unusable cache data, which is cache data that can no longer be used, based on the source information, when the second service application 12 installed in the vehicle is updated or deleted.

[0114] In this application execution platform 20, when the second service application 12 is updated or deleted, it deletes unusable cache data. This prevents the application execution platform 20 from continuing to use cache data that is no longer updated due to the update or deletion of the second service application 12, which could cause malfunctions in the processing of the first service application 11. Therefore, the application execution platform 20 can prevent malfunctions in applications installed in vehicles.

[0115] Furthermore, the application execution platform 20 includes first and second cache data manifests 61 and 62, first and second public API manifests 71 and 72, and a usage data correspondence table 80, which include one or more usage cache data identification information that identifies each of the one or more cache data used by the first and second service applications 11 and 12 installed in the vehicle, and one or more source information indicating the application from which the one or more cache data is obtained.Hereinafter, the first and second cache data manifests 61 and 62, the first and second public API manifests 71 and 72, and the usage data correspondence table 80 will be collectively referred to as the usage dataset.

[0116] The application execution platform 20 is configured to update the data set used when the first and second service applications 11 and 12 are added to a vehicle, when the first and second service applications 11 and 12 are updated, or when the first and second service applications 11 and 12 are removed from a vehicle.

[0117] The application execution platform 20 retrieves data from the second service application 12 based on the data set being used, and stores the retrieved data as cached data, linked to the source information.

[0118] The application execution platform 20 deletes cached data based on the dataset being used.

[0119] Such an application execution platform 20 can appropriately save and delete cache data based on the data set being used when an application is added, updated, or deleted.

[0120] Furthermore, when the first and second service applications 11 and 12 are updated, the application execution platform 20 updates the correspondence between the cached data identification information and the source information in the used dataset. Such an application execution platform 20 can appropriately save and delete cached data based on the used dataset when an application is updated.

[0121] Furthermore, when the second service application 12 is deleted, the application execution platform 20 deletes the cache data associated with the deleted application as the source. Such an application execution platform 20 can appropriately delete cache data when an application is deleted.

[0122] Furthermore, the application execution platform 20 is configured to delete unnecessary cache data, which is cache data that is no longer needed, based on one or more used cache data identification information that identifies each of the one or more cache data used by the first and second service applications 11 and 12 installed in the vehicle, when the first and second service applications 11 and 12 are updated or when the first and second service applications 11 and 12 are removed from the vehicle.

[0123] Such an application execution platform 20 can prevent the continued state in which unnecessary cache data is stored unnecessarily.

[0124] Furthermore, cache data has an expiration date. The application execution platform 20 is configured to delete cache data that has expired and cannot be updated.

[0125] Such an application execution platform 20 can prevent the continued unnecessary storage of cache data whose expiration date has passed.

[0126] Furthermore, the first service application 11 is configured to use cached data obtained from the second service application 12. The ECU 2 is configured to notify the vehicle occupants that a function of the first service application 11 related to the deleted unusable cached data has been stopped or modified, if the cached data obtained by the first service application 11 from the second service application 12 has been deleted as unusable cached data.

[0127] Such an ECU2 can alert the vehicle occupants that the application's functionality has been stopped or modified.

[0128] In the embodiments described above, the application execution platform 20 corresponds to an application execution platform device, the ECU 2 corresponds to an in-vehicle electronic control device, and the first, second, and third service applications 11, 12, and 13 correspond to applications.

[0129] Furthermore, S40, S50, and S140 correspond to processing as a storage unit, S170 and S180 correspond to processing as an unusable data deletion unit, and S20, S30, S120, and S130 correspond to processing as a used data update unit.

[0130] Furthermore, S150 and S160 correspond to processing as an unnecessary deletion unit, and S210, S220, and S240 correspond to processing as an expiration date deletion unit.

[0131] Furthermore, the first service application 11 corresponds to the first application, the second service application 12 corresponds to the second application, and S190 corresponds to processing as a notification unit.

[0132] Although one embodiment of the present disclosure has been described above, the present disclosure is not limited to the above embodiment and can be implemented in various modified forms.

[0133] [Modification 1] In the above embodiment, the cache data related to the unavailable public API was deleted when it was determined that there was cache data related to the unavailable public API. However, the cache data related to the unavailable public API may be deleted after a predetermined grace period has elapsed since it was determined that there is cache data related to the unavailable public API.

[0134] Similarly, the above embodiment shows a configuration in which expired cache data is deleted when it is determined that there is expired cache data. However, it is also possible to delete expired cache data after a predetermined grace period has elapsed since it was determined that there is expired cache data.

[0135] The application execution platform 20 and its method described in this disclosure may be implemented by a dedicated computer provided by configuring a processor and memory programmed to execute one or more functions embodied by a computer program. Alternatively, the application execution platform 20 and its method described in this disclosure may be implemented by a dedicated computer provided by configuring a processor by one or more dedicated hardware logic circuits. Alternatively, the application execution platform 20 and its method described in this disclosure may be implemented by one or more dedicated computers configured by a combination of a processor and memory programmed to execute one or more functions and a processor configured by one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by the computer on a computer-readable non-transitional tangible recording medium. The method for realizing the functions of each part included in the application execution platform 20 does not necessarily need to include software, and all of its functions may be realized using one or more hardware components.

[0136] Multiple functions of one component in the above embodiment may be realized by multiple components, or one function of one component may be realized by multiple components. Furthermore, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, some parts of the configuration of the above embodiment may be omitted. Furthermore, at least some parts of the configuration of the above embodiment may be added to or replaced with the configuration of other above embodiments.

[0137] In addition to the application execution platform 20 described above, this disclosure can also be realized in various forms, such as a system that uses the application execution platform 20 as a component, a program for making a computer function as the application execution platform 20, a non-transitional physical recording medium such as a semiconductor memory on which this program is recorded, and a management method. [Technical Concept Disclosed in This Specification] [Item 1] An application execution platform device (20) for managing at least one application (11, 12, 13) installed in a vehicle, comprising: a storage unit (S40, S50, S140) configured to acquire data from at least one of the applications and store the acquired data as cache data linked to source information indicating the application from which the acquired data was acquired; and an unusable deletion unit (S170, S180) configured to delete unusable cache data, which is the cache data that can no longer be used, based on the source information when at least one of the applications installed in the vehicle is updated or deleted.

[0138] [Item 2] An application execution platform device as described in Item 1, further comprising: a usage dataset (61, 62, 71, 72, 80) including one or more usage cache data identification pieces that identify each of the one or more cache data used by at least one of the applications installed in the vehicle, and one or more source pieces that indicate the application from which the one or more cache data are obtained; and a usage data update unit (S20, S30, S120, S130) configured to update the usage dataset when at least one of the applications is added to the vehicle, at least one of the applications is updated, or at least one of the applications is removed from the vehicle, wherein the storage unit obtains data from at least one of the applications based on the usage dataset, stores the obtained data as cache data linked to the source piece, and the unusable deletion unit deletes the cache data based on the usage dataset.

[0139] [Item 3] An application execution platform device as described in Item 2, wherein the usage data update unit updates the correspondence between the usage cache data identification information and the acquisition source information in the usage dataset when at least one of the applications is updated.

[0140] [Item 4] An application execution platform device according to any one of Items 1 to 3, wherein the unusable deletion unit deletes the cache data to which the deleted application is linked as the source when at least one of the applications is deleted.

[0141] [Item 5] An application execution platform device according to any one of Items 1 to 4, further comprising an unnecessary deletion unit (S150, S160) configured to delete unnecessary cache data, which is the cache data that is no longer needed, based on one or more used cache data identification information that identifies each of the one or more cache data used by the at least one application installed in the vehicle, when at least one of the applications is updated or at least one of the applications is deleted from the vehicle.

[0142] [Item 6] An application execution platform device according to any one of Items 1 to 5, wherein the cache data has an expiration date set, and further comprises an expiration date deletion unit (S210, S220, S240) configured to delete the cache data whose expiration date has expired and which cannot be updated.

[0143] [Item 7] A management method performed by an application execution platform device (20) that manages at least one application (11, 12, 13) installed in a vehicle, comprising: acquiring data from at least one of the applications; storing the acquired data as cache data linked to source information indicating the application from which the acquired data was acquired; and, when at least one of the applications installed in the vehicle is updated or deleted, deleting the unusable cache data, which is the cache data that can no longer be used, based on the source information.

[0144] [Item 8] An in-vehicle electronic control device (2) mounted on a vehicle, comprising an application execution platform device (20) for managing at least one application (11, 12, 13) installed in the vehicle, wherein the application execution platform device comprises a storage unit (S40, S50, S140) configured to acquire data from at least one of the applications and store the acquired data as cache data linked to source information indicating the application from which the acquired data was acquired, and an unusable deletion unit (S170, S180) configured to delete unusable cache data, which is the cache data that can no longer be used, based on the source information when at least one of the applications installed in the vehicle is updated or deleted.

[0145] [Item 9] An in-vehicle electronic control device as described in Item 8, wherein of at least one application installed in the vehicle, one application is designated as a first application (11), and one application different from the first application is designated as a second application (12), the first application is configured to use the cache data obtained from the second application, and further comprises a notification unit (S190) configured to notify the occupants of the vehicle that a function of the first application related to the deleted unusable cache data has been stopped or modified as a result of the cache data obtained by the first application from the second application being deleted as unusable cache data by the unusable deletion unit.

Claims

1. An application execution platform device (20) for managing at least one application (11, 12, 13) installed in a vehicle, comprising: a storage unit (S40, S50, S140) configured to acquire data from at least one of the applications and store the acquired data as cache data linked to source information indicating the application from which the acquired data was acquired; and an unusable deletion unit (S170, S180) configured to delete unusable cache data, which is the cache data that can no longer be used, based on the source information when at least one of the applications installed in the vehicle is updated or deleted.

2. An application execution platform device according to claim 1, further comprising: a usage dataset (61, 62, 71, 72, 80) including one or more usage cache data identification information that identifies each of the one or more cache data used by at least one of the applications installed in the vehicle, and one or more source information indicating the application from which the one or more cache data is obtained; and a usage data update unit (S20, S30, S120, S130) configured to update the usage dataset when at least one of the applications is added to the vehicle, at least one of the applications is updated, or at least one of the applications is removed from the vehicle, wherein the storage unit obtains data from at least one of the applications based on the usage dataset, stores the obtained data as cache data linked to the source information, and the unusable deletion unit deletes the cache data based on the usage dataset.

3. An application execution platform according to claim 2, wherein the usage data update unit updates the correspondence between the usage cache data identification information and the acquisition source information in the usage dataset when at least one of the applications is updated.

4. An application execution platform according to any one of claims 1 to 3, wherein the unusable deletion unit deletes the cache data associated with the deleted application as the source when at least one of the applications is deleted.

5. An application execution platform according to any one of claims 1 to 3, further comprising an unnecessary deletion unit (S150, S160) configured to delete unnecessary cache data, which is the cache data that is no longer needed, based on one or more used cache data identification information that identifies each of the one or more cache data used by the at least one application installed in the vehicle, when at least one of the applications is updated or at least one of the applications is deleted from the vehicle.

6. An application execution platform according to any one of claims 1 to 3, wherein the cache data has an expiration date set, and further comprises an expiration date deletion unit (S210, S220, S240) configured to delete the cache data whose expiration date has expired and which cannot be updated.

7. A management method performed by an application execution platform device (20) that manages at least one application (11, 12, 13) installed in a vehicle, comprising: acquiring data from at least one of the applications; storing the acquired data as cache data linked to source information indicating the application from which the acquired data was acquired; and, when at least one of the applications installed in the vehicle is updated or deleted, deleting the unusable cache data, which is the cache data that can no longer be used, based on the source information.

8. An in-vehicle electronic control device (2) mounted on a vehicle, comprising an application execution platform device (20) for managing at least one application (11, 12, 13) installed in the vehicle, wherein the application execution platform device comprises a storage unit (S40, S50, S140) configured to acquire data from at least one of the applications and store the acquired data as cache data linked to source information indicating the application from which the acquired data was acquired, and an unusable deletion unit (S170, S180) configured to delete unusable cache data, which is cache data that can no longer be used, based on the source information when at least one of the applications installed in the vehicle is updated or deleted.

9. An in-vehicle electronic control device according to claim 8, wherein, of at least one application installed in the vehicle, one application is designated as a first application (11), and one application different from the first application is designated as a second application (12), the first application is configured to use the cache data obtained from the second application, and further comprises a notification unit (S190) configured to notify the occupants of the vehicle that a function of the first application related to the deleted unusable cache data has been stopped or modified as a result of the cache data obtained by the first application from the second application being deleted as unusable cache data by the unusable deletion unit.

Images