On-vehicle communication system

Abstract

To provide an on-vehicle communication system capable of efficiently updating software, with respect to an ECU mounted in a vehicle.SOLUTION: An on-vehicle communication system 10 corresponds to a plurality of communication standards, and updates software. The on-vehicle communication system 10 comprises a main OTA controller 100, and an ECU 300 and an area OTA controller 200 which belong to an area corresponding to a plurality of communication standards. The main OTA controller 100 has a first update data acquisition unit, a first transmission destination determination unit, and a first update data transmission unit which transmits update data to the area OTA controller 200 corresponding to an area of a transmission destination on the basis of a determination result. The area OTA controller 200 has a second update data acquisition unit, a second transmission destination determination unit, and a second update data transmission unit which transmits the update data to the ECU 300 of the transmission destination on the basis of the determination result.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an in-vehicle communication system. [Background technology]

[0002] Conventionally, a device for updating software of an electronic control unit (ECU: Electronic Control Unit) mounted on a vehicle has been proposed. Patent Document 1 discloses an in-vehicle relay device that controls software updates of an electronic control unit mounted on a vehicle. The in-vehicle relay device disclosed in Patent Document 1 outputs a program or the like acquired from an external server to an in-vehicle ECU to be updated, and performs an update process of the program of the in-vehicle ECU. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2021-157466 A Summary of the Invention [Problem to be solved by the invention]

[0004] Vehicles are equipped with on-board ECUs that correspond to various systems, such as powertrain systems such as engine control, body systems such as air conditioner control, information systems such as stereo amplifiers and car navigation systems, and safety systems such as airbags and occupant detection. In addition, various communication standards may be applied to these systems. Therefore, as on-board systems become more sophisticated and perform better, the number of on-board ECUs and communication systems also increases, which increases the burden on on-board relay devices that control software updates for each ECU, resulting in increased power consumption and delays in update processing. Therefore, there is a need for an on-board communication system that can efficiently perform software updates.

[0005] The present invention has been made in consideration of the problems inherent in the conventional technology, and an object of the present invention is to provide an in-vehicle communication system capable of efficiently updating software in an ECU mounted in a vehicle. [Means for solving the problem]

[0006] An in-vehicle communication system according to an embodiment of the present invention is an in-vehicle communication system that supports multiple communication standards and performs software updates, and includes a main OTA control device, and ECUs (Electronic Control Units) and area OTA control devices that belong to areas compatible with the multiple communication standards. The main OTA control device has a first update data acquisition unit that acquires update data, which is software for updating the ECUs, sent from a data center and stores it in a first memory unit, a first destination determination unit that determines an area to which the update data is to be sent based on the update data and area information stored in the first memory unit, and a first update data transmission unit that transmits the update data to an area OTA control device corresponding to the destination area based on the determination result determined by the first destination determination unit. The area OTA control device has a second update data acquisition unit that acquires the update data transmitted from the main OTA control device and stores it in a second memory unit, a second destination determination unit that determines an ECU to which the update data is to be sent based on the update data and the ECU information stored in the second memory unit, and a second update data transmission unit that transmits the update data to the destination ECU based on the determination result determined by the second destination determination unit. Effect of the Invention

[0007] According to the present invention, it is possible to provide an in-vehicle communication system capable of efficiently updating software in an ECU mounted in a vehicle. [Brief description of the drawings]

[0008] [Figure 1] 1 is a diagram showing a configuration of an in-vehicle communication system according to an embodiment of the present invention; [Diagram 2]1 is a diagram for explaining a configuration example to which an in-vehicle communication system according to an embodiment of the present invention is applied; [Diagram 3] 2 is a block diagram showing a configuration of a control device of the in-vehicle communication system according to the embodiment; FIG. [Figure 4A] 2 is a block diagram showing a functional configuration of a main OTA control device among the control devices of the in-vehicle communication system according to the present embodiment. FIG. [Figure 4B] 2 is a block diagram showing a functional configuration of an area OTA control device, among the control devices of the in-vehicle communication system according to the present embodiment. FIG. [Figure 5A] 4 is a diagram for explaining domain information of the in-vehicle communication system according to the embodiment; FIG. [Figure 5B] 4 is a diagram for explaining area information showing a correspondence relationship between domain information and area information of the in-vehicle communication system according to the embodiment; FIG. [Figure 5C] 4 is a diagram for explaining update data information of the in-vehicle communication system according to the embodiment; FIG. [Figure 5D] 4 is a diagram for explaining ECU information of the in-vehicle communication system according to the embodiment. FIG. [Figure 6] 4 is a sequence diagram for explaining a software update process in the in-vehicle communication system according to the embodiment. FIG. [Figure 7] 4 is a diagram for explaining collection of ECU information and area information in the in-vehicle communication system according to the embodiment. FIG. [Figure 8] FIG. 13 is a diagram showing a configuration of an in-vehicle communication system according to another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The in-vehicle communication system 10 according to the present embodiment will be described in detail below with reference to the drawings. Note that the dimensional ratios in the drawings are exaggerated for the sake of explanation and may differ from the actual ratios. In addition, in the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0010] (In-vehicle communication system 10) FIG. 1 is a diagram showing a schematic configuration of an in-vehicle communication system 10 according to this embodiment.

[0011] The in-vehicle communication system 10 is a communication system mounted on a vehicle, and includes a main OTA control device 100, an area control module 510, an area OTA control device 200, and a plurality of ECUs (Electronic Control Units) 300. The in-vehicle communication system 10 is compatible with a plurality of communication standards and performs software updates.

[0012] In this embodiment, the communication system to which the in-vehicle communication system 10 is applied has a plurality of systems (domains) corresponding to a plurality of communication standards. For example, communication between units (ECU 300) related to vehicle control such as the engine and suspension is assigned a communication standard for the powertrain and chassis system. Furthermore, communication between units related to vehicle interior control such as the air conditioner and doors is assigned a communication standard for the body system. Furthermore, communication between units related to entertainment such as car navigation and audio is assigned a communication standard for the information system. Furthermore, communication between units related to periphery monitoring such as cameras and sensors and airbags is assigned a communication standard for the safety system.

[0013] In this embodiment, the communication standard may be CAN (Control Area Network / registered trademark), CAN FD (CAN Flexible Data rate), or the like. In addition, in this embodiment, the communication standard may be Ethernet (registered trademark), LIN (Local Interconnect Network), FlexRay, or the like. Note that the types of communication standards applied do not limit the configuration of this embodiment.

[0014] In addition, in this specification, the in-vehicle communication system 10 according to the present embodiment shows a configuration example in which OTA (Over The Air) is applied, which is a technology for updating software of the ECU 300 in a vehicle by wireless communication. Note that, with respect to software updates, updating the software of the ECU 300 by wireless communication does not limit the configuration of the present embodiment. For example, in the in-vehicle communication system 10 according to the present embodiment, software updates by wire (such as a diagnostic tool) may be applied.

[0015] The area control module 510 controls the ECU 300 provided in each area. Fig. 2 is a diagram for explaining a configuration example to which the in-vehicle communication system 10 according to this embodiment is applied.

[0016] As shown in FIG. 2, ECUs 300 arranged at various locations within a vehicle configure a virtualized domain by connecting to an area control module 510 arranged nearby, regardless of the domain to which each ECU belongs.

[0017] In this embodiment, the multiple area control modules 510 control communication of the ECU 300 in the system to which a different area is assigned. In the example shown in Fig. 1, area control modules 511 to 514 are assigned to areas (1) to (4), respectively. Note that when there is no need to distinguish between the area control modules 511 to 514, they will be simply referred to as "area control modules 510."

[0018] The main OTA control device 100 is a device for controlling software updates of the ECU 300, and transmits update data and receives area information (see FIG. 5B) between the main OTA control device 100 and an area OTA control device 200 described below.

[0019] Furthermore, when the area OTA control device 200 does not exist in the area of ​​the ECU 300 that is the target of software update, the main OTA control device 100 may transmit update data to the ECU 300 and receive ECU information.

[0020] The area OTA control device 200 is a device that controls software updates of the ECU 300 provided in each area. For example, in the example shown in Fig. 1, area OTA control devices 200b, 200c, and 200d that belong to the areas are provided for area (2), area (3), and area (4), respectively. Hereinafter, when there is no need to distinguish between the area OTA control devices 200b, 200c, and 200d, they will be simply referred to as "area OTA control device 200."

[0021] 1 shows an example in which an area OTA control device 200 is not provided for area (1). For example, an example is shown in which the interval between software updates in area (1) is longer than in other areas. In this case, since the software of the ECU 300 belonging to area (1) is updated less frequently, when the software is updated, update data is transmitted directly from the main OTA control device 100 to the ECU 300 to be updated.

[0022] In this way, by configuring the in-vehicle communication system 10 so that the presence or absence of the area OTA control device 200 is determined depending on the frequency of software updates, software updates can be efficiently performed by the area OTA control device 200 in areas with a high frequency of updates.

[0023] ECU300 is an electronic control device belonging to each domain, and as described above, the communication standard applied varies depending on the area. In the example shown in Fig. 1, ECU_A1 to ECU_(X)1 belonging to area (1) are indicated by the reference characters ECU300a1 to ECU300x1, respectively. The reference characters in areas (2) to (4) are determined according to the same rules as those in area (1) shown in Fig. 1. Hereinafter, when it is not necessary to distinguish between ECU300a1 to ECU300x1, ..., ECU300a4 to ECU300x4, etc., they will be simply referred to as "ECU300".

[0024] (Main OTA control device 100) 3 is a block diagram showing the configuration of the main OTA control device 100. Note that the configuration shown in FIG.

[0025] In this embodiment, the main OTA control device 100 is configured by a general computer including a control unit 110, a storage unit 120, an input / output IF 130 (Interface), and a communication IF 140. The control unit 110 and the storage unit 120 will be described in detail later.

[0026] The input / output IF 130 is, for example, a component (interface) for a user to exchange data with the main OTA control device 100. The input / output IF 130 includes, for example, an input IF and an output IF (not shown).

[0027] The input IF in the input / output IF 130 has an interface function for inputting various information by the user, and enables information to be input from outside the main OTA control device 100. Information is input to the input IF by the user via, for example, a keyboard, a mouse, a touch panel, a trackball, a voice recognition device, or the like, connected to the main OTA control device 100. The input IF can also input information as a data input terminal for inputting data from an external storage device (not shown) or the like.

[0028] The output IF in the input / output IF 130 can display area information and update data information (described later) on a display device (not shown) connected to the main OTA control device 100. The display device is, for example, a display device.

[0029] The communication IF 140 is an interface that enables communication with an external data center 400. The communication IF 140 also has a function that enables communication between the ECU 300 and the area OTA control device 200 in the vehicle.

[0030] (Functional configuration of main OTA control device 100) Fig. 4A is a block diagram showing a functional configuration of the main OTA control device 100 according to this embodiment. As shown in Fig. 4A, the control unit 110 of the main OTA control device 100 includes, as functions, an update data acquisition unit 111, a transmission destination determination unit 112, a request transmission unit 113, a response information reception unit 114, and an update data transmission unit 115. The control unit 110 of the main OTA control device 100 also includes, as functions, an area information acquisition unit 116, and an area information reflection unit 117. The functions of the control unit 110 will be described later.

[0031] Furthermore, the control unit 110, for example, operates an operating system to control the entire main OTA control device 100. Furthermore, the control unit 110 operates based on a program stored in the storage unit 120 to execute the above-mentioned functions. Note that the program is not limited to being stored in the storage unit 120, and may be stored in, for example, a ROM (Read Only Memory) or the like (not shown) in the main OTA control device 100.

[0032] As shown in Fig. 4A, the storage unit 120 stores information included in an area information DB 121 (DB: Database) and an update data information DB 122 as data. The storage unit 120 for storing these data may be one or more. For example, a single storage unit 120 may be configured to store the data in separate areas. Alternatively, the data may be distributed and stored in multiple storage devices installed in physically separate locations. The storage unit 120 provided in the main OTA control device 100 corresponds to a first storage unit.

[0033] Area information is stored in the area information DB 121. The relationship between domain information and area information will be described with reference to Figures 5A and 5B.

[0034] 5A shows an example of domain information in this embodiment. The domain information includes items such as "domain name," "domain system," "ECU number," "ECU function," and "ECU software version number," and stores corresponding data.

[0035] FIG. 5B is a diagram for explaining area information showing a correspondence relationship between domains and areas in the in-vehicle communication system 10 according to the present embodiment. The ECUs 300 in each domain shown in FIG. 5A are divided into a plurality of areas as shown in FIG. 5B. Therefore, the main OTA control device 100 according to the present embodiment controls the corresponding area OTA control device 200 for the ECUs 300 that need to be updated according to the correspondence relationship (correspondence table) stored in the area information DB 121. Note that, in this embodiment, an example is shown in which the area OTA control device 200 does not exist in the area (1) as shown in FIG. 1. Therefore, when a software update is required for the ECUs 300 that belong to the area (1), the main OTA control device 100 updates the software for the ECUs 300 that directly correspond to the ECUs 300.

[0036] Update data information is stored in the update data information DB 122. Fig. 5C shows an example of update data in this embodiment. In the example shown in Fig. 5C, the update data has items such as "vehicle identification information," "ECU to be updated," "data," and "software version number," and data corresponding to each item is stored. "Vehicle identification information" corresponds to information for identifying the vehicle in which the in-vehicle communication system 10 is installed.

[0037] Next, each function of the control unit 110 of the main OTA control device 100 will be described.

[0038] The update data acquisition unit 111 acquires update data, which is software for updating the ECU 300, sent from the data center 400, and stores the update data in a first storage unit. The update data acquisition unit 111 provided in the main OTA control device 100 corresponds to a first update data acquisition unit.

[0039] The destination determination unit 112 determines the area of ​​the destination of the update data based on the update data and the area information stored in the storage unit 120. Specifically, the destination determination unit 112 refers to the area information based on the "update target ECU" stored in the update data, and determines the area that includes the ECU 300 to be updated. Note that the destination determination unit 112 provided in the main OTA control unit 100 corresponds to a first destination determination unit. Also, if the area OTA control unit 200 is not provided in the area to which the update data is to be transmitted, a request transmission unit 113 (described later) transmits a request as to whether or not the update is possible to the ECU 300 to be updated by the update data.

[0040] The request transmission unit 113 transmits a request to the ECU 300 when there is no corresponding area OTA control device 200 in the area to which the update data is to be transmitted, determined by the transmission destination determination unit 112. The request from the request transmission unit 113 is a request to inquire of the ECU 300, which is the transmission destination of the update data, whether or not the update data can be updated. The request transmission unit 113 provided in the main OTA control device 100 corresponds to a first request transmission unit.

[0041] Furthermore, the request transmitted from request transmission unit 113 may be a request to ECU 300 to transmit software version information.

[0042] The response information receiving unit 114 receives a response (answer) from the ECU 300 in response to the request transmitted by the request transmitting unit 113. When the response information receiving unit 114 receives a response from the ECU 300 to be updated with the update data that the update is possible, the update data transmitting unit 115 described below transmits the update data to the ECU 300 to be updated. When the response information receiving unit 114 receives a response from the ECU 300 to be updated with the update data that the update is impossible, the request transmitting unit 113 transmits a request again to the ECU 300 to be updated after a predetermined time has elapsed.

[0043] Furthermore, when the request transmitted from request transmitting unit 113 is a request to transmit version information of the software to ECU 300 , response information receiving unit 114 acquires the version information of ECU 300 .

[0044] The update data transmission unit 115 transmits the update data to the area OTA control device 200 corresponding to the destination area based on the determination result determined by the destination determination unit 112. The update data transmission unit 115 provided in the main OTA control device 100 corresponds to a first update data transmission unit.

[0045] As described above, when the area OTA control device 200 is not provided in the destination area and a response indicating that the update is possible is received from the ECU 300 to be updated, the update data transmission unit 115 transmits update data to the ECU 300 to be updated. The update data transmission unit 115 also issues a software update instruction (activation process) to the ECU 300 to be updated. With this configuration, the in-vehicle communication system 10 can update the software of the ECU 300 without providing the area OTA control device 200 in areas where software is updated infrequently, for example, and can update the software of the ECU 300 without going through the area OTA control device 200. As a result, by not providing the area OTA control device 200 in areas where software is updated infrequently, for example, it is possible to reduce the size of the device and reduce power consumption.

[0046] The area information acquisition unit 116 acquires area information transmitted from each area OTA control device 200. As shown in Fig. 5B, the area information includes an area software ID number indicating the version (version number) of the software of the ECU 300 belonging to each area system. The area software ID number is a number that changes every time the software of the ECU 300 in the area is updated. For example, area (2) in Fig. 5B shows an example in which the version numbers of the ECU software for ECU numbers ECU_A2 to ECU_D2 are 1.00 to 1.10.

[0047] For example, the area software ID number for area (2) is "area (2)_ID", which is the version number listed in order [1.00, 1.30, 1.10, 2.00, 1.10], issued as a code related to the software version of each ECU 300. This allows the main OTA control device 100 that receives the area software ID number to also know the software version status of the ECU 300 in the area. Also, if an area OTA control device 200 is not provided in the area, the area information transmitted from the ECU 300 that belongs to that area is acquired.

[0048] The area information reflecting unit 117 reflects the area information, including the ECUs 300 belonging to each area system and the versions (version numbers) of their software, acquired by the area information acquiring unit 116, in the area information DB 121. Furthermore, when the response information receiving unit 114 acquires version information of the ECUs 300, the area information reflecting unit 117 reflects the version information of the ECUs 300 in the area information DB 121.

[0049] (Area OTA control device 200) Fig. 4B is a block diagram showing a functional configuration of the area OTA control device 200 according to this embodiment. As shown in Fig. 4B, the control unit 210 of the area OTA control device 200 includes, as functions, an update data acquisition unit 211, a transmission destination determination unit 212, a request transmission unit 213, a response information reception unit 214, and an update data transmission unit 215. The control unit 210 of the area OTA control device 200 also includes, as a function, an ECU information reflection unit 216. Each function of the control unit 210 will be described later.

[0050] Furthermore, the control unit 210, for example, operates an operating system to control the entire area OTA control device 200. Furthermore, the control unit 210 operates based on a program stored in the storage unit 220 to execute each of the above-mentioned functions. Note that the program is not limited to being stored in the storage unit 220, and may be stored in, for example, a ROM (not shown) in the area OTA control device 200.

[0051] As shown in Fig. 4B, the storage unit 220 stores information included in an ECU information DB 221 and an update data information DB 222 as data. The storage unit 220 for storing these data may be one or more. For example, a single storage unit 220 may be configured to store the data in separate areas. Alternatively, the data may be distributed and stored in a plurality of storage devices installed in physically separate locations. The storage unit 220 provided in the area OTA control device 200 corresponds to a second storage unit.

[0052] The ECU information DB 221 stores ECU information. Fig. 5D shows an example of ECU information in this embodiment. In the example shown in Fig. 5D, the ECU information has items such as "ECU number", "ECU function", and "software version number", and corresponding data is stored. For example, the ECU information shown in Fig. 5D shows information in the ECU information DB 221 of the area OTA control device 200d in area (4).

[0053] The update data acquisition unit 211 acquires the update data transmitted from the main OTA control device 100, and stores it in the storage unit 220. Note that the update data acquisition unit 211 provided in the area OTA control device 200 corresponds to a second update data acquisition unit.

[0054] The destination determination unit 212 determines the ECU 300 to which the update data is to be transmitted, based on the update data and the ECU information stored in the storage unit 220. Specifically, the destination determination unit 212 determines the ECU 300 to be updated, based on the "update target ECU" stored in the update data, by referring to the ECU information. Note that the destination determination unit 212 provided in the area OTA control device 200 corresponds to a second destination determination unit.

[0055] The request transmission unit 213 transmits a request to the ECU 300, which is the transmission destination of the update data, to inquire whether or not the update data can be updated. The request transmission unit 213 provided in the area OTA control device 200 corresponds to a second request transmission unit.

[0056] Furthermore, the request transmission unit 213 transmits a request to the ECU 300 to transmit the version information of the software at a predetermined timing. Note that this predetermined timing is not limited to the configuration of this embodiment. For example, the request may be once every few hours or once every few days.

[0057] The response information receiving unit 214 receives a response (answer) from the ECU 300 in response to the request transmitted by the request transmitting unit 213. When the response information receiving unit 214 receives a response from the ECU 300 to be updated with the update data indicating that the update is possible, the update data transmitting unit 215 described below transmits the update data to the ECU 300 to be updated.

[0058] In addition, if the response information receiving unit 214 receives a response from the ECU 300 that is to be updated with the update data, indicating that the update is not possible, the request sending unit 213 sends a request again to the ECU 300 that is to be updated after a predetermined time has elapsed.

[0059] Furthermore, when the request transmitted from the request transmission unit 213 is a request to transmit version information of the software to the ECU 300 , the response information reception unit 214 acquires the version information of the ECU 300 .

[0060] The update data transmission unit 215 transmits the update data to the destination ECU 300 based on the determination result obtained by the destination determination unit 212. The update data transmission unit 215 also issues a software update instruction (activation process) to the ECU 300 to be updated. The update data transmission unit 215 provided in the area OTA control device 200 corresponds to a second update data transmission unit.

[0061] The ECU information reflecting unit 216 reflects, in the ECU information DB 221, the ECU information including the ECU 300 and the version (edition) of its software, acquired by the response information receiving unit 214.

[0062] As described above, in the in-vehicle communication system 10 according to this embodiment, the area OTA control device 200 determines whether or not software update of the ECU 300 is possible, transmits update data, and controls software update by issuing an update command. This eliminates the need for the in-vehicle communication system 10 to perform communication protocol conversion or the like when the main OTA control device 100 controls software updates of all the ECUs 300, making it possible to improve the efficiency of update processing in the in-vehicle communication system 10. In addition, by distributing the software update functions, the in-vehicle communication system 10 can improve the efficiency of update processing and reduce the power consumption of the main OTA control device 100.

[0063] (Software update process) Next, the flow of software update processing in the in-vehicle communication system 10 will be shown using the sequence diagram shown in Fig. 6. In the following explanation of the sequence diagram, the same contents as those described in the above explanation of the in-vehicle communication system 10 will be omitted or simplified.

[0064] In step S601, software update data is downloaded from the data center 400 to the main OTA control device 100.

[0065] In step S602, the update data acquisition unit 111 of the main OTA control device 100 acquires the update data, which is software for updating the ECU 300 and has been sent from the data center 400, and stores the update data in the storage unit 120.

[0066] In step S603, the destination determination unit 112 of the main OTA control device 100 determines the area of ​​the destination of the update data based on the update data and the area information stored in the storage unit 120. Specifically, the destination determination unit 112 refers to the area information based on the "update target ECU" stored in the update data, and determines the area that includes the ECU 300 to be updated. Note that the destination determination unit 112 provided in the main OTA control device 100 corresponds to a first destination determination unit.

[0067] In step S604, the update data transmission unit 115 of the main OTA control device 100 transmits the update data to the area OTA control device 200 corresponding to the destination area, based on the determination result determined by the destination determination unit 112. The update data transmission unit 115 provided in the main OTA control device 100 corresponds to a first update data transmission unit.

[0068] In step S605, the update data acquisition unit 211 of the area OTA control device 200 acquires the update data transmitted from the main OTA control device 100, and stores it in the storage unit 220. Note that the update data acquisition unit 211 provided in the area OTA control device 200 corresponds to a second update data acquisition unit.

[0069] In step S606, the destination determination unit 212 of the area OTA control device 200 determines the ECU 300 to which the update data is to be transmitted, based on the update data and the ECU information stored in the storage unit 220. Specifically, the destination determination unit 212 determines the ECU 300 to be updated, by referring to the ECU information, based on the "update target ECU" stored in the update data. The destination determination unit 212 provided in the area OTA control device 200 corresponds to a second destination determination unit.

[0070] In step S607, the request transmission unit 213 of the area OTA control device 200 transmits a request to the ECU 300, which is the transmission destination of the update data, to inquire whether the update data can be updated. The request transmission unit 213 provided in the area OTA control device 200 corresponds to a second request transmission unit.

[0071] In step S608, ECU 300 transmits a response to the inquiry from area OTA control device 200 about whether or not the update is possible.

[0072] In step S609, the update data transmission unit 215 of the area OTA control device 200 transmits the update data to the destination ECU 300 based on the determination result determined by the destination determination unit 212. The update data transmission unit 215 provided in the area OTA control device 200 corresponds to a second update data transmission unit. In addition, the update data transmission unit 215 issues a software update instruction (activation process) to the ECU 300 to be updated.

[0073] In step S610, ECU 300 updates the software based on the acquired update data.

[0074] (Collection and processing of ECU information, etc.) Next, the flow of the process of collecting ECU information and the like in the in-vehicle communication system 10 will be described using the sequence diagram shown in Fig. 7. In the following description of the sequence diagram, the same contents as those described in the above description of the in-vehicle communication system 10 will be omitted or simplified.

[0075] In step S701, the request transmission unit 213 of the area OTA control device 200 transmits a request (information transmission request) to the ECU 300 to transmit software version information at a predetermined timing. Note that this predetermined timing does not limit the configuration of this embodiment. For example, it may be once every few hours or once every few days.

[0076] In step S702, in response to a request from the area OTA control device 200, the ECU 300 transmits ECU information including software version information to the area OTA control device 200.

[0077] In step S703, the ECU information reflecting unit 216 of the area OTA control device 200 reflects the acquired ECU information in the ECU information stored in the ECU information DB 221 of the storage unit 220.

[0078] In step S704, the control unit 210 of the area OTA control device 200 transmits the area information stored in the ECU information DB 221 to the main OTA control device 100. The area information includes an area software ID number indicating the version (version) of the software of the ECU 300 belonging to each area system. The area software ID number is configured as a code in which the version numbers of the software of each ECU 300 are written in order.

[0079] In step S605, the area information acquisition unit 116 of the main OTA control device 100 acquires the area information transmitted from each area OTA control device 200. The area information includes an area software ID number indicating the version (edition number) of the software of the ECU 300 belonging to each area system, as shown in FIG. 5B.

[0080] The area software ID number is configured as a code in which the software version numbers of the ECUs 300 in the corresponding area are written in order. The area information reflecting unit 117 of the main OTA control device 100 reflects the ECUs 300 belonging to each area system included in the area software ID number and the versions (version numbers) of their software in the area information DB 121.

[0081] As described above, the in-vehicle communication system 10 according to the present embodiment is an in-vehicle communication system that supports multiple communication standards and updates software. The in-vehicle communication system 10 includes a main OTA control device 100, and an ECU 300 and an area OTA control device 200 that belong to an area that supports multiple communication standards. The main OTA control device 100 includes an update data acquisition unit 111 that acquires update data, which is software for updating the ECU 300, sent from a data center 400 and stores the update data in the storage unit 120. The main OTA control device 100 also includes a destination determination unit 112 that determines the destination area of ​​the update data based on the update data and the OTA information stored in the storage unit 120. The main OTA control device 100 also includes an update data transmission unit 115 that transmits the update data to the area OTA control device 200 that corresponds to the destination area based on the determination result determined by the destination determination unit 112. The area OTA control device 200 has an update data acquisition unit 211 that acquires update data transmitted from the main OTA control device 100 and stores it in the storage unit 220. The area OTA control device 200 also has a destination determination unit 212 that determines the ECU 300 to which the update data is to be transmitted, based on the update data and the ECU information stored in the storage unit 220. The area OTA control device 200 also has an update data transmission unit 215 that transmits the update data to the destination ECU 300, based on the determination result determined by the destination determination unit 212.

[0082] As a result, the in-vehicle communication system 10 can improve the efficiency of the update process and reduce the power consumption of the main OTA control device 100 by distributing the functions in the software update.

[0083] In addition, the request transmission unit 113 of the main OTA control device 100 may transmit a request to the ECU 300 when the corresponding area OTA control device 200 does not exist in the area of ​​the destination of the update data determined by the destination determination unit 112. The request from the request transmission unit 113 is a request to inquire of the ECU 300, which is the destination of the update data, whether or not the update data can be updated. The request transmission unit 113 provided in the main OTA control device 100 corresponds to a first request transmission unit. With this configuration, the in-vehicle communication system 10 is able to update the software of the ECU 300 without providing the area OTA control device 200 for areas where the software is updated infrequently, for example, without using the area OTA control device 200. In this way, the in-vehicle communication system 10 is configured to determine the presence or absence of the area OTA control device 200 depending on the frequency of software updates, and thus, in areas where the software is updated infrequently, the area OTA control device 200 efficiently updates the software.

[0084] Furthermore, the request transmission unit 213 of the area OTA control device 200 may transmit a request to the ECU 300, which is the destination of the update data, to inquire whether the update data can be updated. This eliminates the need for the in-vehicle communication system 10 to perform communication protocol conversion or the like when the main OTA control device 100 controls the software updates of all the ECUs 300, and makes it possible to improve the efficiency of the update process in the in-vehicle communication system 10.

[0085] (Other embodiments) Although the embodiments have been described in detail with reference to the drawings, the present embodiments are not limited to the contents described in the above embodiments. The components described above include those that a person skilled in the art can easily imagine and those that are substantially the same. Furthermore, the configurations described above can be appropriately combined. Various omissions, substitutions, or modifications of the configurations can be made without departing from the spirit of the embodiments.

[0086] In the above embodiment, the update data information DB222 of the area OTA control device 200 has a configuration in which update data transmitted from the main OTA control device 100 is stored. The update data information DB222 of the area OTA control device 200 may include an area for storing update data transmitted from the main OTA control device 100 and update data of an older version than the update data. With this configuration, for example, in a case where a software update fails due to some factor, the older version of the update data can be restored to operate the ECU300. Also, a configuration in which a plurality of different versions of update data are stored in the update data information DB222 may be applied. In this case, for example, it is possible to update software such as the display pattern of a car navigation system according to the user's preference for the ECU300 whose domain system is not directly related to the running of the vehicle, such as an information system.

[0087] In the above embodiment, the area OTA control device 200 is provided outside the area control module 510. This allows the area OTA control device 200 to be retrofitted as hardware to a network of a vehicle already on the market, and the software of other related devices such as the main OTA control device 100 can be updated to implement a method for updating the software of in-vehicle devices by OTA. Furthermore, software updates of other related devices can be performed by conventional wired software updates or at the timing of a model change or minor change of the vehicle by the vehicle manufacturer.

[0088] On the other hand, for example, as shown in Fig. 8, the in-vehicle communication system 10 may be configured such that the area OTA control device 201 is provided as a function in the area control modules 521 to 524. That is, the area OTA control devices 201 (area OTA control devices 201b to 201d) of the in-vehicle communication system 10 shown in Fig. 8 are provided in the area control modules 520 (area control modules 522 to 524) of the same area.

[0089] This makes it possible for the area OTA control device 201 to receive update data without increasing the data load rate of the normal area LAN. That is, when the area OTA control device 201 receives update data from the main OTA control device 100, the update data is not transmitted via the communication line of the normally operating area control module 520. This makes it possible for the in-vehicle communication system 10 to not increase the data load rate (traffic) on the communication line.

[0090] 8, there is no need to increase the number of hardware connection points or connection units. In other words, it is possible to suppress increases in hardware costs. Also, because there is no need to increase the number of connection points or connection units, it is possible to prevent risks that may be a concern in terms of connection reliability and security.

[0091] The features of the in-vehicle communication system 10 are described below.

[0092] The in-vehicle communication system 10 according to the first embodiment is an in-vehicle communication system that supports multiple communication standards and updates software. The in-vehicle communication system 10 includes a main OTA control device 100, and an ECU 300 and an area OTA control device 200 that belong to an area that supports multiple communication standards. The main OTA control device 100 has a first update data acquisition unit that acquires update data, which is software for updating the ECU 300, sent from a data center 400 and stores it in a first storage unit. The main OTA control device 100 also has a first destination determination unit that determines an area to which the update data is to be transmitted, based on the update data and the area information stored in the first storage unit. The main OTA control device 100 also has a first update data transmission unit that transmits the update data to the area OTA control device 200 that corresponds to the destination area, based on the determination result determined by the first destination determination unit. The area OTA control device 200 has a second update data acquisition unit that acquires the update data transmitted from the main OTA control device 100 and stores it in a second storage unit. The area OTA control device 200 also has a second destination determination unit that determines the ECU 300 to which the update data is to be transmitted, based on the update data and the ECU information stored in the second storage unit. The area OTA control device 200 also has a second update data transmission unit that transmits the update data to the destination ECU 300, based on the determination result determined by the second destination determination unit.

[0093] The first memory unit corresponds to memory unit 120. The first update data acquisition unit corresponds to update data acquisition unit 111. The first destination determination unit corresponds to destination determination unit 112. The first update data transmission unit corresponds to update data transmission unit 115. The second memory unit corresponds to memory unit 220. The second update data acquisition unit corresponds to update data acquisition unit 211. The second destination determination unit corresponds to destination determination unit 212. The second update data transmission unit corresponds to update data transmission unit 215.

[0094] According to the above configuration, the in-vehicle communication system 10 can improve the efficiency of the update process and reduce the power consumption of the main OTA control device 100 by distributing the functions in the software update.

[0095] The main OTA control device 100 of the in-vehicle communication system 10 according to the second embodiment may further include a first request transmission unit. The first request transmission unit of the main OTA control device 100 may transmit a request to the ECU 300, which is the destination of the update data, to inquire whether the update data can be updated. This transmission of the request from the first request transmission unit of the main OTA control device 100 to the ECU 300 is performed when there is no corresponding area OTA control device 200 in the area of ​​the destination of the update data determined by the first destination determination unit. The first request transmission unit corresponds to the request transmission unit 113.

[0096] According to the above configuration, for example, in an area where software is updated infrequently, the in-vehicle communication system 10 does not provide the area OTA control device 200, and can update the software of the ECU 300 without going through the area OTA control device 200. In this way, by configuring the in-vehicle communication system 10 to determine the presence or absence of the area OTA control device 200 depending on the frequency of software updates, the area OTA control device 200 can efficiently update software in areas where software is updated frequently.

[0097] The area OTA control device 200 of the in-vehicle communication system 10 according to the third embodiment may further include a second request transmission unit. The second request transmission unit may transmit a request to the ECU 300, which is the destination of the update data, to inquire whether the update data can be updated. The second request transmission unit corresponds to the request transmission unit 213.

[0098] According to the above configuration, the in-vehicle communication system 10 does not need to perform communication protocol conversion or the like when the main OTA control device 100 controls software updates of all the ECUs 300. That is, the in-vehicle communication system 10 can improve the efficiency of the update process in the in-vehicle communication system 10.

[0099] The area OTA control device 200 of the in-vehicle communication system 10 according to the fourth embodiment may include an area for storing the update data and the update data of an older version in the second storage unit. The second storage unit corresponds to the storage unit 220.

[0100] According to the above configuration, when software update fails due to some factor, the in-vehicle communication system 10 can restore the old version of update data to operate the ECU 300. Also, the in-vehicle communication system 10 can update software such as the display pattern of the car navigation system according to the user's preference for the ECU 300 whose domain system is not directly related to the running of the vehicle, such as an information system.

[0101] The in-vehicle communication system 10 according to the fifth embodiment may further include an area control module 511 that corresponds to any one of the multiple areas and controls communication of the ECU 300 arranged in the area. In addition, the area OTA control device 201 may be provided in the area control module 510 of the same area.

[0102] According to the above configuration, the in-vehicle communication system 10 can avoid increasing the data load rate of the normal area LAN when the area OTA control device 201 receives update data. That is, when the area OTA control device 201 receives update data from the main OTA control device 100, the update data is not transmitted via the communication line of the normally operating area LAN, and it is possible to prevent an increase in the data load rate (traffic) on the communication line. Furthermore, the in-vehicle communication system 10 does not need to increase the number of hardware connection points or the connection unit itself. That is, the in-vehicle communication system 10 can suppress an increase in hardware costs. Furthermore, since there is no need to increase the number of connection points or connection units, it is possible to prevent risks that are of concern in terms of connection reliability and security. [Explanation of symbols]

[0103] 10. In-vehicle communication systems 100 Main OTA control device 110, 210 Control unit 111, 211 Update data acquisition section 112, 212 Destination determination unit 113, 213 Request sending section 114, 214 Response information receiving unit 115, 215 Update data transmission unit 116 Area Information Acquisition Unit 117 Area Information Reflection Department 120, 220 storage section 121 Area Information DB 122, 222 Update data information DB 200, 201, 200b-200d, 201b-201d Area OTA control device 216 ECU information reflection section 221 ECU information DB 300, 300a1~300an ECU 400 Data Centers 510~514, 520~524 Area Control Module

Claims

1. An in-vehicle communication system that supports multiple communication standards and performs software updates, A main OTA control device, and an ECU (Electronic Control Unit) and an area OTA control device that belong to an area corresponding to the plurality of communication standards, The main OTA control device includes: a first update data acquisition unit that acquires update data, which is software for updating the ECU, sent from a data center and stores the update data in a first storage unit; a first destination determination unit that determines the area to which the update data is to be transmitted based on the update data and area information stored in the first storage unit; a first update data transmission unit that transmits the update data to the area OTA control device corresponding to the area of ​​the destination based on a result of the determination made by the first destination determination unit; The area OTA control device includes: a second update data acquisition unit that acquires the update data transmitted from the main OTA control device and stores the update data in a second storage unit; a second destination determination unit that determines the ECU to which the update data is to be transmitted based on the update data and the ECU information stored in the second storage unit; a second update data transmission unit that transmits the update data to the ECU as a destination based on a result of the determination made by the second destination determination unit.

2. The main OTA control device further includes a first request sending unit, 2. The in-vehicle communication system according to claim 1, wherein, when there is no corresponding area OTA control device in the area to which the update data is to be transmitted determined by the first transmission destination determination unit, the first request transmission unit transmits a request to the ECU to which the update data is to be transmitted, inquiring whether the update data can be updated.

3. The area OTA control device further includes a second request sending unit, The in-vehicle communication system according to claim 1 , wherein the second request transmission unit transmits a request to the ECU that is a transmission destination of the update data, inquiring whether or not the update data can be updated.

4. The area OTA control device includes an area in the second storage unit for storing the update data and an older version of the update data than the update data.

5. An area control module that corresponds to any one of the plurality of areas and controls communication of the ECUs arranged in the area, The in-vehicle communication system according to claim 4 , wherein the area OTA control device is provided in the area control module of the same area.

Images