File distribution device, file acquisition device, file distribution system, file distribution method, and file distribution program
Patent Information
- Application Number
- JP2025077542
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-07
- Publication Date
- 2026-11-19
AI Technical Summary
Conventional systems require multiple copies of update files for each electronic control unit (ECU) with integrated System on a Chip (SoC), leading to resource consumption and potential degradation of non-volatile memory due to frequent rewriting.
A file distribution system that determines whether the update unit is on the same SoC as the distribution unit, transmitting files or storage location information accordingly to optimize resource usage and reduce unnecessary copying.
Reduces resource consumption and minimizes the degradation of non-volatile memory by optimizing the distribution of update files within the electronic control system.
Smart Images

Figure 2026181824000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a technology for updating software of an electronic control unit using an update file, and mainly relates to a vehicle-use file distribution apparatus, a file acquisition apparatus, a file distribution system, a file distribution method executed by the file distribution apparatus, and a file distribution program executable by the file distribution apparatus (hereinafter collectively referred to as the file distribution apparatus and the like).
Background Art
[0002] In automobiles, various electronic control units connected via an in-vehicle network are installed as an electronic control system. It is assumed that the software of the electronic control units is updated at appropriate times to add new functions, provide services, or implement cybersecurity measures in the electronic control system. For this purpose, dedicated software for updating the system, such as UCM (Update and Configuration Management), is provided in in-vehicle platforms represented by AUTOSAR (AUTomotive Open System ARchitecture).
[0003] Regarding system updates, Patent Document 1 and Patent Document 2 disclose inventions related to software updates in a system in which a plurality of virtual ECUs are constructed using a virtualized operating system such as a hypervisor. These patent documents describe that the update file is transmitted when the hypervisor of the source virtual ECU of the update file is different from the hypervisor of the destination virtual ECU, and when the hypervisors are the same, an instruction to access a storage unit that stores the update file is given, so that the software update using the update file is performed.
Prior Art Documents
Patent Documents
[0004] [Patent Document 1] Japanese Patent Publication No. 2022-85861 [Patent Document 2] Japanese Patent Publication No. 2022-85862 [Overview of the project] [Problems that the invention aims to solve]
[0005] Here, the inventors identified the following problem. With the increasing multi-functionality of electronic control units, a single ECU may incorporate multiple SoCs (System on a Chip). An SoC is an integrated circuit that incorporates a single integrated system, such as one in which a processor and memory are mounted on a single circuit board.
[0006] However, the conventional AUTOSAR specification manages update files separately for each update-related software. For example, if an OTA (Over The Air) client, UCMM (Update and Configuration Management Master), and UCMS (Update and Configuration Management Subordinate) are implemented on a single SoC, each will hold the same update file. This means that copies of the update file are necessary to maintain identical files, which consumes time and CPU resources during the copying process. Furthermore, frequent rewriting of non-volatile memory raises concerns about degradation of non-volatile memory, which has a limited number of write cycles.
[0007] Therefore, the present invention aims to reduce resource consumption caused by copying update files and other actions that are not necessarily required. [Means for solving the problem]
[0008] A file distribution device according to one aspect of this disclosure is: A file distribution system comprising: a file acquisition unit that acquires files for updating software; a distribution unit that distributes the files for updating the software; and an update unit that updates the software based on the files distributed from the distribution unit, wherein the file distribution device comprises at least the distribution unit, The aforementioned distribution unit, Storage section (203), A determination unit (204) determines whether the update unit, which is the destination of the file, is located on the same system-on-chip (SoC) as the distribution unit, The system includes a transmission unit (206) that transmits the aforementioned file or storage location information indicating the storage location of the aforementioned file to the update unit, If the determination unit determines that the update unit is located on a different SoC than the distribution unit, the transmission unit sends the file to the update unit. If the determination unit determines that the update unit is located on the same SoC as the distribution unit, the transmission unit transmits the storage location information to the update unit.
[0009] The numbers in parentheses attached to the claims and the constituent elements of the invention described in this section indicate the correspondence between the present invention and the embodiments described later, and are not intended to limit the present invention. [Effects of the Invention]
[0010] The file distribution device described herein makes it possible to reduce resource consumption caused by copying update files that are not necessarily required. [Brief explanation of the drawing]
[0011] [Figure 1] Diagram illustrating the location of the electronic control system in each embodiment. [Figure 2] This figure illustrates an example configuration of the electronic control system in each embodiment. [Figure 3] Diagram illustrating the layout of devices implementing OTA client, UCMM, and UCMS functions. [Figure 4]Block diagram illustrating the configuration of the file acquisition device 100 according to Embodiment 1 [Figure 5] Diagram illustrating an example of identification information for the file distribution device 200 and the file acquisition device 100 in Embodiment 1 [Figure 6] Diagram illustrating an example of storage position information ("first storage position information") in Embodiment 1 [Figure 7] Block diagram illustrating the configuration of the file distribution device 200 according to Embodiment 1 [Figure 8] Diagram illustrating an example of identification information for the file update device 300 and the file distribution device 200 in Embodiment 1 [Figure 9] Diagram illustrating the processing content of the file processing unit in Embodiment 1 [Figure 10] Diagram illustrating an example of storage position information ("second storage position information") in Embodiment 1 [Figure 11] Block diagram illustrating the configuration of the file update device 300 according to Embodiment 1 [Figure 12] Diagram illustrating an example of identification information for the file update device 300 in Embodiment 1 [Figure 13] Diagram illustrating an overview of the operation of each device in Embodiment 1 [Figure 14] Flowchart illustrating the detailed operation of the file acquisition device 100 according to Embodiment 1 [Figure 15] Flowchart illustrating the detailed operation of the file distribution device 200 according to Embodiment 1 [Figure 16] Diagram illustrating an example of identification information for the file update device 300 and the file distribution device 200 in Embodiment 2 [Figure 17] Diagram illustrating an overview of the operation of each device in Embodiment 2 [Figure 18] Flowchart illustrating the detailed operation of the file distribution device 200 according to Embodiment 2 [Figure 19] Diagram illustrating an example of identification information for the file update device 300 and the file distribution device 200 in Embodiment 3 [Figure 20] Diagram illustrating an overview of the operation of each device in Embodiment 3 [Figure 21] Flowchart illustrating the detailed operation of the file distribution device 200 in Embodiment 3. [Modes for carrying out the invention]
[0012] Embodiments of the present invention will be described below with reference to the drawings.
[0013] Furthermore, "the present invention" means the invention described in the claims or means for solving the problem, and is not limited to the following embodiments. Also, at least the words in quotation marks mean the words described in the claims or means for solving the problem, and are likewise not limited to the following embodiments.
[0014] The configurations and methods described in the dependent claims are optional configurations and methods in the invention described in the independent claims. The configurations and methods in embodiments corresponding to the configurations and methods described in the dependent claims, as well as configurations and methods described only in embodiments and not in the claims, are optional configurations and methods in the present invention. The configurations and methods described in embodiments when the claims are broader than the descriptions in embodiments are also optional configurations and methods in the present invention, in the sense that they are illustrative examples of the configurations and methods of the present invention. In any case, by describing them in the independent claims, they become essential configurations and methods of the present invention.
[0015] The effects described in the embodiments are those that occur when the configuration is that of an exemplary embodiment of the present invention, and are not necessarily effects of the present invention itself.
[0016] When there are multiple embodiments (including examples and variations; the same applies hereinafter), the configuration disclosed in each embodiment is not confined to that embodiment alone, but can be combined across embodiments. For example, the configuration disclosed in one embodiment may be combined with another embodiment. Alternatively, the configuration disclosed may be collected and combined in each of multiple embodiments.
[0017] The problems described in the section on the problems that the invention aims to solve are not publicly known problems, but rather problems that the inventors have discovered independently, and together with the structure and method of the present invention, these facts affirm the inventive step of the invention.
[0018] 1. Configurations and other prerequisites for each embodiment (1) Location where the electronic control system S and the electronic control device 10 are installed. Referring to Figure 1, the locations where the electronic control system S of each embodiment is installed will be described.
[0019] The electronic control system S that implements the file distribution device or file update device of each embodiment has one or more electronic control units (ECUs: hereinafter referred to as ECUs) 10 connected to a network.
[0020] The electronic control system S and the ECU 10 included therein, which realize the file distribution device and file update device of each embodiment, are "mounted" on a vehicle, which is a "mobile body," as shown in Figure 1(a). The following embodiments will be described based on the arrangement shown in Figure 1(a). Here, A "moving object" refers to any object that can move, regardless of its speed. It also includes objects that are stationary. Examples include, but are not limited to, automobiles, motorcycles, bicycles, pedestrians, ships, aircraft, and items carried on them. "To be mounted" includes not only cases where it is directly fixed to the moving object, but also cases where it is not fixed to the moving object but moves with it. Examples include cases where it is carried by a person riding on the moving object, or where it is mounted on cargo placed on the moving object.
[0021] In each embodiment, the electronic control system S is described as an in-vehicle system mounted on a vehicle. However, the electronic control system S is not limited to in-vehicle systems and can be applied to an electronic control system S installed in any location, as shown in Figure 1(b). For example, the electronic control system S may be mounted on a stationary or fixed object rather than a moving object. Alternatively, it may be installed in a building.
[0022] (2) Configuration of the electronic control system S Figure 2 shows an example of the configuration of the electronic control system S. The electronic control system S consists of multiple ECUs 10 and an in-vehicle network (NW1 to NW3) connecting them. Figure 2 shows eight ECUs (ECU10a to ECU10h) as an example, but naturally, the electronic control system S can consist of any number of ECUs. In the following explanation, when describing one or more ECUs as a whole, we will refer to them as ECU10 or each ECU10, and when describing individual electronic control devices, we will refer to them as ECU10a, ECU10b, ECU10c, ...
[0023] In the case of Figure 2, each ECU 10 is connected via an in-vehicle communication network, etc. For example, they are connected via an in-vehicle communication network such as CAN (Controller Area Network) or LIN (Local Interconnect Network). Alternatively, they may be connected using any communication method, whether wired or wireless, such as Ethernet®, Wi-Fi®, or Bluetooth®. Furthermore, multiple of these communication methods may be used. Note that connection refers to a state in which data can be exchanged, and includes not only cases where different hardware is connected via a wired or wireless communication network, but also cases where virtualized electronic control units implemented on the same hardware are virtually connected to each other.
[0024] The electronic control system S shown in Figure 2 includes an integrated ECU 10a, an external communication ECU 10b, zone ECUs (10c, 10d), and individual ECUs (10e to 10h).
[0025] The integrated ECU 10a is an ECU that has the function of controlling the entire electronic control system S, as well as a gateway function that mediates communication between each ECU 10. The integrated ECU 10a is sometimes called a gateway ECU (G-ECU) or a mobility computer (MC). The integrated ECU 10a may also be a relay device or a gateway device.
[0026] The external communication ECU 10b is an ECU having a communication unit that communicates with an external device located outside the vehicle, for example, an external device 30 in each embodiment. The communication method used by the external communication ECU 10b is either wireless communication or wired communication. For example, it is connected via a communication network using wireless communication methods such as IEEE802.11 (Wi-Fi®), IEEE802.16 (WiMAX®), W-CDMA (Wideband Code Division Multiple Access), HSPA (High Speed Packet Access), LTE (Long Term Evolution), LTE-A (Long Term Evolution Advanced), 4G, 5G, etc. Alternatively, DSRC (Dedicated Short Range Communication) can be used. If the vehicle is parked in a parking lot or housed in a repair shop, a wired communication method can be used instead of wireless communication. For example, a LAN (Local Area Network), the internet, or a fixed telephone line can be used. Furthermore, to implement multiple communication methods, multiple external communication ECUs 10b may be provided. Alternatively, instead of providing external communication ECUs 10b, the integrated ECU 10a may incorporate the functions of the external communication ECUs 10b.
[0027] Zone ECUs (10c, 10d) are gateway-function ECUs appropriately positioned according to the location and function of the individual ECUs described later. For example, Zone ECU 10c is an ECU that has a gateway function to mediate communication between individual ECUs 10e and 10f, located at the front of the vehicle, and other ECUs 10, while Zone ECU 10d is an ECU that has a gateway function to mediate communication between individual ECUs 10g and 10h, located at the rear of the vehicle, and other ECUs 10. Zone ECUs (10c, 10d) are sometimes called domain computers (DCs). Individual ECUs 10e and 10f are connected to Zone ECU 10c via Network 2 (NW2), and individual ECUs 10g and 10h are connected to Zone ECU 10d via Network 3 (NW3).
[0028] Individual ECUs (10e~10h) can be composed of ECUs with any function. Examples include drivetrain electronic control units that control the engine, steering wheel, brakes, etc., vehicle system electronic control units that control meters, power windows, etc., information system electronic control units such as navigation systems, or safety control system electronic control units that prevent collisions with obstacles or pedestrians. Furthermore, the ECUs may not be in parallel, but may be classified as master and slave units. Furthermore, depending on the function implemented by each individual ECU (10e to 10h), necessary sensors may be connected to each individual ECU (10e to 10h). Examples include, but are not limited to, speed sensors, acceleration sensors, angular velocity sensors, temperature sensors, sheet sensors, and voltmeters. In addition, these sensors may be connected to the integrated ECU 10a or zone ECUs (10c, 10d) instead of each individual ECU (10e to 10h).
[0029] Each ECU 10 may be a physically independent electronic control unit, or a virtualized electronic control unit implemented using virtualization technology. Furthermore, if each ECU 10 is implemented on different hardware, they only need to be connected via wired or wireless communication. If multiple virtualized electronic control units are implemented on the same hardware, they only need to be virtually connected to each other.
[0030] The file acquisition device 100, file distribution device 200, and file update device 300 of each embodiment are implemented in each ECU 10. For example, Case 1 shows a case where the external communication ECU 10b is a file acquisition device 100 implementing an OTA client, the integrated ECU 10a is a file distribution device 200 implementing UCMM, and the individual ECUs 10e and 10f are file update devices 300 implementing UCMS. Case 2 also shows a case where the external communication ECU 10b is a file acquisition device 100 implementing an OTA client, the integrated ECU 10a is a file distribution device 200 and a file update device 300 implementing UCMM and UCMS, and the individual ECUs 10g and 10h are file update devices 300 implementing UCMS. Furthermore, Case 3 shows a case where the integrated ECU 10a is an OTA client, a file acquisition device 100, a file distribution device 200, and a file update device 300 that implement UCMM and UCMS, and the individual ECUs 10g and 10h are file update devices 300 that implement UCMS. Thus, the functions of the OTA client, UCMM, and UCMS may be implemented in separate ECUs, as in Case 1, or multiple functions may be implemented in a single ECU, as in Cases 2 and 3. The functions of the OTA client, UCMM, and UCMS will be described later.
[0031] (3) Arrangement of a file acquisition device 100, a file distribution device 200, and a file update device 300, which implement the functions of an OTA client, UCMM, and UCMS. AUTOSAR defines the functions of the OAT client, UCMM, and UCMS for updating the software of each ECU10. The OAT client (corresponding to the "file acquisition unit") is a function that acquires update files for updating the software from an external device. The UCMM (corresponding to the "distribution unit") is a function that distributes the update files acquired by the OTA client to ECUs and other devices that require software updates. The UCMS (corresponding to the "update unit") is a function that performs software updates based on the update files distributed from the UCMM. In other words, a UCMS is provided for each piece of software that is to be updated.
[0032] ECU10 is an ECU based on the Adaptive Platform (AP) in AUTOSAR, a platform that allows for dynamic function expansion. AP is primarily a platform suitable for ECUs used in autonomous driving. ECU10 is also based on the Classic Platform (CP) in AUTOSAR, a platform that optimizes static functions. CP is primarily a platform suitable for ECUs used in vehicle control.
[0033] Figure 3 illustrates variations in the configuration of a file acquisition device 100, a file distribution device 200, and a file update device 300, all of which implement the functions of an OTA client, UCMM, and UCMS. Note that while a UCMS is provided for each software being updated, only one is shown in Figure 3.
[0034] Figure 3(a) shows an example where the functions of the OTA client, UCMM, and UCMS are each implemented by separate ECUs 10. For example, Case 1 in Figure 2 corresponds to this example. Figure 3(b) shows an example where the ECU 10 implementing the OTA client functionality and the ECU 10 implementing the UCMM and UCMS functionality are separate ECUs. For example, this corresponds to the case shown in Case 2 of Figure 2, where the integrated ECU 10a implements UCMS functionality in addition to UCMM functionality in order to update the software within the integrated ECU 10a. Hereafter, the device implementing the UCMM and UCMS functionality will be referred to as File Distribution System 1. Figure 3(c) shows an example where the ECU 10 implementing the OTA client and UCMM functions and the ECU 10 implementing the UCMS functions are separate ECUs. For example, this corresponds to the case where the integrated ECU 10a in Figure 2 has communication functions. Hereafter, the device implementing the OTA client and UCMM functions will be referred to as file distribution system 2. Figure 3(d) shows an example where a single ECU 10 implements the functions of an OTA client, UCMM, and UCMS. For example, as in Case 3 of Figure 3, this corresponds to a case where the integrated ECU 10a has communication functions and also implements the UCMS function in order to update the software within the integrated ECU 10a. Alternatively, this corresponds to a case where the external communication ECU 10b in Figure 2 implements the functions of an OTA client and UCMM, and also implements the UCMS function in order to update the software within the external communication ECU 10b. Hereinafter, the device that implements the functions of an OTA client, UCMM, and UCMS will be referred to as the file distribution system 3.
[0035] (4) Appearance of the apparatus of each embodiment In the following embodiments, a device implementing the functionality of an OTA client is referred to as a file acquisition device 100, a device implementing the functionality of a UCMM is referred to as a file distribution device 200, and a device implementing the functionality of a UCMS is referred to as a file update device 300. Furthermore, as shown in Figures 3(b), (c), and (d), a device implementing two or more of the OTA client, UCMM, and UCMS is referred to as a file distribution system 1 to 3. The file acquisition device 100, file distribution device 200, file update device 300, and file distribution systems 1 to 3 can each take the form of a component, a semi-finished product, or a finished product. Examples of components, semi-finished products, and finished products will be described later.
[0036] Furthermore, the entire system of OTA client, UCMM, and UCMS is sometimes referred to as the file distribution system. Unlike the specific file distribution systems 1-3 described above, the relationship between each function and the device on which that function is implemented is not specified; this file distribution system is a general term for a system that integrates the functions of the OTA client, UCMM, and UCMS.
[0037] 2. Embodiment 1 (1) Configuration of the file acquisition device 100 Referring to Figure 4, the configuration of the file acquisition device 100 of this embodiment will be described. The file acquisition device 100 includes a first communication unit 101, an identification information collection unit 102, a storage unit 103, a determination unit 104, and a second communication unit 105. In subsequent embodiments, the ECU 10 and each ECU 10 will be simply referred to as ECU.
[0038] The first communication unit 101 receives update files for updating software from an external device 30 located outside the electronic control system S, using either wireless or wired communication. The update files received by the first communication unit 101 are used to update the software and applications of the file update devices 300 of each ECU, and may therefore include information that identifies the file update device 300 to be updated. The update files may also be a group of update files containing multiple update files.
[0039] The identification information collection unit 102 collects identification information of the ECU or SoC on which the file distribution device 200, which is directly or indirectly connected to the file acquisition device 100, is implemented. Specifically, it performs a search process to query the file distribution device 200 for information about the file distribution device 200. For example, the identification information collection unit 102 transmits a search signal generated by the identification information collection unit 102 to the file distribution device 200 from the second communication unit 105 (described later), and the second communication unit 105 receives a response signal transmitted from the file distribution device 200 that received the search signal, thereby collecting identification information of the ECU or SoC on which the file distribution device 200 is implemented.
[0040] Figure 5(a) shows an example of identification information for the file distribution device 200. The response signal contains the UCMM name, ECU ID, and SoC ID. For example, UCMM001 indicates that it is implemented in ECU00 and SoC00.
[0041] The storage unit 103 stores the updated files received by the first communication unit 101 and the identification information collected by the identification information collection unit 102. Furthermore, in addition to the identification information of the file distribution device 200 shown in Figure 5(a), the storage unit 103 may also store the identification information of the ECU or SoC on which the file acquisition device 100 itself is implemented, as shown in Figure 5(b).
[0042] The storage unit 103 is a storage device capable of reading or writing various types of information. The storage unit 103 may be either an external storage device (hard disk, USB memory, CD / BD, etc.) or an internal storage device (ROM, RAM, etc.). It may also be a volatile memory such as SRAM or DRAM, or a non-volatile memory such as flash memory or a hard disk. The same applies to the storage unit 203 described later.
[0043] The determination unit 104 determines whether the file distribution device 200 (corresponding to the "distribution unit"), which is the destination of the updated file received by the first communication unit 101 and stored in the storage unit 103, is "located" on the same "SoC" as the file acquisition device 100 (corresponding to the "file acquisition unit"). If the determination unit 104 determines that the file distribution device 200 is "located" on a different "SoC" than the file acquisition device 100, the determination unit 104 instructs the second communication unit 105, described later, to send the update file. If the determination unit 104 determines that the file distribution device 200 is "located" on the same "SoC" as the file acquisition device 100, the determination unit 104 instructs the second communication unit 105, described later, to send storage location information (corresponding to the "first storage location information") indicating the storage location of the update file in the file acquisition device 100. Here, "SoC" refers to an integrated circuit that incorporates a single, unified system. For example, it can be a form in which a processor and memory are mounted on a single circuit board. "Deployment" is a concept that simply means there is a place where the main part of a function is executed, and it also includes implementation.
[0044] An SoC (System on a Chip) is a single chip that integrates a CPU, memory, and, if necessary, a GPU (Graphics Processing Unit) for image processing and a communication module. In particular, in this embodiment, an SoC refers to a system that uses one non-volatile memory with one or more operating systems (OS). In this embodiment, for example, if two operating systems run on one package (i.e., a chip), and each OS manages separate non-volatile memory, then there are two SoCs in one package. When multiple operating systems each manage separate non-volatile memory, this includes cases where the two operating systems do not share a common non-volatile memory and each uses separate non-volatile memory. Also, if two operating systems run on one package, and each OS manages one common non-volatile memory, then there is one SoC in one package. In other words, the number of non-volatile memories corresponds to the number of SoCs, and multiple SoCs are considered different SoCs. However, if one OS manages multiple non-volatile memories, it is exceptionally considered to be one SoC. The above criteria are based on the premise that if the file update device 300 can access update files from other devices, it does not need to send update files, and therefore the file update device 300 and other devices can be evaluated as the same SoC.
[0045] For example, if Figure 5(a) shows the identification information for the file distribution device 200 and Figure 5(b) shows the identification information for the file acquisition device 100, the determination unit 104 instructs the file distribution devices 200 (UCMM002, UCMM003) implemented on SoC01, which is a different SoC from the file acquisition device 100, to send the updated file. The determination unit 104 also instructs the file distribution device 200 (UCMM001) implemented on SoC00, which is the same SoC as the file acquisition device 100, to send storage location information indicating the storage location of the updated file.
[0046] Figure 6 shows an example of storage location information. In this embodiment, the storage location information is the file name of the update file and the path to the storage location where the update file is stored. In the path in Figure 6, ota01 is the path name of the file acquisition device 100, str is the path name of the storage unit 103, and update is the folder name of the storage unit 103 where the update file is stored. Alternatively, instead of the file name and path, the starting address and file size of the updated file in the storage unit 103 may be used as storage location information.
[0047] The second communication unit 105 (corresponding to the "transmission unit") transmits the update file or the storage location information of the update file to the file distribution device 200 based on the instructions of the determination unit 104.
[0048] (2) Configuration of the file distribution device 200 Referring to Figure 7, the configuration of the file distribution device 200 of this embodiment will be described. The file distribution device 200 includes a first communication unit 201, an identification information collection unit 202, a storage unit 203, a determination unit 204, a file processing unit 205, and a second communication unit 206.
[0049] The first communication unit 201 "acquires" an update file or storage location information of the update file (corresponding to "first storage location information") from the file acquisition device 100 using a wireless communication method or a wired communication method, for updating the software. Here, "acquisition" can refer to either the case where the distribution unit receives and acquires a file sent from the file acquisition unit, or the case where the distribution unit accesses the storage unit of the file acquisition unit to acquire the file.
[0050] The identification information collection unit 202 collects identification information of the ECU or SoC on which the file update device 300, which is directly or indirectly connected to the file distribution device 200, is implemented. Specifically, it performs a search process to query the file update device 300 for information about the file update device 300. For example, the identification information collection unit 202 transmits a search signal generated by the identification information collection unit 202 to the file update device 300 from the second communication unit 206 (described later), and the second communication unit 206 receives a response signal transmitted from the file update device 300 that received the search signal, thereby collecting identification information of the ECU or SoC on which the file update device 300 is implemented.
[0051] The timing at which the identification information collection unit 202 collects the identification information of the file update device 300 can be at any time. Preferably, the search process should be performed when a search signal is received from the file acquisition device 100. In this case, the file distribution device 200 may transmit its own identification information to the file acquisition device 100, as well as the identification information of the file update device 300 that it has collected.
[0052] Figure 8(a) shows an example of identification information for the file update device 300. The response signal contains the UCMS name, ECU ID, and SoC ID. For example, UCMS001 indicates that it is implemented in ECU00 and SoC00. Note that in Figure 8(a), the SoC ID is identification information within the ECU, so even if the SoC ID is the same, different ECU IDs indicate different SoCs.
[0053] The storage unit 203 stores the update file or the storage location information of the update file "acquired" by the first communication unit 201, and the identification information collected by the identification information collection unit 202. Depending on the usage and system configuration, the information stored in the storage unit 203 may include only the update file or only the storage location information of the update file. Furthermore, in addition to the identification information of the file update device 300 shown in Figure 8(a), the storage unit 203 may also store identification information of the ECU or SoC on which the file distribution device 200 itself is implemented, as shown in Figure 8(b).
[0054] The determination unit 204 determines whether the file update device 300 (corresponding to the "update unit"), which is the destination for the update file, is "located" on the same "SoC" as the file distribution device 200 (corresponding to the "distribution unit"). If the determination unit 204 determines that the file update device 300 is "located" on a different SoC than the file distribution device 200, the determination unit 204 instructs the second communication unit 206 (described later) to send the update file. If the determination unit 204 determines that the file update device 300 is "located" on the same SoC as the file distribution device 200, the determination unit 204 instructs the second communication unit 206 (described later) to send storage location information indicating the storage location of the update file. Here, "SoC" refers to an integrated circuit that incorporates a single, unified system. For example, it can be a form in which a processor, microcontroller, and memory are mounted on a single circuit board. "Deployment" is a concept that simply means there is a place where the main part of a function is executed, and it also includes implementation.
[0055] For example, if Figure 8(a) is the identification information for the file update device 300 and Figure 8(b) is the identification information for the file distribution device 200, the determination unit 204 instructs the file update devices 300 (UCMS002, UCMS003, UCMS004) implemented on a different SoC than the file distribution device 200 to send the update file. The determination unit 204 also instructs the file update device 300 (UCMS001) implemented on the same SoC as the file distribution device 200 to send storage location information indicating the storage location of the update file.
[0056] However, the storage unit 203 may contain either an updated file or information about the storage location of the updated file in the file acquisition device 100. Furthermore, in each of these cases, there are cases where the updated file is sent to the file update device 300 and cases where the storage location information of the updated file is sent. Therefore, in this embodiment, a file processing unit 205 is provided after the determination unit 204, and the file processing unit 205 gives detailed instructions to the second communication unit 206 according to these cases.
[0057] Figure 9 is a diagram illustrating the instructions given by the file processing unit 205. If the determination unit 204 determines that the file update device 300 is located on the same SoC as the file distribution device 200, the file processing unit 205 determines whether the update file is stored in the storage unit 203. If the update file is stored in the storage unit 203, the second communication unit 206 is instructed to transmit the storage location information of the update file in the storage unit 203 of the file distribution device 200 (corresponding to "second storage location information"). If the update file is not stored in the storage unit 203, but the storage location information of the update file in the storage unit 103 of the file acquisition device 100 (corresponding to "first storage location information") is stored in the storage unit 203, the second communication unit 206 is instructed to transmit this storage location information (corresponding to "first storage location information").
[0058] Figure 10 shows an example of the storage location information to be transmitted. In this embodiment, the storage location information is the file name of the update file and the path to the storage location where the update file is saved. The first row of Figure 10 shows the path used when the update file is stored in the storage unit 203. ucmm001 is the path name of the file distribution device 200, str is the path name of the storage unit 203, and update is the folder name in the storage unit 203 where the update file is stored. The second row of Figure 10 shows the path used when the update file is not stored in the storage unit 203, but is stored in the storage unit 103. ota01 is the path name of the file acquisition device 100, str is the path name of the storage unit 103, and update is the folder name in the storage unit 103 where the update file is stored.
[0059] Returning to Figure 9, if the determination unit 204 determines that the file update device 300 is located on a different SoC than the file distribution device 200, the file processing unit 205 determines whether the update file is stored in the storage unit 203. If an update file is stored in the storage unit 203, the second communication unit 206 is instructed to read the update file from the storage unit 203 of the file distribution device 200 and transmit it. If the update file is not stored in the storage unit 203, and the storage location information of the update file in the storage unit 103 of the file acquisition device 100 (corresponding to "first storage location information") is stored in the storage unit 2003, the second communication unit 206 is instructed to read the update file from the storage location indicated by this storage location information and transmit it.
[0060] In this embodiment, the determination unit 204 makes the determination in the preceding stage and the file processing unit 205 makes the determination in the subsequent stage. However, the determination unit 204 may perform both the determination in the preceding and subsequent stages.
[0061] The second communication unit 206 (corresponding to the "transmission unit") transmits the updated file or information about the storage location of the updated file to the file update device 300 based on instructions from the file processing unit 205.
[0062] Furthermore, information that distinguishes between a file update device 300 that sent an update file and a file update device 300 that sent storage location information without sending an update file may be stored in the storage unit 203. A specific example of using this information will be described in Embodiment 3.
[0063] (3) Configuration of the file update device 300 Referring to Figure 11, the configuration of the file update device 300 in this embodiment will be described. The file distribution update device 300 includes a communication unit 301, a storage unit 302, and a software update unit 303.
[0064] The communication unit 301 receives update files or storage location information for update files (corresponding to "storage location information") from the file distribution device (corresponding to the "distribution unit") 200 using a wireless communication method or a wired communication method. Furthermore, the communication unit 301 receives a search signal from the file distribution device 200, reads the identification information of the file update device 300 from the storage unit 302 (described later), and transmits the read identification information to the file distribution device 200 as a response signal.
[0065] The storage unit 302 stores the updated file or the storage location information of the updated file received by the communication unit 301. The storage location information is the storage location information of the updated file in the storage unit 103 of the file acquisition device 100 (corresponding to the "first storage location information"), or the storage location information of the updated file in the storage unit 203 of the file distribution device 200 (corresponding to the "second storage location information").
[0066] Furthermore, the storage unit 302 stores identification information for the file update device 300. This identification information includes the UCMS name, ECU ID, and SoC ID. Figure 12 shows an example of the identification information for the file update device 300. In this example, it is shown that UCMS001 is implemented in ECU00 and SoC00.
[0067] When the communication unit 301 receives an update file, the software update unit 303 reads the update file from the storage unit 302 and updates the software using the read update file. Furthermore, when the communication unit 301 receives storage location information for an update file, the software update unit 303 reads the update file from the storage location indicated by the storage location information stored in the storage unit 302 and updates the software using the read update file.
[0068] (4) Operation of each device First, with reference to Figure 13, an overview of the operation of each device in this embodiment, configured as described above, will be explained. Figure 13 shows the ECU and SoC on which the file acquisition device 100, file distribution device 200, and file update device 300 are implemented. The ECU and SoC on which each device is implemented are the examples shown in Figures 5, 8, and 12. In the figure, F represents the update file stored in each device. The solid arrows in the figure indicate the operation of reading update files across devices.
[0069] Figure 13(a) shows an example where the file acquisition device 100 (OTA01) and the file distribution device 200 (UCMM001) are implemented on the same SoC (SoC00). The file update device 300 is shown as an example of a device (UCMS001) implemented on the same ECU (ECU00) and the same SoC (SoC00) as the file distribution device 200, a device (UCMS002) implemented on the same ECU (ECU00) but on a different SoC (SoC01), and a device (UCMS004) implemented on a different ECU (ECU01) and a different SoC (SoC00).
[0070] In the case of Figure 13(a), since the file distribution device 200 (UCMM001) is implemented on the same SoC as the file acquisition device 100 (OTA01), the file acquisition device 100 (OTA01) transmits the storage location information of the updated file (corresponding to "first storage location information") to the file distribution device 200 (UCMM001), and the file distribution device 200 (UCMM001) saves the received storage location information. The file distribution device 200 (UCMM001) reads the update file from the storage location indicated by the storage location information, in this case from the file acquisition device 100 (OTA01), to the file update devices 300 (UCMS002, UCMS004), which are implemented on a different SoC than the file distribution device 200 (UCMM001), and transmits the read update file. The file update devices 300 (UCMS002, UCMS004), which receive the update file, save the received update file. The file distribution device 200 (UCMM001) also transmits the storage location information of the update file (corresponding to "first storage location information") to the file update device 300 (UCMS001), which is implemented on the same SoC as the file distribution device 200 (UCMM001). The file update devices 300 (UCMS002, UCMS004) then perform a software update using the saved update file. Furthermore, the file update device 300 (UCMS001) reads the update file from the storage location indicated by the storage location information, in this case from the file acquisition device 100 (OTA01), and uses the read update file to update the software.
[0071] In the case of Figure 13(b), since the file distribution device 200 (UCMM002) is implemented on a different SoC than the file acquisition device 100 (OTA01), the file acquisition device 100 (OTA01) sends the updated file to the file distribution device 200 (UCMM002), and the file distribution device 200 (UCMM002) saves the received updated file. The file distribution device 200 (UCMM002) sends an update file to the file update devices 300 (UCMS003, UCMS004), which are implemented on a different SoC than the file distribution device 200 (UCMM002). The file update devices 300 (UCMS003, UCMS004), upon receiving the update file, save it. The file distribution device 200 (UCMM002) also sends storage location information for the update file (corresponding to "second storage location information") to the file update device 300 (UCMS002), which is implemented on the same SoC as the file distribution device 200 (UCMM002). The file update devices 300 (UCMS003, UCMS004) then perform the software update using the saved update file. The file update device 300 (UCMS002) also reads the update file from the storage location indicated by the storage location information, in this case from the file distribution device 200 (UCMM002), and performs the software update using the read update file.
[0072] Next, the operation of the file acquisition device 100 will be explained with reference to Figure 14. Figure 14 not only shows the file acquisition method performed by the file acquisition device 100, but also the processing steps of a file acquisition program that can be executed by the file acquisition device 100. Furthermore, these processes are not limited to the order shown in Figure 14. That is, the order can be changed unless there are constraints such as a relationship where one step utilizes the result of the preceding step. The same applies to other embodiments.
[0073] The first communication unit 101 of the file acquisition device 100 receives an update file for updating the software from the external device 30 using either wireless communication or wired communication (S101). The update file is stored in the storage unit 103. The identification information collection unit 102 collects identification information of the ECU or SoC on which the file distribution device 200, which is directly or indirectly connected to the file acquisition device 100, is implemented (S102). The identification information is stored in the storage unit 103. The determination unit 104 determines whether the file distribution device 200, which is the destination for the updated file, is located on the same SoC as the file acquisition device 100 (S103). If the determination unit 104 determines that the file distribution device 200 is located on a different SoC than the file acquisition device 100, the determination unit 104 instructs the second communication unit 105 to send the update file, and the second communication unit 106 sends the update file to the file distribution device 200 (S104). If the determination unit 104 determines that the file distribution device 200 is located on the same SoC as the file acquisition device 100, the determination unit 104 instructs the second communication unit 105 to transmit storage location information indicating the storage location of the updated file, and the second communication unit 105 transmits the storage location information (S105). The above operations are repeated for the number of times equal to the number of identification pieces of the file distribution device 200 obtained in S102.
[0074] Next, the operation of the file distribution device 200 will be described with reference to Figure 15. Figure 15 not only shows the file distribution method performed by the file distribution device 200, but also the processing steps of a file distribution program that can be executed by the file distribution device 200. Furthermore, these processes are not limited to the order shown in Figure 15. That is, the order may be changed unless there are constraints such as a relationship where one step utilizes the result of the preceding step. The same applies to other embodiments.
[0075] The first communication unit 201 of the file distribution device 200 "acquires" an update file or storage location information of the update file from the file acquisition device 100 using a wireless communication method or a wired communication method (S201). The update file or storage location information is stored in the storage unit 203. The identification information collection unit 202 collects identification information of ECUs and SoCs on which file update devices 300, which are directly or indirectly connected to the file distribution device 200, are implemented (S202). The identification information is stored in the storage unit 203. The determination unit 204 determines whether the file update device 300, which is the destination for the update file, is located on the same SoC as the file distribution device 200 (S203). If the determination unit 204 determines that the file update device 300 is located on a different SoC than the file distribution device 200, the determination unit 204 instructs the second communication unit 206 to send the update file, and the second communication unit 206 sends the update file to the file update device 300 (S204). If the determination unit 204 determines that the file update device 300 is located on the same SoC as the file distribution device 200, the determination unit 204 instructs the second communication unit 206 to transmit storage location information indicating the storage location of the update file, and the second communication unit 206 transmits the storage location information (S205). The above operations are repeated for the number of times equal to the number of identification pieces of the file update device 300 obtained in S202.
[0076] (5) Summary As described above, with the file distribution device 200 of this embodiment, if the file update device 300 is located on a different SoC than the file distribution device 200, the update file is sent to the file update device 300. If it is located on the same SoC, the storage location information of the update file is sent. Therefore, if they are on the same SoC, the update file can be shared, and it is possible to avoid storing multiple identical update files on the same SoC. As a result, time, CPU, and memory resources that would otherwise be used to copy the update file can be saved. Similar effects can be expected for the file acquisition device 100, the file update device 300, and the entire file distribution system. According to the file distribution device 200 of this embodiment, by further providing a file processing unit 205, appropriate processing can be performed for all combinations of cases where an updated file is stored in the storage unit 203 and where the storage location information of the updated file is stored in the file acquisition device 100, respectively, when an updated file is sent to the file update device 300 and when the storage location information of the updated file is sent. According to the file distribution device 200 of this embodiment, identification information of the SoC on which the file update device 300 is located can be collected in advance and used for determination by the determination unit 204, so that the determination by the determination unit 204 can be performed quickly.
[0077] 3. Embodiment 2 In Embodiment 1, when the file update device 300 is located on the same SoC as the file distribution device 200, it transmits storage location information instead of the update file. However, even when located on the same SoC, if the virtual machines are different, it may not be possible to directly read the update file using the storage location information. Therefore, in this embodiment, a file distribution device, etc., that further determines whether the virtual machines are different and performs appropriate processing according to the determination result will be described. In this embodiment, only the differences from Embodiment 1 will be described. For configurations and operations that are the same as in Embodiment 1, the description and drawings of Embodiment 1 will be referenced as the configurations and operations of this embodiment.
[0078] In the electronic control system S, a virtual machine, which is a virtualized electronic control unit, can be used as the ECU 20. In other words, the functions of the OTA client, UCMM, and UCMS can each be implemented using a virtual machine. Therefore, in this embodiment, we will describe the case in which a virtual machine is used for the file distribution device 200 and file update device 300 of Embodiment 1.
[0079] (1) Configuration of the file acquisition device 100 Since this is the same as Embodiment 1, the description and drawings of Embodiment 1 will be referenced.
[0080] (2) Configuration of the file distribution device 200 Since the configuration of the file distribution device 200 in this embodiment is the same as in Figure 7, only the configuration specific to this embodiment will be explained using Figure 7.
[0081] The identification information acquisition unit 202 collects identification information of the ECU or SoC on which the file update device 300 is implemented, as well as identification information of the virtual machine.
[0082] Figure 16(a) shows an example of identification information for the file update device 300. The response signal contains the UCMS name, ECU ID, SoC ID, and VM ID. For example, UCMS101 indicates that it is implemented in ECU00, SoC00, and VM01. Furthermore, in addition to the identification information of the file update device 300 shown in Figure 16(a), the storage unit 203 also stores the identification information of the ECU, SoC, and virtual machine on which the file distribution device 200 itself is implemented, as shown in Figure 16(b).
[0083] If the determination unit 204 determines that the file update device 300 is located on the same SoC as the file distribution unit 200, it further determines whether the file update device 300 is located on the same "virtual machine" as the file distribution device 200. If the determination unit 204 determines that the file update device 300 is located in the same "virtual machine" as the file distribution device 200, the determination unit 204 instructs the second communication unit 206 to transmit storage location information. If the determination unit 204 determines that the file update device 300 is located in a different "virtual machine" than the file distribution device 200, the determination unit 204 instructs the second communication unit 206 to transmit storage location information and identification information of the virtual machine in which the file distribution device 200 is located. Furthermore, file transfer protocol information may also be transmitted. Here, "virtual machine" refers to a virtual computer created using software such as a hypervisor.
[0084] Examples of file transfer protocols include SCP (Secure Copy Protocol) and SFTP (SSH File Transfer Protocol). Alternatively, the NFS (Network File System) protocol can also be used. Furthermore, in this embodiment, the storage location information includes the file name of the update file and the path to the storage location where the update file is saved, but the storage location also includes the ID of the virtual machine.
[0085] For example, if Figure 16(a) is the identification information for the file update device 300 and Figure 16(b) is the identification information for the file distribution device 200, the determination unit 204 instructs the file update device 300 (UCMS101), which is implemented in the same virtual machine as the file distribution device 200, to transmit storage location information indicating the storage location of the updated file. The determination unit 204 also instructs the file update device 300 (UCMS102), which is implemented in a different virtual machine than the file distribution device 200, to transmit storage location information.
[0086] The second communication unit 206 transmits storage location information, or storage location information plus file transfer protocol information, to the file update device 300 based on instructions from the determination unit 204.
[0087] (3) Configuration of the file update device 300 Since this is the same as Embodiment 1, the description and drawings of Embodiment 1 will be referenced.
[0088] (4) Operation of each device First, with reference to Figure 17, an overview of the operation of each device in this embodiment configured as described above will be explained. Figure 17 shows the ECU, SoC, and virtual machine on which the file acquisition device 100, file distribution device 200, and file update device 300 are implemented. The ECU, SoC, and virtual machine on which each device is implemented are the same as those shown in Figure 16. In the figure, solid arrows indicate the operation of reading updated files, and dotted arrows indicate the operation of reading updated files using a file transfer protocol.
[0089] Figure 17 shows an example where the file acquisition device 100 (OTA101), file distribution device 200 (UCMM10), and file update devices 300 (UCMS101, UCMS102) are implemented on the same ECU (ECU00) and SoC (SoC00). The file update device 300 is shown as an example where it is implemented on the same virtual machine (VM01) as the file distribution device 200 (UCMS101), and on a different virtual machine (VM02) (UCMS102).
[0090] In the case of Figure 17, the file update device 300 (UCMS101) is implemented in the same virtual machine as the file distribution device 200 (UCMM101). Therefore, the file distribution device 200 (UCMM101) sends information about the storage location of the update file to the file update device 300 (UCMS101), and the file update device 300 (UCMS101) saves the received storage location information. The file update device 300 (UCMS101) reads the update file from the storage location indicated by the storage location information, in this case from the file distribution device 200 (UCMM101), and uses the read update file to update the software.
[0091] Furthermore, since the file update device 300 (UCMS102) is implemented on a different virtual machine than the file distribution device 200 (UCMM101), the file distribution device 200 (UCMM101) transmits information about the storage location of the update file and the file transfer protocol information to the file update device 300 (UCMS102), and the file update device 300 (UCMS102) stores the received storage location information and the file transfer protocol information. The file update device 300 (UCMS102) reads the update file using the file transfer protocol from the storage location indicated by the storage location information, in this case the storage location of the file distribution device 200 (UCMM101), and updates the software using the read update file.
[0092] Next, the operation of the file distribution device 200 will be explained with reference to Figure 18. Note that for flows with the same step numbers as in Figure 15, the explanation in Figure 15 will be referenced and omitted. The determination unit 204 determines whether the file update device 300, which is the destination for the update file, is located on the same virtual machine as the file distribution device 200 (S211). If the determination unit 204 determines that the file update device 300 is located on the same virtual machine as the file distribution device 200, the determination unit 204 instructs the second communication unit 206 to transmit storage location information, and the second communication unit 206 transmits the storage location information to the file update device 300 (S212). If the determination unit 204 determines that the file update device 300 is located on a different virtual machine than the file distribution device 200, the determination unit 204 instructs the second communication unit 206 to transmit storage location information and the transfer protocol for the updated file, and the second communication unit 206 transmits the storage location information and the transfer protocol for the updated file (S213).
[0093] (5) Summary As described above, according to the file distribution device 200 of this embodiment, if the file update device 300 is located on the same virtual machine as the file distribution device 200, storage location information is sent to the file update device 300. If it is located on a different virtual machine, in addition to storage location information, the update file transfer protocol is sent. Therefore, even if they are on different virtual machines, as long as they are on the same SoC, the update files can be shared, and it is possible to avoid storing multiple identical update files on the same SoC. As a result, time, CPU, and memory resources that would otherwise be lost due to copying update files can be saved.
[0094] 4. Embodiment 3 In Embodiment 1, if the file update device 300 is located on a different SoC than the file distribution device 200, it sends the update file. However, even if they are located on different SoCs, a file update device 300 located on the same SoC as a file update device that has already sent an update file can retrieve the update file from the file update device. Therefore, in this embodiment, we will describe a file distribution device, etc., that performs further determination regarding the SoC on which the file update device 300 is located and performs appropriate processing according to the determination result. In this embodiment, only the differences from Embodiment 1 will be described. For configurations and operations that are the same as in Embodiment 1, the description and drawings of Embodiment 1 will be referenced as the configurations and operations of this embodiment.
[0095] (1) Configuration of the file acquisition device 100 Since this is the same as Embodiment 1, the description and drawings of Embodiment 1 will be referenced.
[0096] (2) Configuration of the file distribution device 200 Since the configuration of the file distribution device 200 in this embodiment is the same as in Figure 7, only the configuration specific to this embodiment will be explained using Figure 7.
[0097] The identification information acquisition unit 202 collects identification information of the ECU or SoC on which the file update device 300 is implemented.
[0098] Figure 19(a) shows an example of identification information for the file update device 300. The response signal contains the UCMS name, ECU ID, and SoC ID. For example, UCMS201 indicates that it is implemented in ECU11 and SoC11. Furthermore, in addition to the identification information of the file update device 300 shown in Figure 19(a), the storage unit 203 also stores the identification information of the ECU and SoC on which the file distribution device 200 itself is implemented, as shown in Figure 19(b).
[0099] In this embodiment, the identification information of the file update devices 300 is further supplemented with information indicating whether or not an update file has already been sent to each file update device 300, and this information is stored in the storage unit 203. For example, when an update file is sent to a file update device 300, that file update device 300 is defined as a "sent file update device" (corresponding to a "sent update unit"), and a sent flag indicating that it is a sent file update device is recorded.
[0100] If the determination unit 204 determines that the file update device 300 is located on a different SoC than the file distribution device 200, the determination unit 204 further determines whether the file update device 300 is located on the same SoC as the transmitted file update device that has already sent updated files from the file distribution device 200. If the determination unit 204 determines that the file update device 300 is located on a different SoC than the transmitted file update device, the determination unit 204 instructs the second communication unit 206 to send the update file. If the determination unit 204 determines that the file update device 300 is located on the same SoC as the transmitted file update device, the determination unit 204 instructs the second communication unit 206 to send file transmission information. File transmission information includes, for example, identification information for the file update device that has sent the file.
[0101] For example, let's consider the case where Figure 19(a) shows the identification information of the file update device 300, and Figure 19(b) shows the identification information of the file distribution device 200.
[0102] The determination unit 204 determines that the file update device 300 (UCMS201) is located on the same SoC as the file distribution device 200 (UCMM201). In this case, the determination unit 204 instructs the second communication unit 206 to transmit storage location information, but since no updated file has been transmitted, the transmitted flag for the file update device 300 (UCMS201) is not recorded.
[0103] The determination unit 204 determines that the file update device 300 (UCMS202) is located on a different SoC than the file distribution device 200 (UCMM201). In this case, the determination unit 204 further determines whether the file update device 300 (UCMS202) is located on the same SoC as the transmitted file update device that has already sent an update file from the file distribution device 200. In the case of Figure 19, at this point, no update file has yet been sent to any of the file update devices 300 located on SoC 12, so the determination unit 204 instructs the second communication unit 206 to send the update file and records a transmitted flag indicating that the file update device 300 (UCMS202) is a transmitted file update device.
[0104] The determination unit 204 determines that the file update device 300 (UCMS203) is located on a different SoC than the file distribution device 200 (UCMM201). In this case, the determination unit 204 further determines whether the file update device 300 (UCMS203) is located on the same SoC as the transmitted file update device that has already sent an update file from the file distribution device 200. In the case of Figure 19, since an update file has already been sent to the file update device 300 (UCMS202) located on SoC 12, the determination unit 204 instructs the second communication unit 206 to send file transmission information, but since no update file is sent, the transmitted flag for the file update device 300 (UCMS203) is not recorded.
[0105] The second communication unit 206 transmits the updated file or file transmission information to the file update device 300 based on the instructions of the determination unit 204.
[0106] (3) Configuration of the file update device 300 Since this is the same as Embodiment 1, the description and drawings of Embodiment 1 will be referenced.
[0107] (4) Operation of each device First, with reference to Figure 20, an overview of the operation of each device in this embodiment configured as described above will be explained. Figure 20 shows the ECU and SoC on which the file acquisition device 100, file distribution device 200, and file update device 300 are implemented. The ECU and SoC on which each device is implemented are the examples shown in Figure 19.
[0108] Figure 20 shows an example where the file acquisition device 100 (OTA101), file distribution device 200 (UCMM201), and file update devices 300 (UCMS201, UCMS202, UCMS203) are implemented on the same ECU (ECU11). The file update devices 300 include examples of devices implemented on the same SoC (SoC11) as the file distribution device 200 (UCMS201) and devices implemented on different SoCs (SoC12) (UCMS202, UCMS203).
[0109] In the case of Figure 20, the file update device 300 (UCMS201) is implemented on the same SoC as the file distribution device 200 (UCMM201). Therefore, the file distribution device 200 (UCMM201) sends the storage location information of the update file to the file update device 300 (UCMS201) and does not record a transmitted flag. The file update device 300 (UCMS201) saves the received storage location information, reads the update file from the storage location indicated by the storage location information, in this case from the file distribution device 200 (UCMM201), and performs a software update using the read update file.
[0110] The file update device 300 (UCMS202) is implemented on a different SoC than the file distribution device 200 (UCMM201), and there are no file update devices 300 implemented on the same SoC as the file distribution device 200 (UCMS202) that have already received the update file at this point. Therefore, the file distribution device 200 (UCMM201) sends the update file to the file update device 300 (UCMS202). The file update device 300 (UCMS202) saves the received update file and uses the update file to update the software.
[0111] The file update device 300 (UCMS203) is implemented on a different SoC than the file distribution device 200 (UCMM201), and there is another file update device 300 (UCMS202) that is implemented on the same SoC as the file distribution device 200 (UCMS203) and has already received the update file. Therefore, the file distribution device 200 (UCMM201) sends file transmission information to the file update device 300 (UCMS203). The file update device 300 (UCMS203) uses the identification information of the file update device 300 (UCMS202) contained in the received file transmission information to read the update file from the file update device 300 (UCMS202), and uses the read update file to update the software.
[0112] Next, the operation of the file distribution device 200 will be explained with reference to Figure 21. Note that for flows with the same step numbers as in Figure 15, the explanation in Figure 15 will be referenced and omitted. The determination unit 204 further determines whether the file update device 300 is located on the same SoC as the transmitted file update device that has already sent an updated file from the file distribution device 200 (S221). If the determination unit 204 determines that the file update device 300 is located on a different SoC than the file update device that has already transmitted the file, the determination unit 204 instructs the second communication unit 206 to send the update file, and the second communication unit 206 sends the update file to the file update device 300 (S222). If the determination unit 204 determines that the file update device 300 is located on the same SoC as the file update device that has already transmitted the file, the determination unit 204 instructs the second communication unit 206 to transmit file transmission information, and the second communication unit 206 transmits the file transmission information to the file update device 300 (S223).
[0113] Although this embodiment is a modification of Embodiment 1, it may also be combined with Embodiment 2. In that case, if the determination unit 204 determines that the file update device 300 is located on the same SoC as the file distribution device 200, it will perform the processing of Embodiment 2, and if it determines that the file update device 300 is located on a different SoC than the file distribution device 200, it will perform the processing of Embodiment 3.
[0114] (5) Summary As described above, according to the file distribution device 200 of this embodiment, if the file update device 300 is located on a different SoC than the file update device that has already sent the file, it sends the updated file. If it is located on the same SoC, it sends file transmission information without sending the updated file. This avoids storing multiple identical updated files within the same SoC. As a result, time, CPU, and memory resources that would otherwise be lost due to copying the updated file can be saved.
[0115] 6. Summary The features of the file distribution device, etc., in each embodiment (including modified examples; the same applies hereinafter) have been described above.
[0116] The terms used in each embodiment are illustrative and may be replaced with synonymous terms or terms that include synonymous functions.
[0117] The block diagram used in the description of the embodiment classifies and organizes the configuration of the device by function. Each block representing a function can be realized by any combination of hardware or software. Furthermore, since it represents a function, such a block diagram can also be understood as a disclosure of an invention of a method executed by the device, and an invention of a program that can be executed by the device and causes the device to perform a predetermined process.
[0118] The functional blocks that can be understood as processes, flows, and methods described in each embodiment may be reordered, unless there are constraints such as a relationship where one step utilizes the results of other preceding steps.
[0119] The terms "first," "second," through "nth" (where N is an integer) used in each embodiment and in the claims are used to distinguish between two or more configurations or methods of the same kind, and do not imply any order or hierarchy.
[0120] Each embodiment is based on a system and device for use in a vehicle, but unless otherwise specifically limited by the claims, the present invention also includes dedicated or general-purpose systems and devices other than those for use in vehicles.
[0121] In each embodiment, the description was based on the premise that the device disclosed in each embodiment is mounted on a vehicle, but it may also be based on the premise that it is carried by a pedestrian.
[0122] Examples of the system or apparatus configurations of the present invention and each embodiment include the following: Examples of component forms include semiconductor elements, electronic circuits, modules, and microcomputers. Examples of semi-finished products include electronic control units (ECUs) and system boards. Examples of finished products include mobile phones, smartphones, tablets, personal computers (PCs), workstations, and servers. Other devices with communication capabilities include, for example, video cameras, still cameras, and car navigation systems.
[0123] Each embodiment of the device may be modified to include necessary functions such as an antenna or a communication interface.
[0124] The devices of the present invention and each embodiment can be used in terminal-side devices and server-side devices to provide various services. In connection with the provision of these services, the devices of the present invention will be used, the methods of the present invention will be used, and / or the programs of the present invention will be executed. In other words, by implementing the present invention, value will be provided through various services that exceed the value of the devices and programs of the present invention themselves.
[0125] The present invention can be realized not only with dedicated hardware having the configuration and functions described in each embodiment, but also as a combination of a program for realizing the present invention recorded on a recording medium such as memory or a hard disk, and general-purpose hardware having a processor and memory capable of executing said program.
[0126] The program of the present invention may be stored in a non-transitional tangible recording medium (for example, an external storage device (hard disk, USB memory, CD / BD, etc.) or an internal storage device (RAM, ROM, etc.)). Furthermore, the program of the present invention can be provided via a non-transitional tangible recording medium, or without a non-transitional tangible recording medium, using a communication line from a server or the like. This allows the recipient of the program to always be provided with the latest functionality through program upgrades.
[0127] In this disclosure or claims, the term "processor" means one or more hardware processors configured to execute processing defined by computer program code (i.e., one or more instructions of a computer program) contained in a computer program by reading the computer program code each time. In other words, a "processor" is a hardware device that executes one or more programmed processes. Therefore, computer program code can also be said to be software that can define the processing of the processor according to its content. A "processor" can be a general-purpose or specific-purpose processor, and may be, but is not limited to, a CPU, microprocessor, GPU, and DFP (Data Flow Processor). In this disclosure or claims, the term “memory” means one or more hardware memories that are non-transitional tangible recording media configured to record computer program code and / or data in a manner accessible from a processor. “Memory” can be implemented by memory technology such as SRAM, SDRAM, non-volatile / flash type memory, or other types of memory. The computer program code that constitutes the program is recorded in memory and executed by a processor, thereby enabling the processor to perform the various functions described above. In this disclosure or claims, the term “circuit” refers to one or more logic circuits as hardware, configured to perform specific processing defined based on a pre-designed circuit configuration. In other words (and, in contrast to “processor”), “circuit” in this disclosure or claims refers to a hardware device that performs specific processing based on a circuit configuration, rather than processing defined by software such as the computer program code described above. For example, “circuit” may include custom ICs such as ASICs (Application Specific Integrated Circuits) and FPGAs (Field Programmable Gate Arrays) designed with a Hardware Description Language (HDL). That is, “circuit” in this disclosure or claims includes all hardware circuits except for the processor described above, which performs processing by reading computer program code. In this disclosure or claims, the expression "at least one of a circuit and a processor" should be interpreted as a disjunctive (logical OR) and not as "at least one circuit and at least one processor." Therefore, in this disclosure or claims, "at least one of a circuit and a processor causes the file distribution device, etc. to perform functions" includes the case where only the circuit causes the file distribution device, etc. to perform all functions. Furthermore, "at least one of a circuit and a processor causes the file distribution device, etc. to perform functions" includes the case where only the processor causes the file distribution device, etc. to perform all functions. Moreover, "at least one of a circuit and a processor causes the file distribution device, etc. to perform functions" includes the case where the circuit causes the file distribution device, etc. to perform some functions and the processor causes the file distribution device, etc. to perform the remaining functions. In the last example, for example, if the file distribution device, etc. performs functions A to C, functions A and B may be implemented by the circuit, and the remaining function C may be implemented by the processor. [Industrial applicability]
[0128] The file distribution device and the like of the present invention are primarily intended for devices mounted in automobiles, but may also be intended for ordinary devices not mounted in automobiles. [Explanation of Symbols]
[0129] 100 File acquisition device, 200 File distribution device, 300 File update device, 10 ECU, 30 External devices, 101, 201 First communication unit, 102, 202 Identification information collection unit, 103, 203 Storage unit, 104, 204 Determination unit, 205 File processing unit, 105, 206 Second communication unit
Claims
1. A file distribution system comprising: a file acquisition unit that acquires files for updating software; a distribution unit that distributes the files for updating the software; and an update unit that updates the software based on the files distributed from the distribution unit, wherein the file distribution device comprises at least the distribution unit, The aforementioned distribution unit, Storage section (203), A determination unit (204) determines whether the update unit, which is the destination of the file, is located on the same system-on-chip (SoC) as the distribution unit, The system includes a transmission unit (206) that transmits the aforementioned file or storage location information indicating the storage location of the aforementioned file to the update unit, If the determination unit determines that the update unit is located on a different SoC than the distribution unit, the transmission unit transmits the file to the update unit. If the determination unit determines that the update unit is located on the same SoC as the distribution unit, the transmission unit transmits the storage location information to the update unit. File distribution device (200).
2. If the determination unit determines that the update unit is located on the same SoC as the distribution unit, the determination unit further determines whether the update unit is located on the same virtual machine as the distribution unit. If the determination unit determines that the update unit is located on the same virtual machine as the distribution unit, the transmission unit transmits the storage location information to the update unit. If the determination unit determines that the update unit is located on a different virtual machine than the distribution unit, the transmission unit transmits the storage location information and the identification information of the virtual machine on which the distribution unit is located to the update unit. The file distribution device according to claim 1.
3. If the determination unit determines that the update unit is located in a different SoC than the distribution unit, the determination unit further determines whether the update unit is located in the same SoC as the transmitted update unit that has already sent the file from the distribution unit. If the determination unit determines that the update unit is located on a different SoC than the transmitted update unit, the transmission unit transmits the file to the update unit. If the determination unit determines that the update unit is located on the same SoC as the transmitted update unit, the transmission unit transmits file transmission information to the update unit indicating that the file has already been sent to the transmitted update unit. The file distribution device according to claim 1.
4. When the determination unit determines that the update unit is located on the same SoC as the distribution unit, If the file is stored in the storage unit, the transmission unit transmits a second storage location information indicating the storage location of the file in the distribution unit as the storage location information. If the first storage location information indicating the storage location of the file in the file acquisition unit is stored in the storage unit, the transmission unit transmits the first storage location information as the storage location information. The file distribution device according to claim 1 or 2.
5. If the determination unit determines that the update unit is located on a different SoC than the distribution unit, If the file is stored in the storage unit, the transmission unit transmits the file read from the storage unit. If a first storage location information indicating the storage location of the file in the file acquisition unit is stored in the storage unit, the transmission unit transmits the file read from the storage location indicated by the first storage location information of the file acquisition unit. The file distribution device according to claim 1 or 3.
6. The distribution unit includes an identification information collection unit (202) that collects identification information of the SoC in which the update unit is located from the update unit, The determination unit performs a determination using the identification information collected by the identification information collection unit. The file distribution device according to claim 1.
7. The distribution unit includes an identification information collection unit (202) that collects identification information of the SoC and virtual machine on which the update unit is located from the update unit. The determination unit performs a determination using the identification information collected by the identification information collection unit. The file distribution device according to claim 2.
8. When the transmission unit transmits the file to the update unit, the update unit, which is the destination of the file, is saved in the storage unit as a transmitted update unit. The file distribution device according to claim 1.
9. A file distribution system comprising: a file acquisition unit that acquires files for updating software; a distribution unit that distributes the files for updating the software; and an update unit that updates the software based on the files distributed from the distribution unit, wherein the file acquisition device comprises at least the file acquisition unit, The aforementioned file acquisition unit, A storage unit (103) for storing the file received from an external device, A determination unit (104) determines whether the distribution unit, which is the destination of the file, is located on the same system-on-chip (SoC) as the file acquisition unit, The system includes a transmission unit (105) that transmits to the distribution unit first storage location information indicating the storage location of the file or the file in the file acquisition unit, If the determination unit determines that the distribution unit is located on a different SoC than the file acquisition unit, the transmission unit transmits the file to the distribution unit. If the determination unit determines that the distribution unit is located on the same SoC as the file acquisition unit, the transmission unit transmits the first storage location information to the distribution unit. File acquisition device (100).
10. The file distribution device is mounted on a mobile device. The file distribution device according to claim 1.
11. The file acquisition device is mounted on a mobile device. The file acquisition device according to claim 9.
12. A file distribution system comprising: a file acquisition unit that acquires files for updating software; a distribution unit that distributes the files for updating the software; and an update unit that updates the software based on the files distributed from the distribution unit, wherein the file distribution system comprises at least the distribution unit and the update unit, The aforementioned distribution unit, Storage section (203), A determination unit (204) determines whether the update unit, which is the destination of the file, is located on the same system-on-chip (SoC) as the distribution unit, The system includes a transmission unit (206) that transmits the aforementioned file or storage location information indicating the storage location of the aforementioned file to the update unit, If the determination unit determines that the update unit is located on a different SoC than the distribution unit, the transmission unit transmits the file to the update unit. If the determination unit determines that the update unit is located on the same SoC as the distribution unit, the transmission unit transmits the storage location information to the update unit. The aforementioned update unit is When the aforementioned file is received from the distribution unit, the software is updated using the aforementioned file. When the storage location information is received from the distribution unit, the software is updated by reading the file from the storage location indicated by the storage location information. File distribution system (1).
13. A file distribution system comprising: a file acquisition unit that acquires files for updating software; a distribution unit that distributes the files for updating the software; and an update unit that updates the software based on the files distributed from the distribution unit, wherein a file distribution method is performed on a file distribution device having at least the distribution unit, It is determined whether the update unit, which is the destination of the file, is located on the same system-on-chip (SoC) as the distribution unit (S203). If the update unit determines that it is located on a different SoC than the distribution unit, it sends the file to the update unit (S204). If the update unit determines that it is located on the same SoC as the distribution unit, it transmits storage location information indicating the storage location of the file to the update unit (S205). File distribution method.
14. A file distribution system comprising: a file acquisition unit that acquires files for updating software; a distribution unit that distributes the files for updating the software; and an update unit that updates the software based on the files distributed from the distribution unit, wherein the file distribution program is executable on a file distribution device having at least the distribution unit, The file distribution program is It is determined whether the update unit, which is the destination of the file, is located on the same system-on-chip (SoC) as the distribution unit (S203). If the update unit determines that it is located on a different SoC than the distribution unit, it sends the file to the update unit (S204). If the update unit determines that it is located on the same SoC as the distribution unit, it transmits storage location information indicating the storage location of the file to the update unit (S205). The file distribution device is instructed to perform a process that includes the following: File distribution program.
Citation Information
Patent Citations
Electronic control device, software update method, software update program, and electronic control system
JP2022085861A
Electronic control device, software update method, software update program, and electronic control system
JP2022085862A
