Patent ID: 12236227

DESCRIPTION OF EMBODIMENTS

To begin with, a relevant technology will be described first only for understanding the following embodiments. In a circumstance, it is conceivable that a communications carrier, which is a telecommunication company that provides infrastructure for wireless mobile communication, may differ in different regions and countries. It is also assumed that there are multiple communication carriers in each country, and the communication carriers used by each vendor are different. Under such circumstances, when a vehicle travels across multiple regions or countries, it is desirable to be able to smoothly communicate with carriers in each of the regions, which means to smoothly update application program.

The present disclosure has been made in view of the above circumstances, and one objective thereof is to provide a vehicle data communication device that can easily acquire update data of an electronic control unit from a communication carrier even when the vehicle travels across a plurality of regions. Another object thereof is to provide a corresponding center device for communicating with the vehicle data communication device, a data communication method thereof, and a computer-readable non-transitory tangible storage medium storing a corresponding computer program.

In this configuration, even when the vehicle moves across regions, the client selection unit (i) selects one of the plurality of communication clients that corresponds to the communication carrier and the region that are specified by the acquired information and (ii) activates the selected one of the plurality of communication clients, thereby enabling data communication with the corresponding distribution server in the respective region. Therefore, the vehicle data communication device can acquire update data for the electronic control unit in a destination area without the need for the user to consider the travelling state of the vehicle.

According to a second aspect of the present disclosure, the communication control unit controls the transition state between four phases of (1) checking data update, (2) downloading, (3) installing, and (4) activating in data communication with the distribution server. When the client selection unit switches and activates a communication client at the phase (2) or (3), the data communication is re-executed from the phase (1).

That is, when the communication client is switched while the data communication with the distribution server is in the downloading or installing phase, interruption of acquiring update data and writing the update data into the electronic control device is likely to occur. Therefore, the communication control unit acquires the update data by re-executing by the distribution server and the switched communication client from the data update.

According to a third aspect of the present disclosure, the communication control unit continuously executes data communication to the current phase when the client selection unit switches and activates a communication client at the same time as in the second aspect. That is, even if the OTA client is switched when the data communication with the distribution server is at the downloading phase or the installing phase, it is not necessary to retry from the data update check, and the switched communication client is continuously executed. As a result, it is possible to avoid an increase in data communication amount between the distribution server and the communication client.

Next, a plurality of embodiments will be described with reference to the drawings.

First Embodiment

As shown inFIG.1, a multiple OTA vendors system1of the present embodiment includes an OTA center2, as a center device, and a vehicle system3. The vehicle system3includes a DCM (Data Communication Module)4, a CGW (Central Gate Way)5, and a plurality of electronic control units (ECUs)6. InFIG.1, three ECUs6, which are electronic control units, are shown as three targets for updating an application program. In actual environment, more ECUs6are equipped to the vehicle.

DCM4is a vehicle communication device for data communication with the OTA center2via a mobile communication network, for example, a mobile object communication network such as a 4G line, the Internet, and Wi-Fi (Wireless Fidelity (registered trademark)). When the DCM4downloads a distribution package from the OTA Center2, the DCM4extracts write data from the distribution package and transfers the extracted data to CGW5. The CGW5then writes the data into the ECU6, which is a writing target.

In the OTA center2, a WEB portal21inquiries to a OEM (Original Equipment Manufacturer) operator22whether or not the application program has been updated, and when yes, the content of the update is reflected in a distribution server23.FIG.1shows, for example, three distribution servers (1) to (3) corresponding to three OTA vendors. The OEM operator22may exist individually, corresponding to each of the three OTA vendors, or may operate the three OTA vendors collectively.

The DCM4includes OTA clients (1) to (3)7corresponding to the distribution servers (1) to (3)23, respectively. The OTA client7is a software having a function of wirelessly communicating with the OTA center2and downloading the distribution package via the distribution server23. The downloaded distribution package is transferred to an in-vehicle cooperation unit9via an OTA sequence control unit8. The OTA sequence control unit8is an example of a communication control unit, and the OTA client7is an example of a communication client.

The DCM4includes an OTA vendor switching control unit10, a database11, and a communication information acquisition unit12. The communication information acquisition unit12is a wireless communication interface that performs, for example, LTE (Long Term Evolution) communication with the outside separately from the OTA client7. The communication information acquisition unit12can acquire information such as connection carrier information (Mobile Network Code) and country information (Mobile Country Code) by performing LTE communication with a communication carrier in each region.

As shown inFIGS.2and3, the database11stores information indicating which OTA vendor should be used in the corresponding region. It should be noted thatFIGS.2and3are different examples. Then, when the OTA vendor switching control unit10acquires connection carrier information and country information from the communication information acquisition unit12, the OTA vendor switching control unit10acquires such information from the database11. Next, the OTA client7corresponding to the distribution server23adopted by the OTA vendor in the region is enabled (activated) via the OTA sequence control unit8. The OTA vendor switching control unit10is an example of a client selection unit, and the database11is an example of a client storage unit.

The in-vehicle cooperation unit9is an interface for in-vehicle communication with the CGW5, and has functions such as “vehicle information acquisition”, “command control”, and “CAN/Eth communication”, etc. “CAN” is a registered trademark of ROBERT BOSCH GmbH, “Eth” is an abbreviation for “Ethernet”, and “Ethernet” is a registered trademark of Fuji Xerox Co., Ltd. The CGW5is also a reprogramming master that writes data into the target ECU6as described above, and communicates with the ECU6and the in-vehicle cooperation unit9to perform functions such as “vehicle information acquisition”, “ECU reprogramming control” and “power control”, etc. The CGW5updates the application program of the target ECU6, which is the rewrite target ECU, by using the distribution package transferred from the in-vehicle cooperation unit9, via the “ECU reprogramming control” function. The vehicle system3is an example of the data communication device.

Next, an operation of the present embodiment will be described. As shown inFIG.3, for example, there are three regions NO. 1: Northern, NO. 2: Middle, and NO. 3: Southern, corresponding carriers X, Y, and Z, and corresponding OTA vendors E, F, and G, respectively. Regarding the phase (or the state) of OTA implementation, there are following Phases 1 to 4.Phase 1: Check the distribution server for updatesPhase 2: DownloadPhase 3: InstallPhase 4: Activate.

As shown inFIG.5, for example, initial state of the region is “No. 2”, and the OTA vendor switching control unit10activates the OTA client (1)7corresponding to the OTA vendor: Company F (S1). When the OTA client (1)7is activated, it communicates with the distribution server (1)23, and although not shown, checks with the distribution server (1)23whether a program update is available. If there is a program update, the distribution package is downloaded (2). At this stage, when the communication information acquisition unit12acquires country information and recognizes that the region has been switched to “No. 1”, it notifies the OTA vendor switching control unit10(S3) of the region change.

Then, the OTA vendor switching control unit10accesses the DB11, and checks which OTA vendor should be selected in Region No. 2 (S4). Since the OTA vendor in Region No. 1 is Company E, the switching control unit10determines that it is necessary to switch to OTA client (2)7(S5). Therefore, the OTA vendor switching control unit10disables the OTA client (1)7(S6) and then activates the OTA client (2)7(S7).

The OTA client (2)7checks with the distribution server (2)23whether a program update is available, and when there is a program update, the distribution package is downloaded (S8). Thereafter, installation (S9) and activation (S10) are executed, and the OTA vendor switching control unit10recognizes the transition between the phases.

As shown inFIG.4, for each OTA vendor, the phase transition occurs in an order of Phases 1 to 4 while confirming the user's permission at each transition between the phases. In the present embodiment, for example, when a region change occurs at Phase 3 and the OTA vendor is switched, the OTA sequence control unit8returns to Phase 1 and restarts the process from checking update.

As described above, the OTA clients7use the line of the communication carrier to wirelessly communicate with the center device2and thereby acquires the update data to be written into the plurality of ECUs6. The information acquisition unit12uses wireless communication to acquire the information regarding the communication carrier and the region in which the center device2is located. The database11stores a plurality of communication clients that respectively correspond to different distribution servers (1)-(3)23. On the basis of the information acquired by the communication information acquisition unit12, the OTA vendor switching control unit10selects and activates one of the OTA clients7that corresponds to the communication carrier and the region from the database11, thereby making it possible for data communication with the distribution servers23.

In this configuration, even when the vehicle moves across regions, the OTA vendor switching control unit10selects and activates one of the OTA clients7corresponding to the communication carrier and the region specified by the acquired information, thereby enabling data communication with the distribution server23in each region. Therefore, the vehicle system3can acquire the update data for the ECUs6in the destination area without considering a travelling state of the vehicle.

When the OTA vendor switching control unit10switches and activates the OTA client7at the downloading phase (2) or the installing phase (3), the OTA sequence control unit8re-executes the data communication of the distribution server23from the downloading phase (1).

That is, when the OTA client7is switched while performing the data communication with the distribution server23at the downloading or installing phase, interruption of acquiring the update data and writing the update data into the ECU6is likely to occur. Therefore, the OTA sequence control unit8acquires the update data by retrying by the distribution server23and the switched OTA client7from the data update check.

Second Embodiment

Hereinafter, the identical parts as those in the first embodiment will be designated by the same reference numerals for simplification of the description. Only differences from the first embodiment will be described below. In the second embodiment, the phase transition by the OTA sequence control unit28and the switching control unit30shown inFIG.6is different from that of the first embodiment. For example, when communicating with Company F and region transition occurs at “Phase 3: installation”, the OTA sequence control unit28continuously executes the same “Phase 3: installation” at which the OTA vendor is switched to Company E.

As shown inFIG.7, an encryption key and a signature key used when transmitting/receiving the distribution package is different for each OTA vendor. The rewriting operation/procedure for rewriting the target ECUs is different for each OTA vendor, and the content and format of the metadata, which is specification data that defines the operation of rewriting, also differs for each OTA vendor. Therefore, when the OTA vendor is changed from Company F to Company E, it is necessary to perform format conversion of the metadata, which is the specification data, included in the distribution package. The metadata provided by the OEM includes information related to rewriting of an application program, information for specifying the rewrite target ECU, information for specifying a rewrite order when there are a plurality of rewrite target ECUs, and data defining behavior involved in the rewriting.

In the sequence shown inFIG.8, steps S1to S6are performed in the same manner as in the first embodiment. In this example, since “Phase 2: Download” is completed, when a metadata format conversion process is performed (S11), installation (S9) and activation (S10) are executed after step S7.

Next, the metadata format conversion process will be described. As shown inFIG.10, the format conversion process includes (1) rearranging the order of items, (2) converting data values, and (3) adding the number of items. As shown inFIG.9, the OTA vendor switching control unit30first confirms a conversion source and a conversion destination of the metadata (S11, S12). In the example shown inFIG.10, the conversion source is Company F and the conversion destination is Company E.

Subsequently, the OTA vendor switching control unit30accesses another database31instead of the database11and confirms the conversion source, the items in which the order should be changed for the conversion destination the items in which the data value should be changed for the conversion destination, and the necessity of adding any item for the conversion destination (S13). That is, the information necessary for these conversion processes is stored in advance in the database31. The database31is also a part of the client selection unit. When the order needs to be changed (S14; YES), the order of the items for the conversion destination in the metadata is changed (S15), and when the data value needs to be converted (S16; YES), the data value is converted (S17). When it is necessary to add an item (S18; YES), the item is added (S19).

In the example shown inFIG.10, the order of the item “rewriting environment” is changed from the first order to the third order, the data value of the item “data recognition” is changed, and the item “the number of target ECUs” is added. The metadata includes information related to the update data for the ECU to be rewritten, type information indicating the type of the ECU, and attribute information indicating the attribute of the ECU. The type information is an identification (ID) for device identification, indicating the type of each ECU device. The attribute information is information indicating a hardware attribute and a software attribute regarding the ECU. For example, “update program size” is an example of software attribute information. “Power control information” is an example of hardware attribute information.

As described above, according to the second embodiment, when the OTA switching control unit30switches and activates the OTA client7, the OTA sequence control unit28continuously executes the data communication from the current phase at which the switching and activating occurs. That is, even if the OTA client7is switched when the data communication with the distribution server23is at the downloading phase or the installing phase, it is not necessary to retry from the data update check. That is, the current phase can be maintained, and thus it is possible to avoid an increase in data communication amount between the distribution server23and the OTA client7.

Then, the database31stores the specification data including the information about the update target ECU and the update data related information of the ECU. When the OTA vendor switching control unit30switches to and activates the OTA client7, the format of the stored specification data before switching is converted into a format in compliant with the switched OTA client7. As a result, the OTA vendor can continuously execute the phase before and after switching.

Third Embodiment

As shown inFIG.11, the third embodiment relates to a process performed on the center device41instead of the center device2. OEM back-end systems43G to43E, which are replacement of the OEM operator22as described above, are connected to a WEB portal42. The OEM back-end systems43G to43E are systems that manage the software of each vehicle model in each OEM, and when an operator selects the software to be updated, the systems43G to43E forwards the software to the corresponding distribution servers23G to23E via the WEB portal42.

In the third embodiment, as shown inFIG.12, the WEB portal42hears the implementation phase of OTA for each distribution server23G to23E, that is, the update status of the program for each vehicle (S21). The distribution server23is an example of a log information storage unit. Then, the OTA implementation phase of each vehicle is compared, and as shown inFIG.13, the OTA phase implemented at the latest time is selected, and the information is merged, the merged result is displayed on the display or the like as KPI information (S22). The WEB portal42is an example of the information processing unit.

As described above, according to the third embodiment, in the center device41, the distribution server23stores the log information of the execution date and time of the phases (2) to (4) regarding a program update transmitted from the DCM4. The web portal42merges a plurality of pieces of log information for each of a plurality of vehicles into the latest information, if the plurality of pieces of log information stored for each of the plurality of communication clients in the distribution server23due to switching and activating of the communication client by the OTA vendor switching control unit30. As a result, the user can grasp the latest OTA implementation phase for each vehicle by referring to the KPI information which is the merged log information.

Other Embodiments

Although DCM4and CGW5are separated, they may be configured as an integrated ECU, or the functional part for communication of DCM4and CGW5may be configured as separated, and the other functional parts may be configured as an integrated ECU. The function of the DCM4in this embodiment may be implemented in the CGW5.

Although the present disclosure has been made in accordance with the embodiments, it is understood that the present disclosure is not limited to such embodiments and configurations. The present disclosure incorporates various modifications and variations within the scope of equivalents. In addition, the present disclosure also includes various combinations and configurations, as well as other combinations and configurations that include only one element, more, or less within the scope and spirit of the present disclosure.

In the above embodiment, each of the control unit may be provided separately as one or more than one controller or may be provided integrally as one or more than one controller. Such a controller and method thereof described in the present disclosure may be implemented by one or more than one special-purpose computer. Alternatively, the control unit described in the present disclosure and the method thereof may be realized by a dedicated computer configured as a processor with one or more dedicated hardware logic circuits. Alternatively, the control unit and the technique according to the present disclosure may be achieved using one or more dedicated computers constituted by a combination of the processor and the memory programmed to execute one or more functions and the processor with one or more hardware logic circuits. Further, the computer program may be stored in a computer-readable non-transitory tangible storage medium as instructions executed by a computer.