Center device and method for distributing data packages

Abstract

To provide a center device that can create a delivery package according to the specification of a master device.SOLUTION: In a center device 1, a package creation server 2 acquires identification information provided to a logic for creating a package that refers to a manifest file registered in a file registration unit 6 and distributes the file to a vehicle. A logic ID management unit 4 is registered with the ID according to an OTA master 12 that receives the distributed package on the side of the vehicle and transfers update data to a target ECU 13. The package creation server 2 acquires information on the OTA master 12 corresponding to the ID from the logic ID management unit 4. When the package creation server 2 acquires the logic corresponding to the ID from the logic ID management unit 4, it creates a package based on the logic.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a center device for managing data to be written to a plurality of electronic control units mounted on a vehicle, and a method for distributing data packages.

Background Art

[0002] In recent years, with the diversification of vehicle control such as driving support functions and autonomous driving functions, the scale of application programs for vehicle control and diagnosis mounted on vehicle electronic control units (hereinafter referred to as ECUs (Electronic Control Units)) has been increasing. Also, with version upgrades due to function improvements, etc., the opportunity to perform so-called reprogramming to rewrite the application program of the ECU is increasing. On the other hand, with the development of communication networks, etc., the technology of connected cars is also spreading. For these reasons, for example, Patent Document 1 discloses a technology for distributing an update program for an ECU from a server to an in-vehicle device by OTA (Over The Air) and rewriting the update program on the vehicle side.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When distributing an update program via OTA, it is necessary to generate a data package for distribution. On the other hand, the vehicle-side system is composed of, for example, a DCM (Data Communication Module) that directly communicates with a center device, a so-called target ECU which is an electronic control device to be rewritten with the update program, and a central ECU which is a master device that transfers the update program received via the DCM to the target ECU. And since the specification of the package depends on the specification of the central ECU, it is necessary to generate the distribution package according to the specification of the central ECU.

[0005] However, conventionally, the specific process of generating a distribution package according to the specification of the central ECU has not been disclosed. The present invention has been made in view of the above circumstances, and an object thereof is to provide a center device capable of generating a distribution package according to the specification of a master device and a method for distributing a data package.

Means for Solving the Problems

[0006] According to the center device described in claim 1, the identification information acquisition unit in the package generation unit refers to the manifest file registered in the file registration unit and acquires the identification information given to the logic for generating the package to be distributed to the vehicle. In the logic identification information registration unit, the identification information is registered according to the specification of the master device that receives the distributed package on the vehicle side and transfers the update data to the electronic control device. The master information acquisition unit acquires the information of the master device corresponding to the identification information from the logic identification information registration unit. When the logic acquisition unit in the package generation unit acquires the logic corresponding to the identification information from the logic identification information registration unit, the package generation unit generates a package based on the logic.

[0007] That is, by registering the manifest file in advance in the file registration unit, the identification information assigned to the logic from the file can be obtained. And once the identification information is obtained, the information and logic of the master device corresponding to the identification information can be obtained. Therefore, the package generation unit can generate a package according to the specifications of the master device based on the obtained logic.

[0008] According to the center device described in claim 2, the identification information acquisition unit acquires the identification information from the manifest file on the condition that the information of the master device cannot be acquired from an external server. That is, when a package generation request occurs, if the necessary information can be obtained from an external server, the package can be generated based on the information obtained from the server. If the necessary information cannot be obtained from the server, the identification information can be acquired from the manifest file as described in claim 1 to generate a package.

[0009] According to the center device described in claim 3, the package generation unit associates the generated package with the information about the master device corresponding to the identification information and transmits it to the package distribution unit. Thereby, the package distribution unit can distribute the package to the vehicle equipped with the master device to be distributed.

Brief Description of Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14A

Figure 14B

Figure 15A

Figure 15B

Figure 16A

Figure 16B

Figure 17A

Figure 17B

Figure 18A

Figure 18B

Figure 19A

Figure 19B

Figure 20A

Figure 20B

Mode for Carrying Out the Invention

[0011] Hereinafter, an embodiment will be described. As shown in FIG. 2, the vehicle-side system 11 includes an OTA master 12 and target ECUs 13. The OTA master 12 is composed of a DCM (Data Communication Module) 12A and a central ECU 12B. The DCM 12A communicates directly with the center device 1 shown in FIG. 1. When the OTA master 12 acquires the distribution package received from the center device 1, it transfers the update data included in the acquired distribution package to each target ECU 13. Hereinafter, the "central ECU" will be referred to as "C-ECU".

[0012] As shown in FIG. 1, the center device 1 of the present embodiment includes a PKG generation server 2 and a distribution server 3. The PKG generation server 2 includes a logic ID management DB 4, a logic management DB 5, and a file registration unit 6. Note that "PKG" means "package" and "DB" means database.

[0013] The PKG generation server 2 generates data packages to be distributed to the vehicle-side system 11, and the generated distribution packages are distributed to the vehicle-side system 11 via the distribution server 3. The format of the distribution packages varies according to the specifications of the C-ECU 12B of each vehicle-side system 11. In this embodiment, the information for generating distribution packages corresponding to the specifications of the C-ECU 12B is referred to as "logic". Note that, hereinafter, the term "vehicle" simply refers to a vehicle equipped with the vehicle-side system 11.

[0014] When a specification change occurs for any of the C-ECU 12B in the OEM back office 7, which is an external server, the OEM back office 7 identifies the ID, which is the identifier of the logic corresponding to the specification, and generates a manifest file including the ID and provides it to the center device 1. The ID, which is the identifier of the logic, is also referred to as logic identification information or logic ID. Note that when a specification change occurs for any of the C-ECU 12B, the back office 7 may identify the logic corresponding to the specification in addition to the logic ID. The PKG generation server 2 registers the provided manifest file in the file registration unit 6. The logic ID is managed in the logic ID management DB 4 together with the information of the corresponding C-ECU 12B, and the logic corresponding to each ID is managed in the logic management DB 5.

[0015] When information on the C-ECU 12B, which is the transmission target of the update data, is input from the distribution server 3, the PKG generation server 2 acquires the logic ID corresponding to the C-ECU 12B from the logic ID management DB 4. Then, when the logic corresponding to the acquired logic ID is acquired from the logic management DB 5, a package is generated according to the logic. The generated package is registered in the package DB 8 and distributed to the vehicle-side system 11; C-ECU 12B that is the transmission target via the distribution server 3.

[0016] In addition, the distribution server 3 is provided with a configuration information DB 9 and an individual vehicle information DB 10. In the configuration information DB 9, regular configuration information is registered as vehicle configuration information for each vehicle type. The regular configuration information is the configuration information of a vehicle authorized by a public institution. The configuration information is identification information regarding the hardware and software of the ECUs mounted on the vehicle, and is an example of vehicle-related information. The configuration information includes identification information of a system configuration composed of a plurality of ECUs and identification information of a vehicle configuration composed of a plurality of systems. Further, vehicle constraint information regarding program update may be registered as the configuration information.

[0017] In the individual vehicle information DB 10, individual vehicle information uploaded from each individual vehicle is registered. The individual vehicle information is the configuration information held by each vehicle at that time. When registering the individual vehicle information uploaded from the vehicle, the individual vehicle information is compared with the configuration information of the same type of vehicle registered in the configuration information DB 9, and when the two do not match, the newer information is overwritten to make the two match, which is called "vehicle configuration information synchronization".

[0018] As shown by an example in FIG. 3, in the logic ID management DB 4, the software version or software ID of each C-ECU 12B is registered as C-ECU information, and the logic ID corresponding to the C-ECU information is registered. In FIG. 4, two C-ECU information "1.0.2" and "1.1.0" with the logic ID being "AAA" are added.

[0019] In the examples shown in FIGS. 3 and 4, the C-ECU information is expressed separated by a period symbol. For example, in "1.0.2", the lowest digit indicates the revision build, the middle digit indicates the minor version, and the highest digit indicates the major version. When the upper digit increases, the lower digits are reset to zero. For example, in "1.0.2", when the middle digit increases from "0" to "1", the lowest digit "2" becomes "0".

[0020] In another example shown in FIG. 5, the C-ECU information is a combination of a plurality of part numbers. For example, an OTA part number, a UCM (Update Configuration Management) part number, a Flashing Adaptor part number, etc. Note that since UCM and Flashing Adaptor are described in AUTOSAR, the details are omitted.

[0021] As shown in FIG. 6, in the logic management DB5, the specifications of the logic corresponding to the logic ID are registered. The logic specification defines the input, processing, and output necessary for generating a data package.

[0022] As shown in FIG. 7, the manifest file includes the data size of the package, the logic ID, campaign information, update information which is information related to reprogramming, synchronization group information, etc.

[0023] Next, the operation of this embodiment will be described. <Preparatory Phase> As shown in FIG. 8, when the registration of the information of the new C-ECU12B is started, the PKG generation server 2 determines whether the specification of the package corresponding to the C-ECU12B is different from the specification of the existing package (S1). If it is the same as the specification of the existing package (NO), the process ends. If it is different from the specification of the existing package (YES), the generation logic of the package corresponding to the new specification is added and an ID is assigned to the logic (S2). Then, the logic ID is associated with the information of the C-ECU12B corresponding to it and added to the logic ID management DB4 (S3). Also, the information of the added logic ID is notified to the OEM back office 7.

[0024] <Judgment Processing Phase> As shown in FIGS. 9 and 10, when there is a package generation request from the distribution server 3, the PKG generation server 2 determines whether it can obtain the information of the corresponding C-ECU 12B from the OEM back office 7 at that time (S11). If the information can be obtained, it proceeds to the judgment processing phase executed according to the information (S18). However, since the content of the judgment processing phase is irrelevant to the gist of this embodiment, the description is omitted. Briefly described, based on the information of the C-ECU 12B, the logic ID is specified by referring to the logic ID management DB 4. Then, referring to the logic management DB 5, a package is generated according to the logic indicated by the logic ID.

[0025] On the other hand, when the information of the corresponding C-ECU 12B cannot be obtained from the back office 7, the PKG generation server 2 obtains the files necessary for generating the package, including the manifest file (S12). Then, when the logic ID information is obtained from the manifest file (S13), a package based on the logic ID is generated (S14). Also, the range of the C-ECU 12B for which the generated package is to be distributed is specified from the logic ID management DB 4 (S15).

[0026] Here, the above-mentioned "range" is the range of the C-ECU 12B associated with the logic, which is indicated by the minimum version of the C-ECU 12B associated with the logic indicated by the ID and the minimum version of the C-ECU 12B associated with the logic after the logic has switched. For example, the versions of the C-ECU 12B adopting the logic ID: AAA are in the range where they are associated, such as 1.0.1, 1.0.2, 1.0.3,....

[0027] For example, in FIG. 3, when the logic ID: AAA is acquired as the logic ID information, "1.0.1" is registered in the logic ID management DB4 as the C-ECU information. This corresponds to the minimum version of the C-ECU 12B associated with the logic indicated by the ID. Also, "2.0.0" is registered as the next version of "1.0.1". This corresponds to the minimum version of the C-ECU 12B associated with the logic after the logic has switched. Therefore, the range of the C-ECU 12B corresponding to the logic ID: AAA is "1.0.1" or higher and less than "2.0.0". Here, the reason for stating less than "2.0.0" is that from the information in the logic ID management DB4, the range of the C-ECU 12B corresponding to the logic ID: AAA also includes "1.99.0" and "1.0.99".

[0028] Alternatively, as shown in FIG. 4, two C-ECU information "1.0.2" and "1.1.0" with the logic ID both being "AAA" may be added. In this case, the range of the C-ECU 12B corresponding to the logic ID: AAA is "1.0.1", "1.0.2", "1.1.0".

[0029] Then, when the generated package and the list of versions of the C-ECU 12B corresponding to the package; range are associated (S16), the associated version information is registered in the distribution server 3 (S17).

[0030] <Distribution Preparation Phase> As shown in FIG. 11, the distribution preparation phase is executed following the execution of the determination processing phase. After the distribution server 3 acquires the version of Package-C-ECU 12B generated in the distribution preparation phase, that is, the range of C-ECU 12B to which one package is applicable (S21), it narrows down the list of target vehicles from the version and the update target system (S22). To perform this narrowing down, data associating the vehicles referred to by the distribution server 3 with C-ECU 12B is prepared, and the distribution server 3 narrows down to perform distribution only to the vehicles equipped with C-ECU 12B of the acquired version. Since the distribution server 3 has the configuration information DB9 and the individual vehicle information DB10, it narrows down to the information of the actually existing C-ECU 12B from within the range of C-ECU 12B.

[0031] Then, the target vehicle for update is selected (S23). Here, it is approved by the OEM person in charge that the information of C-ECU 12B matches the vehicle to which the campaign is applied. For example, it is also possible to select only a specific vehicle such as a test vehicle as the target vehicle for update. The distribution server 3 prepares to identify the target vehicle by matching based on the information of C-ECU 12B to which a plurality of packages are associated for one case, so that the generated package is distributed to the vehicle to which it should be distributed. In this case, for example, a data table or the like is used to determine "OK" if the version of the update program distributed by the campaign is equal to or higher than the version of the target C-ECU 12B. Thus, the preparation for distribution, that is, the generation of the case is completed (S24).

[0032] <Distribution Phase> As shown in FIG. 12, when the process of synchronizing vehicle configuration information with the vehicle is completed (S31), the distribution server 3 determines whether the vehicle configuration information matches the vehicle configuration information before being updated with the issued campaign information (S32). If both pieces of information match, the information of the C-ECU 12B uploaded from the vehicle is confirmed (S33). Then, among the packages associated with the campaign information, those that match the information of the C-ECU 12B are distributed as the target vehicle (S34).

[0033] FIG. 13 shows an overview of the package generation process corresponding to step S14. Note that "repro" means "reprogram". Regarding the data update method, there are a storage method in which all of the update program is downloaded from the center device 1 to the memory on the vehicle side and then updated, and a streaming method in which the update program is downloaded from the center device 1 to the vehicle side while updating. The package generation process is divided into seven cases according to the combination of the platform types of the C-ECU 12B and the target ECU 13, the storage method, and the streaming method.

[0034] <CP-CP Storage> As shown in FIG. 14, by specifying the logic for generating the package, the corresponding CP storage repro setting file, CP repro header, and CP storage update data are acquired. Specification data is generated from the repro setting file and the repro header, and verification data is attached to the specification data. Regarding the update data, difference data and rollback data from the pre-update data are generated, and verification data for them is attached. File configuration information is generated from these, and after verification data is attached to it, the archived combination of these becomes the master layer package corresponding to CP-CP storage. Finally, the package is compressed into a ZIP file.

[0035] <AP-AP Streaming> As shown in FIG. 15, the logic identifies the file of the AP streaming update data and the AP streaming reprovisioning file. Regarding the update data, as described above, the differential data is generated, and the AP-AP streaming target layer package is generated. From the reprovisioning file for the AP, the Vehicle package is generated. These are collectively compressed into a ZIP file to form the final package.

[0036] <CP-CP Streaming> As shown in FIG. 16, for the specification data and its verification data, they are generated in the same manner as in the case of FIG. 14. When the update data for CP streaming is identified, for the corresponding differential data, the target layer package and the verification data of the differential data are generated. These are collectively compressed into a ZIP file.

[0037] <CP-CP Storage · CP-CP Streaming Mixed> In this case, as shown in FIG. 17, it becomes a pattern that integrates FIG. 14 and FIG. 16, and the data for CP-CP storage and the data for CP-CP streaming are combined into one package.

[0038] <AP-CP Storage> As shown in FIG. 18, the processing related to the CP storage part is substantially the same as in FIG. 14, but the rollback data is not included in the reprovisioning data and its verification data. Regarding the processing related to the AP storage part, only the Vehicle package is generated in the same manner as in FIG. 15.

[0039] <AP-CP Streaming> As shown in FIG. 19, it is the processing shown in FIG. 16 with the addition of the generation of the Vehicle package. <AP-CP Storage · AP-AP Streaming Mixed> As shown in FIG. 20, it is the integration of the processing shown in FIG. 15 and the processing shown in FIG. 18.

[0040] As described above, according to this embodiment, in the center device 1, the package generation server 2 refers to the manifest file registered in the file registration unit 6 and acquires an ID assigned to the logic for generating a package to be distributed to the vehicle. In the logic ID management unit 4, the ID is registered according to the specifications of the OTA master 12 that receives the distributed package on the vehicle side and transfers the update data to the target ECU 13. The package generation server 2 acquires information on the OTA master 12 corresponding to the ID from the logic ID management unit 4. When the package generation server 2 acquires the logic corresponding to the ID from the logic ID management unit 4, it generates a package based on that logic.

[0041] That is, by registering the manifest file in the file registration unit 6 in advance, the ID assigned to the logic can be acquired from the file. And once the ID is acquired, the information and logic of the OTA master 12 corresponding to that ID can be acquired. Therefore, the package generation server 2 can generate a package according to the specifications of the OTA master 12 based on the acquired logic.

[0042] In addition, the package generation server 2 acquires the logic ID from the manifest file on the condition that the information on the OTA master 12 cannot be acquired from the back office 7. That is, when a package generation request occurs, if the necessary information can be obtained from the back office 7, a package can be generated based on the information acquired therefrom. If the necessary information cannot be obtained from the back office 7, the logic ID can be acquired from the manifest file to generate a package.

[0043] Furthermore, the package generation server 2 associates the generated package with the information on the OTA master 12 corresponding to the logic ID and transmits it to the distribution server 3. Thereby, the distribution server 3 can distribute the package to the vehicle equipped with the OTA master 12 to be distributed.

[0044] Furthermore, the distribution server 3 includes a configuration information DB 9 in which device identification information for each of the plurality of target ECUs 13 and vehicle-related information related to the identification of the data stored in the device are stored together with the type of the vehicle, and identifies the vehicle to which the package is to be distributed by comparing the information regarding the OTA master 12 with the content of the configuration information DB 9. Then, when the information regarding the OTA master 12 of the vehicle that requests the distribution of the package corresponds to the vehicle to which the package is to be distributed, the package is distributed. Thereby, the center device 1 can appropriately distribute the generated package to the target vehicle.

[0045] Although the present disclosure has been described based on the embodiments, it is understood that the present disclosure is not limited to the embodiments and structures. The present disclosure also includes various modifications and modifications within the equivalent scope. In addition, various combinations and forms, and further other combinations and forms including only one element, more than one element, or less than one element thereof, are within the scope and spirit scope of the present disclosure.

[0046] The means and / or functions provided by each device or the like can be provided by software recorded in a physical memory device, a computer that executes the software, software only, hardware only, or a combination thereof. For example, when the control device is provided by an electronic circuit that is hardware, it can be provided by a digital circuit including a number of logic circuits or an analog circuit.

[0047] The control unit and its method described in the present disclosure may be implemented by a dedicated computer provided by configuring a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the control unit and its method described in the present disclosure may be implemented by a dedicated computer provided by configuring a processor with one or more dedicated hardware logic circuits. Or, the control unit and its method described in the present disclosure may be implemented by one or more dedicated computers configured by a combination of a processor and a memory programmed to execute one or more functions and a processor configured by one or more hardware logic circuits. Further, the computer program may be stored in a computer-readable non-transitory tangible recording medium as instructions to be executed by a computer.

Explanation of Signs

[0048] In the drawings, 1 represents a center device, 2 represents a package generation server, 3 represents a distribution server, 4 represents a logic ID management DB, 5 represents a logic management DB, 6 represents a file registration unit, 7 represents a back office, 11 represents a vehicle-side system, 12 represents an OTA master, 12B represents a C-ECU, and 13 represents a target ECU.

Claims

1. A center device that manages data to be written to a plurality of electronic control units mounted on a vehicle, a package generation unit (2) that generates a package including update data to be distributed to the vehicle, a logic identification information registration unit (4) in which identification information assigned to the logic for generating the package is registered according to the specifications of a master device (12) that is mounted on the vehicle, receives the package distributed from the center device, and transfers the update data to the electronic control unit, a logic registration unit (5) in which the logic is registered, and a file registration unit (6) in which a manifest file in which the identification information is described is registered, the package generation unit includes an identification information acquisition unit (S13) that acquires the identification information by referring to the manifest file, a master information acquisition unit (S15) that acquires information on the master device corresponding to the identification information from the logic identification information registration unit, and a logic acquisition unit (S14) that acquires the logic corresponding to the identification information from the logic identification information registration unit, and the center device that generates a package based on the logic.

2. The center device according to claim 1, wherein the identification information acquisition unit acquires the identification information from the manifest file on the condition that information on the master device cannot be acquired from an external server.

3. including a package distribution unit (3) that distributes the package to the vehicle, the center device according to claim 1 or 2, wherein the package generation unit associates the generated package with information on the master device corresponding to the identification information and transmits the package to the package distribution unit.

4. the package distribution unit includes a vehicle information storage unit (9) in which device identification information for each of the plurality of electronic control units and vehicle-related information related to the identification of data stored in the device are stored together with the type of the vehicle, the center device according to claim 3, wherein the vehicle to which the package is to be distributed is specified by comparing the information on the master device with the content of the vehicle information storage unit.

5. The center device according to claim 4, wherein the package distribution unit distributes the package when information on the master device of the vehicle that requests the distribution of the package corresponds to the vehicle to which the package is to be distributed.

6. The center device according to any one of claims 1 to 5, wherein the master information acquisition unit acquires the information of the master device as a range corresponding to the configurations of a plurality of master devices.

7. managing data to be written to a plurality of electronic control devices mounted on a vehicle, when generating a package including update data to be distributed to the vehicle, registering identification information assigned to the logic for generating the package according to the specifications of a master device that is mounted on the vehicle and receives a package distributed from a center device and transfers the update data to the electronic control device, registering the logic, registering a manifest file in which the identification information is described, acquiring the identification information by referring to the manifest file, acquiring information of a master device corresponding to the identification information, A method for generating a data package that acquires the logic corresponding to the identification information and generates a package based on the logic.

Images