Center, update control method, update control program, OTA master

The center system identifies and avoids defective software packages during OTA updates, ensuring timely and efficient application of important software updates in vehicles.

JP7582059B2Active Publication Date: 2024-11-13TOYOTA JIDOSHA KK
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2021081819
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-05-13
Publication Date
2024-11-13
Estimated Expiration
2041-05-13

AI Technical Summary

Technical Problem

Existing OTA update systems face delays in applying important software updates due to the risk of defects in campaign data, leading to potential disruptions and inefficiencies.

Method used

A center that communicates with an OTA master in vehicles, equipped with a distribution unit, defect determination unit, and application avoidance instruction unit, allowing for the identification and exclusion of defective software packages during updates.

Benefits of technology

Enables rapid application of critical software updates by avoiding defective packages, ensuring timely and efficient software updates without canceling entire campaigns.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582059000001
    Figure 0007582059000001
  • Figure 0007582059000002
    Figure 0007582059000002
  • Figure 0007582059000003
    Figure 0007582059000003
Patent Text Reader

Abstract

To provide a center capable of quickly applying update software with high importance.SOLUTION: A center comprises: a distribution unit for distributing campaign data including one or more package data that include one or more pieces of update software of a target ECU to an OTA master; a problem determination unit for determining whether or not a problem due to update of a content of predetermined package data included in predetermined campaign data has been found after the distribution of the campaign data; and an application avoidance instruction transmission unit for transmitting an application avoidance instruction to a vehicle to which the campaign data is applied so as not to apply the package data in which the problem has been found when applying the campaign data, when the problem has been found.SELECTED DRAWING: Figure 14
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a center capable of communicating with an OTA master provided in a vehicle via a network. [Background technology]

[0002] Conventionally, vehicles are equipped with multiple electronic control units (called "ECUs") for executing control functions. The ECU includes a processor and a storage unit, and the processor executes software stored in the storage unit to realize the control function of the ECU. The software stored in each ECU is updatable. Specifically, the software can be updated at a maintenance shop or the like using an external device connected via a diagnostic connector provided in the vehicle. In addition, the software can be updated using software downloaded from a distribution server provided in an update center via wireless communication by wirelessly connecting a communication device provided in the in-vehicle network to a communication network such as the Internet (for example, JP 2020-004245 A). This update service via wireless communication is called an OTA service.

[0003] In the update process in the above-mentioned OTA service, package data including one or more pieces of update software for updating the software of a specific ECU (called a target ECU) to be updated is distributed in units of events called "campaigns." As an example of package data, for example, "package data for automatic driving control" includes three pieces of update software, namely, update software for an accelerator ECU, update software for a steering wheel ECU, and update software for a brake ECU. In addition, "package data for window control" includes update software for a window control ECU. One campaign may include multiple pieces of package data. More specifically, these package data are compiled by distribution date and time to generate campaign data, and the campaign data is distributed to the vehicle. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-004245 A Summary of the Invention [Problem to be solved by the invention]

[0005] Here, let us assume that after a certain campaign data is distributed, a defect is found in part of the package data included in the campaign data. In such a case, the distribution of the campaign data itself is stopped. Therefore, if such campaign data contains package data that is not defective but includes important update software, there is a risk that the application of the important update software (including the package data) will be delayed due to the suspension of the distribution of the campaign data itself.

[0006] The present disclosure has been made in consideration of the above-mentioned problems, and aims to provide a center that is capable of quickly applying package data that includes update software of high importance. [Means for solving the problem]

[0007] In order to solve the above problem, one aspect of the disclosed technology is a center capable of communicating with an OTA master equipped in a vehicle via a network. The center includes a distribution unit that distributes campaign data including one or more package data including one or more update software for a target ECU to the OTA master, a defect determination unit that determines whether or not a defect associated with the update is found after distribution of a specific package data included in the specific campaign data, and an application avoidance instruction transmission unit that, when a defect is found, transmits an application avoidance instruction to a vehicle to which the campaign data is to be applied via a specific network so as not to apply the package data in which the defect is found when applying the campaign data. Effect of the Invention

[0008] According to the center of the present disclosure, even if a specified campaign data includes defective package data and a package that includes update software that is not defective but is highly important, the application of only the defective package can be avoided while the package without the defect can be applied, thereby enabling the update software of high importance to be applied quickly. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing the overall configuration of a system according to an embodiment of the present invention; [Diagram 2] Block diagram showing the general configuration of center 1 [Diagram 3] Block diagram showing the schematic configuration of the OTA master 31 [Figure 4] Center 1 Functional Block Diagram [Diagram 5] OTA Master 31 Functional Block Diagram [Figure 6] A memory map showing an example of data stored in the memory unit 16 of the center 1. [Figure 7] An example of the data configuration of the campaign definition data 103 [Figure 8] An example of data configuration for campaign content 122 [Figure 9] An example of the data structure of the package data 106 [Figure 10] An example of the data structure of defect data 107 [Figure 11] An example of the data configuration of the application avoidance target data 108 [Figure 12] A memory map showing an example of data stored in the memory unit 47 of the OTA master 31. [Figure 13] 1 is a flowchart showing details of a defect registration process according to a first embodiment. [Figure 14] 1 is a flowchart showing details of an update control process according to a first embodiment. [Figure 15]1 is a flowchart showing details of an OTA master control process in the first embodiment. [Figure 16] An example of the data configuration of the campaign definition data 103 according to the second embodiment [Figure 17] 11 is a flowchart showing details of a defect registration process according to a second embodiment. [Figure 18] 11 is a flowchart showing details of an update control process according to a second embodiment. [Figure 19] 11 is a flowchart showing details of an OTA master control process according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0011] (First embodiment) First, a first embodiment will be described. In the first embodiment, the following process is performed. After distribution of certain campaign data is started, if a defect is found in a specific package data (hereinafter simply referred to as a package) included in the campaign data, for example, an OEM manufacturer notifies an OTA center (hereinafter simply referred to as a center) of the defect. The center stores information about the defect. Then, when the OTA master inquires of the center about the presence or absence of software updates (hereinafter referred to as an update inquiry), if there are updates, the center distributes campaign data including one or more packages. At this time, information about the package with the defect (hereinafter referred to as a defective package) is transmitted from the center to the OTA master. Based on the information, the OTA master applies each package included in the specific campaign data while avoiding application of the defective package.

[0012] [Overall system configuration of the first embodiment] Next, a configuration of an update control system in the first embodiment will be described. Fig. 1 is a block diagram showing the overall configuration of the update control system in the first embodiment. The update control system includes a center 1 and a vehicle 3.

[0013] The center 1 is a server for managing software updates of an electronic control unit (hereinafter, ECU) provided in the vehicle 3 (more precisely, the center 1 is a center system including such a server, but for convenience of explanation, the center 1 will be described as a server below). The center 1 is capable of communicating with the vehicle 3 (OTA master 31).

[0014] The vehicle 3 is equipped with an in-vehicle network system. The in-vehicle network system is capable of communicating with the center 1. The in-vehicle network system includes at least an OTA master (software update device) 31, a communication module 32, and a plurality of ECUs 33a to 33d.

[0015] The OTA master 31 is connected to the communication module 32 and the ECUs 33a to 33d via a bus 35. The OTA master 31 is capable of wireless communication with the center 1 via the communication module 32. The OTA master 31 executes control of software update processing of each ECU 33 while transmitting and receiving predetermined data to and from the center 1. In other words, the OTA master 31 has a software update function. The communication module 32 is a communication device that connects to a predetermined network (such as a telephone network or the Internet).

[0016] The ECUs 33a to 33d control the operations of the various parts of the vehicle 3. It goes without saying that the number of ECUs 33 in FIG.

[0017] [Center 1 configuration] Fig. 2 is a block diagram showing a schematic configuration of the center 1. As shown in Fig. 2, the center 1 includes a processor 11, a RAM 12, a storage device 13, and a communication device 14. The storage device 13 includes a readable / writable storage medium such as a hard disk or SSD, and stores various programs and data required for the processing according to this embodiment. In the center 1, the processor 11 executes a program read from the storage device 13 by using the RAM 12 as a working area, thereby performing a predetermined control processing. The communication device 14 is a device that communicates with the vehicle 3 via a network.

[0018] [About the configuration of OTA Master 31] Fig. 3 is a block diagram showing a schematic configuration of the OTA master 31. As shown in Fig. 3, the OTA master 31 includes a microcomputer 45 including a processor 41, a RAM 42, a ROM 43, and a storage device 44, and a communication device 46. In the OTA master 31, the processor 41 of the microcomputer 45 executes a program read from the ROM 43 by using the RAM 42 as a working area, thereby executing a predetermined control process. The communication device 46 is a device that communicates with the communication module 32 and the ECUs 33a to 33d via the bus 35 shown in Fig. 1.

[0019] [Center 1 functional block diagram] Fig. 4 is a functional block diagram of the center 1. The center 1 includes a storage unit 16, a communication unit 17, and a control unit 18. The communication unit 17 and the control unit 18 are realized by the processor 11 shown in Fig. 2 executing a program stored in the storage unit 13 using the RAM 12, and the storage unit 16 is realized by the storage unit 13 shown in Fig. 2.

[0020] The storage unit 16 stores the programs and data used in the processing according to this embodiment.

[0021] The control unit 18 uses the communication unit 17 to transmit and receive predetermined data to and from the OTA master 31, and executes the software update process.

[0022] [OTA Master 31 Functional Block Diagram] FIG. 5 is a functional block diagram of the OTA master 31 shown in FIG.

[0023] The OTA master 31 includes a storage unit 47, a communication unit 48, and a control unit 49. The storage unit 47 is realized by the storage device 44 shown in Fig. 3, and the communication unit 48 and the control unit 49 are realized by the processor 41 shown in Fig. 3 executing a program stored in the ROM 43 using the RAM 42.

[0024] The storage unit 47 stores various programs and various data for executing the software update process.

[0025] The control unit 49 communicates with the center 1 via the communication unit 48 and executes various controls related to the software update process. Specifically, the control unit 49 inquires whether an update is available, and if so, downloads campaign-related data. It also inquires of the center 1 whether there is a defective package, and depending on the response, executes the update process while avoiding the application of only the defective package.

[0026] The process according to the first embodiment will be described in detail below.

[0027] [Data used at Center 1] First, the data used in the processing at the center 1 will be described. Fig. 6 is a memory map showing an example of data stored in the storage unit 16 of the center 1. The storage unit 16 stores an update control program 101, a vehicle database 102, campaign definition data 103, campaign data 104, defect data 107, application avoidance target data 108, and the like. Although not shown in the figure, various other programs and data for realizing the OTA service are also stored in the storage unit 16.

[0028] The update control program 101 is a program for controlling the software update process according to this embodiment.

[0029] The vehicle database 102 is a database of the vehicles 3 managed by the center 1, and specifically, is a database in which information about the vehicles 3 to which the OTA service is provided is registered. Although not shown in the figure, the vehicle database 102 includes a vehicle identification number (VIN) for identifying each vehicle 3, data indicating update history, and the like.

[0030] The campaign definition data 103 is data defining the contents of the above-mentioned campaign. FIG. 7 shows an example of the data structure of the campaign definition data 103. The campaign definition data 103 is data in a table format including at least the items of campaign ID 121, campaign contents 122, and applicable data 123. The campaign ID 121 is an ID for uniquely identifying the above-mentioned campaign. The campaign contents 122 is data relating to a package included in a predetermined campaign (the corresponding campaign data 104). For example, the campaign contents 122 has a data structure as shown in FIG. 8. In FIG. 8, the campaign contents 122 includes items of package ID 131 and package contents 132. The package ID 131 is an ID for identifying each package. The package contents 132 is data in which one or more update software IDs 133 for identifying update software included in the package are defined.

[0031] 7, the applicable target data 123 is data defining targets to which a certain campaign is applied. For example, the applicable target data 123 defines information such as the vehicle type to which the campaign is applied.

[0032] Returning to FIG. 6, the campaign data 104 is data generated based on the definition contents of the campaign definition data 103, and is data distributed to the OTA master 31 as a campaign. In FIG. 6, only one campaign data 104 is illustrated for convenience of explanation, but a plurality of campaign data 104 may be stored in the storage unit 16 according to the number of campaigns. One campaign data 104 includes a campaign ID 105 and one or more package data 106 according to the definition contents of the campaign definition data 103. The campaign ID 105 is an ID corresponding to the campaign ID 121 of the campaign definition data 103. The package data 106 is specific data of the package included in the campaign. FIG. 9 shows an example of the data configuration of the package data. Each package data 106 includes a package ID 141 and one or more update software 142. The package ID 141 is an ID corresponding to the package ID 131 of the campaign content 122. Although not shown, each update software 142 includes an update software ID corresponding to the update software ID 133 of the campaign content 122, and data that is the main body of the update software for the target ECU.

[0033] Returning to Fig. 6, next, defect data 107 is data related to the above-mentioned defective package. For example, the defect data 107 is added in response to notification of a defective package from an OEM manufacturer. Fig. 10 shows an example of the data configuration of the defect data 107. Defect data 107 stores a defective package ID 181, which is information for identifying a defective package.

[0034] The application avoidance target data 108 is data that can be generated based on the defect data 107, and is data for identifying defective packages for which application of updates should be avoided on a campaign-by-campaign basis. FIG. 11 is a diagram showing an example of the data configuration of the application avoidance target data 108. The application avoidance target data 108 is data in a table format including at least a campaign ID 151 and a target package 152. The campaign ID 151 is an ID for identifying the campaign data 104. The target package 152 is data indicating information for identifying a defective package (the above-mentioned defective package ID 181) with respect to the specified campaign data 104. Furthermore, when there are multiple defective packages to be avoided from being applied, information on each of the multiple packages is defined in order to identify them individually.

[0035] The partial avoidance instruction data 109 is data for instructing the OTA master 31 to avoid application of a predetermined defective package. The partial avoidance instruction data 109 includes information for identifying the defective package (the defective package ID 181 described above). In addition, since the partial avoidance instruction data 109 is transmitted to each OTA master 31, the storage unit 16 can (temporarily) store a plurality of partial avoidance instruction data 109 corresponding to each OTA master 31.

[0036] [About the data used by OTA Master 31] Next, a description will be given of data used in the OTA master 31. Fig. 12 is a memory map showing an example of data stored in the storage unit 47 of the OTA master 31. At least an update control program 151 and download data 162 are stored in the storage unit 47 of the OTA master 31. In addition, although not shown in the figure, various programs and data for realizing the OTA service are also stored in the storage unit 47.

[0037] The update control program 161 is a program for the OTA master 31 to execute the process according to this embodiment.

[0038] The download data 162 is data that (temporarily) stores predetermined campaign data 104 distributed from the center 1. The OTA master 31 executes an update process based on the download data 162.

[0039] In addition, although not shown in the figure, the storage unit 47 also stores partial avoidance instruction data 109 transmitted from the center 1 and the like.

[0040] [Processing flow of the first embodiment] Next, a description will be given of the flow of processing in the first embodiment. First, the processing executed in the center 1 will be described, and then the processing executed in the OTA master 31 will be described.

[0041] FIG. 13 is a flowchart showing details of the defect registration process executed by the center 1. The process can be repeatedly executed at a predetermined timing in the center 1. In addition, in this embodiment, when a defect is found in a predetermined package, information about the defect is transmitted to the center 1 by inter-server communication from the server of the OEM, which is the developer of the package, as an example. In FIG. 13, first, in step S1, the control unit 18 judges whether or not a new defect is found in the predetermined package. In this embodiment, the judgment is made based on whether or not information about the defect is received from the OEM server as described above. If the information is received, the control unit 18 judges that a new defect is found. If a new defect is found as a result of the judgment (YES in step S1), in step S2, the control unit 18 updates the contents of the defect data 107 based on the received information. Specifically, the control unit 18 registers a defect package ID 181 that identifies the new defective package in the defect data 107. Furthermore, the control unit 18 refers to the campaign definition data 103 and extracts a campaign ID 121 including the newly found defective package. Then, the control unit 18 updates the content of the application avoidance target data 108 based on the extracted campaign ID 121 and the content of the defect data 107. That is, the control unit 18 sets the extracted campaign ID 121 as the campaign ID 151 of the application avoidance target data 108, and adds data with the newly found defect package ID 181 as the target package 152 to the application avoidance target data 108. Thereafter, the control unit 18 ends the defect registration process.

[0042] On the other hand, if the result of the determination in step S1 above is that no new malfunction has been found (NO in step S1), the control unit 18 skips the process in step S2 above and ends the malfunction registration process.

[0043] In this embodiment, the defect registration process is described as an example in which defect information is sent from a predetermined OEM server to the center 1. However, in other embodiments, the defect registration process may be performed by manually updating the defect data 107 and the avoidance target data 108 by an operator or the like.

[0044] Next, FIG. 14 is a flowchart showing details of the update control process executed by the center 1. In FIG. 14, first, in step S11, the control unit 18 judges whether or not an update inquiry has been received from a predetermined OTA master 31. If not (NO in step S11), the control unit 18 continues to wait for the update inquiry by repeating the process of step S11. On the other hand, if an update inquiry has been received (YES in step S11), the control unit 18 judges whether or not there is an update for the vehicle 3 that has sent the update inquiry (hereinafter, the update inquiry source vehicle) in step S12. Specifically, the control unit 18 judges whether or not there is a deliverable campaign data 104 based on the vehicle database 102 and the campaign definition data 103. For example, the control unit 18 judges whether or not there is an update based on the update history of the update inquiry source vehicle. If the result of the determination is that there is no update, that is, there is no distributable campaign data 104 (NO in step S12), in step S14, the control unit 18 transmits a notice that there is no update to the OTA master 31 of the update inquiry source vehicle. After that, the control unit 18 returns to the above step S11 and repeats the process.

[0045] On the other hand, if the result of the determination in step S12 is that there is distributable campaign data 104 (YES in step S12), then in step S13, the control unit 18 distributes the campaign data 104 to the OTA master 31 of the update inquiry source vehicle.

[0046] Next, in step S15, it is determined whether or not an inquiry as to the presence or absence of application avoidance targets (hereinafter, application avoidance inquiry) has been received from the OTA master 31 that has distributed the above campaign data 104. The application avoidance inquiry is an inquiry as to whether or not there is a defective package whose application should be avoided for the distributed campaign data 104. The application avoidance inquiry may include information such as the campaign ID 151 that is the subject of the inquiry. As a result of the determination, if the application avoidance inquiry has not been received (NO in step S15), the control unit 18 continues to wait for the reception of the application avoidance inquiry. On the other hand, if the application avoidance inquiry has been received (YES in step S15), in step S16, the control unit 18 refers to the application avoidance target data 108 and determines whether or not there is a defective package for the campaign ID 151 related to the application avoidance inquiry. If the result of the determination is that there is no defective package (NO in step S16), in step S18, the control unit 18 transmits a notification that there is no defective package to the OTA master 31 of the vehicle 3 that sent the application avoidance inquiry (hereinafter, avoidance inquiry source vehicle). After that, the control unit 18 returns to the above step S11 and repeats the process.

[0047] On the other hand, if the determination result in step S16 indicates that there is a defective package (YES in step S16), in step S17, the control unit 18 generates partial avoidance instruction data 109 including information indicating the defective package based on the applied avoidance target data 108. Then, the control unit 18 transmits the partial avoidance instruction data 109 to the OTA master 31 of the avoidance inquiry source vehicle. After that, the control unit 18 returns to the above step S11 and repeats the process.

[0048] This concludes the explanation of the processing executed in the center 1.

[0049] Next, the process executed by the OTA master 31 will be described. Fig. 15 is a flowchart showing details of the OTA master control process executed by the OTA master 31. This process is executed, for example, once every two weeks when the ignition is turned on. In Fig. 15, first, in step S31, the control unit 49 of the OTA master 31 generates an update inquiry and transmits it to the center 1.

[0050] Next, in step S32, the control unit 49 receives response data to the update inquiry transmitted from the center 1 and determines whether there is an update, that is, whether there is campaign data 104 to be distributed. If the result of the determination is that there is no update (NO in step S32), the control unit 49 ends the OTA master control process.

[0051] On the other hand, if there is an update (YES in step S32), in step S33, the control unit 49 receives (downloads) the campaign data 104 from the center 1. After receiving the campaign data 104, in step S34, the control unit 49 generates the application avoidance inquiry. Then, the control unit 49 transmits the application avoidance inquiry to the center 1.

[0052] Next, in step S35, the control unit 49 judges whether or not the partial avoidance instruction data 109 has been received from the center 1. If the result of this judgment is that the partial avoidance instruction data 109 has not been received (in this case, it means that a message indicating that there is no defective package has been received from the center 1), in step S37, the control unit 49 executes an update process for applying all packages included in the campaign data 104 received in the above step S33. Then, when the update process is completed, the control unit 49 ends the OTA master control process.

[0053] On the other hand, if the result of the determination in step S35 is that partial avoidance instruction data 109 has been received (YES in step S35), in step S36, the control unit 49 stores the received partial avoidance instruction data 109 in the storage unit 47. Next, the control unit 49 executes an update process for applying other packages while not applying the defective package specified in the partial avoidance instruction data 109. For example, the control unit 49 may identify a package to be avoided from application from the download data 162 based on the defective package ID 181 included in the partial avoidance instruction data 109, and perform control to skip the process of applying the package. Then, when the update process is completed, the control unit 49 ends the OTA master control process.

[0054] This completes the description of the processes executed by the OTA master 31.

[0055] In this way, in the first embodiment, information on defective packages is stored in the center 1, and when applying updates related to a specific campaign, the information on the defective packages is transmitted to the OTA master 31. Then, the OTA master 31 executes update processing based on this information so as not to apply the defective packages. As a result, even if the specific campaign data 104 includes both a package including update software with no defects but high importance and a defective package, it is possible to apply the package including the update software with high importance without stopping the application of the entire campaign data 104.

[0056] (Second Example) Next, a second embodiment will be described. In the above first embodiment, the process is performed to simply not apply only the defective package. In contrast to this, in the second embodiment, the application avoidance is determined in consideration of the degree of association between packages included in a certain campaign data 104. For example, assume that a certain campaign data 104 includes package A, package B, and package C. Then, assume that a defect is found in package B. Furthermore, assume that in such a case, the degree of association between package A and package B is high. A high degree of association means, for example, a case in which the dependency between packages is relatively high, such as when a part of the function of the software included in package B is used to realize a function related to package A, or when the processing result of the software related to package B is used. Hereinafter, the relationship between packages with a high degree of association is called "tight coupling", and the relationship when the degree of association is low is called "loose coupling". In addition, in this embodiment, assume that in principle each package is "loosely coupled", but there are exceptional packages that are "tightly coupled".

[0057] As described above, when package A and package B are "tightly coupled," in the first embodiment, only the application of package B, which is a defective package, is avoided. In this case, package A is updated, but package B, which is "tightly coupled," is not updated. Therefore, package A, which uses or depends on the functions of package B (after update), may not achieve the expected performance. In addition, as a result of correcting a defect in package B, package A may also need to be further modified. In this case, package A needs to be updated again, which may result in a double update. In other words, even if only one of the "tightly coupled" packages is updated and applied, it may not function sufficiently on its own or may need to be updated again, so there is room for improvement in terms of the efficiency of the update process. Therefore, in the second embodiment, the degree of association between the defective package and other packages included in a certain campaign data 104 is determined. Then, only when the defective package is "loosely coupled" to other packages, a process is performed to avoid the application of the defective package. For example, in the above example, if package B is a defective package and it is "loosely coupled" to both packages A and C, a process is performed to avoid the application of only package B. On the other hand, if package B is "tightly coupled" with package A, the entire campaign is not applied (application is stopped).

[0058] The second embodiment will be described in detail below. First, the hardware configuration (center 1 and OTA master 31) in the second embodiment is basically the same as that in the first embodiment, and therefore a detailed description thereof will be omitted.

[0059] Next, data used in the second embodiment will be described. Basically, the same data as in the first embodiment is used in the second embodiment, but there is a difference in the data configuration of the campaign definition data 103 stored in the storage unit 16 of the center 1. Specifically, as shown in FIG. 16, the relevance data 124 is included in the campaign definition data 103.

[0060] The relevance data 124 is data that defines "tightly coupled" packages among the packages included in the predetermined campaign data 104. Specifically, package IDs 141 of packages in a "tightly coupled" relationship are defined. In addition, when there are multiple combinations of "tightly coupled" packages, each combination is defined so that it can be identified.

[0061] Next, a process flow according to the second embodiment will be described. FIG. 17 is a flowchart showing details of the defect registration process according to the second embodiment. In FIG. 17, first, in step S51, the control unit 18 judges whether or not a new defect has been found for a predetermined package. This process is the same as the process in step S1 above. As a result of the judgment, if a new defect has not been found (NO in step S51), the control unit 18 ends the defect registration process. On the other hand, if a new defect has been found (YES in step S51), in step S52, the control unit 18 updates the defect data 107 by adding information of the newly found defective package to the defect data 107.

[0062] Next, in step S53, the control unit 18 refers to the campaign definition data 103 and extracts campaign IDs 121 that include the defective package.

[0063] Next, in step S54, the control unit 18 determines whether or not the defective package is "loosely coupled" with other packages for the campaign data 104 corresponding to the extracted campaign ID 121, based on the relevance data 124. If the result of the determination is that the defective package is "loosely coupled" (YES in step S54), the control unit 18 adds data specifying only this defective package as an application avoidance target to the application avoidance target data 108 for the campaign data 104 including the defective package.

[0064] On the other hand, if the defective package is not "loosely coupled", that is, if it is "tightly coupled" with any package (NO in step S54), in step S56, the control unit 18 designates the defective package as an application avoidance target, and adds data indicating that the defective package is "tightly coupled" to the application avoidance target data 108. The data may be, for example, a flag indicating, with two values, whether the package is "tightly coupled" or "loosely coupled". This ends the defect registration process according to the second embodiment.

[0065] The processing of steps S55 and S56 is not limited to the above, and in the case of "loose coupling", an instruction to avoid application of the designated defective package may be stored as application avoidance target data 108, and in the case of "tight coupling", an instruction to stop application of the entire campaign may be stored as application avoidance target data 108. In this case, the OTA master 31 may control the update processing based on the instruction included in application avoidance target data 108.

[0066] Also, in the second embodiment, similarly to the first embodiment, the contents of the defect data 107 and application avoidance target data 108 may be updated manually by an operator or the like.

[0067] Next, an update control process executed by the center 1 in the second embodiment will be described. Fig. 18 is a flowchart showing details of the update control process according to the second embodiment. In this flowchart, the processes related to steps S11 to S18 are similar to the processes described above with reference to Fig. 14, so the description will be omitted here, and the other processes (steps S61 to S62) will be mainly described.

[0068] As a result of the determination in step S16 in FIG. 18, if there is a defective package (YES in step S16), in step S61, the control unit 18 refers to the application avoidance target data 108 and determines whether the defective package is "loosely coupled" with respect to other packages. Specifically, if the application avoidance target data 108 indicates content indicating that the defective package is "tightly coupled", the control unit 18 determines that the defective package is not "loosely coupled". If the content does not indicate that the defective package is "tightly coupled", the control unit 18 determines that the defective package is "loosely coupled". If the determination result indicates that the defective package is "loosely coupled" (YES in step S61), the control unit 18 executes the process of step S17 (sending partial avoidance instruction data 109). On the other hand, if the defective package is not "loosely coupled" (NO in step S61), in step S62, the control unit 18 transmits an application stop instruction to the OTA master 31 to stop application of the entire campaign.

[0069] Next, an OTA master control process in the second embodiment will be described. Fig. 19 is a flowchart showing details of the OTA master control process according to the second embodiment. In Fig. 19, the processes of steps S31 to S34 and S36 to S37 are similar to the processes described above with reference to Fig. 15, so the description will be omitted here, and the other processes (steps S71 to S73) will be mainly described.

[0070] 19, after sending an application avoidance inquiry to the center 1, in step S71 the control unit 49 judges whether or not there is a defective package based on the data received from the center 1. Specifically, the control unit 49 judges whether or not there is a message from the center 1 indicating that there is no defective package, and if this message has been received, it judges that there is no defective package. On the other hand, if the message indicating that there is no defective package has not been received, the control unit 49 judges that there is a defective package.

[0071] As a result of the above determination, if there is no defective package (NO in step S71), the process proceeds to step S37, where the control unit 49 applies all packages included in the campaign data 104. On the other hand, if there is a defective package (YES in step S71), in step S72, the control unit 49 determines whether the content received from the center 1 is a partial avoidance instruction. If the result of the determination is a partial avoidance instruction (YES in step S72), the process proceeds to step S36, where the control unit 49 executes the update process without applying only the defective package that is instructed to be avoided. On the other hand, if there is no partial avoidance instruction (NO in step S72), the application cancellation instruction has been received from the center 1, and therefore in step S73, the control unit 49 executes a process for canceling the application of the entire campaign. For example, the control unit 49 cancels the update process and discards the download data 162.

[0072] This concludes the detailed description of the processing according to the second embodiment.

[0073] In this way, in the second embodiment, the center 1 generates application avoidance target data 108 in consideration of the relationship between packages included in a given campaign. Then, when there is a defective package, if the defective package is "loosely coupled" with other packages, partial avoidance instruction data 109 for avoiding application of only the defective package is transmitted to the OTA master 31. As a result, when a certain defective package is "loosely coupled", the OTA master 31 can execute update processing so as to avoid application of only the defective package and apply updates to the other packages. Also, if the defective package is not "loosely coupled", control is performed to stop application of the entire campaign. This allows efficient update processing to be executed.

[0074] [Variations] In the second embodiment above, if the defective package is "tightly coupled" with other packages, the application of the entire campaign is stopped. In other embodiments, in such a case, control may be performed to avoid application of only the defective package and packages that are "tightly coupled" with it. For example, suppose that a campaign contains packages A, B, and C, and packages A and B are "tightly coupled." Then, consider a case in which a defect is found in package B. In this case, rather than stopping application of the entire campaign, control may be performed to avoid application of only packages A and B, and to apply an update to package C.

[0075] Also, in each of the above embodiments, an example was given in which an application avoidance inquiry is made after receiving campaign data 104. This is not limiting, and in other embodiments, an application avoidance inquiry may be made before starting to receive campaign data 104. Furthermore, in this case, control may be performed so that package data 106 related to a package to be avoided is not transmitted from center 1. This makes it possible to reduce the amount of communication and perform efficient communication.

[0076] The application avoidance instruction data may be notified via a network other than the network used for the OTA service. For example, the OTA service may be used over the Internet, and the application avoidance instruction data may be notified via SMS or V2X of a carrier network. If the OTA master 31 receives such application avoidance instruction data when applying a campaign, the OTA master 31 may perform an update process to avoid application of the defective package based on the application avoidance instruction data.

[0077] The above describes one embodiment of the disclosed technology. However, the present disclosure can be understood as an update control method executed by a computer at an OTA center that is equipped with not only a center but also at least a processor and a memory and is capable of communicating with an in-vehicle network, a control program for that method, a computer-readable non-transitory recording medium storing the control program, an OTA master, etc. [Industrial Applicability]

[0078] The disclosed technology can be used in a center that can communicate with an OTA master installed in a vehicle via a network. [Explanation of symbols]

[0079] 1 Center 3. Vehicle 11 Processors 12 RAM 13 Storage device 14 Communication equipment 31 OTA Master 32 Communication Module 33 Electronic Control Unit (ECU) 35 Bus 41 Processors 42 RAM 43 ROM 44 Storage device 46 Communication Equipment

Claims

1. A center capable of communicating with an OTA master provided in a vehicle via a network, A distribution unit that distributes campaign data including one or more package data including one or more update software for a target ECU to the OTA master; a defect determination unit that determines whether or not a defect has been found in the content of a predetermined package data included in the predetermined campaign data, the defect being associated with an update based on the campaign data after the campaign data has been distributed; The center is equipped with an application avoidance instruction sending unit that, when the defect is discovered, transmits an application avoidance instruction to a vehicle to which the campaign data is to be applied via a specified network, so as not to apply the package data in which the defect was discovered when applying the campaign data.

2. the center further comprises a degree of association determination unit that determines a degree of association between the package data in which the defect is found and other package data in the campaign data in which the package data is included, 2. The center according to claim 1, wherein the application avoidance instruction transmission unit transmits the application avoidance instruction when it is determined that the degree of association between the package data in which the defect was found and other package data is low.

3. An update control method executed by a computer at a center capable of communicating with an OTA master provided in a vehicle via a network, comprising: A distribution step of distributing campaign data including one or more package data including one or more update software for the target ECU to the OTA master; a defect determination step of determining whether or not a defect has been found in the content of a predetermined package data included in the predetermined campaign data, the defect being associated with an update based on the campaign data after the distribution of the campaign data; an application avoidance instruction sending step for, when the defect is discovered, sending an application avoidance instruction to the vehicle to which the campaign data is to be applied via a specified network so as not to apply the package data in which the defect was discovered when applying the campaign data.

4. An update control program to be executed by a computer at a center that includes at least a processor and a memory and is capable of communicating with an OTA master provided in a vehicle via a network, A distribution step of distributing campaign data including one or more package data including one or more update software for the target ECU to the OTA master; a defect determination step of determining whether or not a defect has been found in the content of a predetermined package data included in the predetermined campaign data, the defect being associated with an update based on the campaign data after the distribution of the campaign data; An update control program that causes the computer to execute an application avoidance instruction sending step, which, when the defect is discovered, sends an application avoidance instruction to the vehicle to which the campaign data is to be applied via a specified network, so as to prevent the application of the package data in which the defect was discovered when applying the campaign data.

5. An OTA master that is connected to an in-vehicle network including a plurality of ECUs, can communicate with a center via the network, and updates a program of one or more of the ECUs, an update inquiry unit that transmits an update inquiry to the center as to whether or not there is campaign data including one or more package data including one or more update software programs for the target ECU; a first receiving unit that receives the campaign data from the center when the campaign data is found as a result of the inquiry; an application avoidance inquiry unit that transmits an application avoidance inquiry to the center as to whether or not there is a package to be avoided among the package data included in the campaign data received from the center; an update processing unit that updates software of the target ECU using package data included in the campaign data, When the update processing unit receives an application avoidance instruction from the center as a result of the application avoidance inquiry indicating that part of the package data included in the campaign data will not be applied, the update processing unit updates the software of the target ECU by not applying only the specified package data indicated in the application avoidance instruction, the OTA master.

Citation Information

Patent Citations

  • Information processor and method for updating program thereof

    JP2005135147A

  • Client device, software streaming method and program

    JP2006344230A

  • Program update device, program update system, program update method and program update program

    JP2020004245A

  • Electronic control system for vehicle, method for controlling transfer of file, program for controlling transfer of file, and data structure of specification data

    JP2020027639A

  • Server, software update system, and software update device

    JP2021022018A