Master device, relay device, external device, data communication system, data processing method, and data processing program

Abstract

A host device (14) that performs a diagnosis service configures a diagnosis client for the diagnosis service to a relay device connected to the host device in a manner that enables data communication. The relay device (6-8) performs the diagnosis service when the diagnosis client for performing the diagnosis service is configured from the host device, the authority to the diagnosis client is transferred, and the execution of the diagnosis service is instructed.

Description

[0001] Cross-reference of related applications

[0002] This application is based on Japanese Patent Application No. 2024-53765, filed on March 28, 2024, the contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to a main control device, a relay device, an external device, a data communication system, a data processing method, and a data processing program. Background Technology

[0004] Vehicles are equipped with numerous electronic control units (hereinafter referred to as ECUs). As a diagnostic service for ECUs, OTA (Over-The-Air) reprogramming technology is provided to wirelessly update the software installed in the ECU. A structure is disclosed in which, when there are multiple target ECUs that are the devices to be updated with software, the software is installed in parallel from the OTA master to multiple target ECUs (see, for example, Patent Document 1).

[0005] Existing technical documents

[0006] Patent documents

[0007] Patent document 1: Japanese Patent Application Publication No. 2018-92577.

[0008] When installing software from the OTA master controller to multiple target ECUs in parallel, data communication using the standard 11-bit CAN ID will fail if a conflict occurs between identical CAN IDs. Therefore, to prevent CAN ID conflicts, there are technical issues such as having to configure only one installer as a diagnostic client per vehicle, or requiring intervention to stop transmissions within the installer, thus increasing the software installation time. Furthermore, since only one installer is configured for each specific ECU, there are also technical issues where the target ECUs of the installer are limited to those capable of data communication with all ECUs in the vehicle, or those with high-performance specifications. These technical problems are common to all diagnostic services utilizing diagnostic communication, and are not limited to parallel software installation; they also occur in parallel remote diagnostics, vehicle information collection, and other similar scenarios. Summary of the Invention

[0009] This disclosure aims to appropriately reduce the constraints on the configuration objectives of the diagnostic client and appropriately shorten the time required for the diagnostic service, with the primary objective of providing appropriate diagnostic services and the secondary objective of enabling the main control device and relay device to provide appropriate diagnostic services.

[0010] This disclosure discloses a method for a master control device to perform diagnostic services. A diagnostic client is configured on a relay device, which enables the relay device to perform diagnostic services to the target device. The relay device is connected to the master control device in a manner capable of data communication.

[0011] One type of relay device disclosed herein is capable of data communication with a master control device that performs diagnostic services. The diagnostic service is performed to the target device after a diagnostic client for performing the diagnostic service has been configured from the master control device, a transfer of authority to the diagnostic client has been performed, and the execution of the diagnostic service has been instructed.

[0012] One aspect of this disclosure provides an external device capable of data communication with a master control device performing diagnostic services. The master control device receives and distributes the following information: configuration target information for determining the configuration target of a diagnostic client corresponding to the diagnostic service, and diagnostic service information for the master control device to perform the diagnostic service on the target device.

[0013] One aspect of the data communication system disclosed herein includes a master control device for performing diagnostic services and an external device capable of data communication with the master control device. The external device distributes the following information to the master control device: configuration target information for the master control device to determine the configuration target of a diagnostic client corresponding to the diagnostic service, and diagnostic service information for the master control device to perform the diagnostic service to the target device. Based on the configuration target information received from the external device, the master control device configures the diagnostic client in the relay device, and performs the diagnostic service to the target device based on the diagnostic service information received from the external device.

[0014] One data processing method disclosed herein includes a diagnostic client configuration step in a master control device that performs diagnostic services. The diagnostic client is configured in a relay device to enable the relay device to perform diagnostic services to the target device. The relay device is connected to the master control device in a manner that enables data communication.

[0015] One method of the data processing procedure disclosed herein causes a master control device performing diagnostic services to execute: a diagnostic client configuration step, configuring a diagnostic client on a relay device, the diagnostic client being used to enable the relay device to perform diagnostic services to the target device, the relay device being connected to the master control device in a manner capable of data communication.

[0016] One aspect of the data processing method disclosed herein involves a relay device capable of data communication with a master control device performing diagnostic services, comprising the following diagnostic service execution steps: When a diagnostic client for performing the diagnostic service is configured from the master control device, and a transfer of authority to the diagnostic client is performed and the execution of the diagnostic service is instructed, the diagnostic service is performed on the target device.

[0017] One aspect of the data processing procedure disclosed herein enables a relay device capable of data communication with a master control device performing diagnostic services to perform the following diagnostic service execution steps: performing the diagnostic service to the target device after a diagnostic client for performing the diagnostic service has been configured from the master control device, a transfer of authority to the diagnostic client has been performed, and the execution of the diagnostic service has been instructed.

[0018] One data processing method disclosed herein involves, in an external device capable of data communication with a master control device performing diagnostic services, a step of distributing configuration target information and diagnostic service information to the master control device. The configuration target information is used by the master control device to determine the configuration target of a diagnostic client corresponding to the diagnostic service, and the diagnostic service information is used by the master control device to perform the diagnostic service to the target device.

[0019] One aspect of the data processing procedure disclosed herein enables an external device capable of data communication with a master control device performing diagnostic services to perform a distribution step of distributing configuration target information and diagnostic service information to the master control device: the configuration target information is used by the master control device to determine the configuration target of a diagnostic client corresponding to the diagnostic service, and the diagnostic service information is used by the master control device to perform the diagnostic service to the service recipient device.

[0020] According to one aspect of this disclosure, a diagnostic client is configured in the relay device to enable data communication between the relay device and the master control device performing the diagnostic service, thus providing diagnostic services to the target device. This appropriately reduces the constraints on the configuration objectives of the diagnostic client, appropriately shortens the time required for the diagnostic service, and allows for more efficient diagnostic service delivery.

[0021] According to one aspect of this disclosure, a diagnostic service is performed when a diagnostic client for performing diagnostic services is configured from the main control device, permissions are transferred to the diagnostic client, and the execution of the diagnostic service is instructed. This appropriately reduces the constraints of the diagnostic client's configuration objectives and appropriately shortens the time required for the diagnostic service, thus enabling the diagnostic service to be performed appropriately.

[0022] According to one method of this disclosure, configuration target information for determining the configuration target of the diagnostic client for performing diagnostic services and diagnostic service information for performing diagnostic services to the service recipient device are distributed to the main control device. This enables the main control device and the relay device to perform diagnostic services appropriately.

[0023] According to one aspect of this disclosure, an external device distributes configuration target information to a master control device for determining the configuration target of a diagnostic client corresponding to the diagnostic service, and diagnostic service information for performing diagnostic services to the target device. The master control device configures the diagnostic client in the relay device based on the configuration target information received from the external device, and performs diagnostic services to the target device based on the diagnostic service information received from the external device. The external device enables the master control device and the relay device to perform diagnostic services appropriately. The master control device and the relay device can appropriately reduce the constraints of the diagnostic client's configuration target and appropriately shorten the time required for diagnostic services, thus enabling appropriate diagnostic service performance. Attached Figure Description

[0024] The foregoing objects, as well as other objects, features, or advantages of this disclosure, will become more apparent from the following detailed description with reference to the accompanying drawings. These drawings are as follows:

[0025] Figure 1 This is a diagram showing the overall structure of one implementation method.

[0026] Figure 2 This is a functional block diagram of the reprogrammable main controller.

[0027] Figure 3 It is a diagram showing the distribution of specification data and installers.

[0028] Figure 4 It is a diagram representing a series of processing stages.

[0029] Figure 5 This diagram illustrates the transfer of permissions to the installer.

[0030] Figure 6 It is a diagram representing specification data.

[0031] Figure 7 It is a diagram representing specification data.

[0032] Figure 8 It's a flowchart.

[0033] Figure 9 It's a flowchart.

[0034] Figure 10 It's a flowchart.

[0035] Figure 11 It's a flowchart.

[0036] Figure 12 It's a flowchart. Detailed Implementation

[0037] Hereinafter, one embodiment will be described with reference to the accompanying drawings. In this embodiment, the diagnostic service includes a whole service utilizing diagnostic communication, such as software updates, remote diagnostics, and vehicle information collection. The diagnostic client is equivalent to the write control function unit (installer) used for installation during the software update installation phase, the control function unit used for remote diagnostics, and the control function unit used for vehicle information collection, etc.

[0038] like Figure 1 As shown, the data communication system 1 (equivalent to a data communication system) is configured to enable data communication between an OTA (Over-The-Air) center 2 (equivalent to an external device) and vehicle-side systems 3 installed in the vehicle. A considerable number of vehicle-side systems 3 can communicate with the OTA center 2. The vehicle is, for example, an electric vehicle such as a battery-powered vehicle (BEV). Unlike non-electric vehicles such as gasoline vehicles that use gasoline as a power source, electric vehicles can freely control the power supply of all ECUs installed in the vehicle through software.

[0039] The vehicle-side system 3 includes an onboard communication unit (hereinafter referred to as a DCM (Data Communication Module)) 4 (equivalent to a control object device), a central gateway (hereinafter referred to as a CGW) 5, a first relay 6 (equivalent to a relay device), a second relay 7 (equivalent to a relay device), and a third relay 8 (equivalent to a relay device). CGW5, the first relay 6, the second relay 7, and the third relay 8 are referred to as domain controllers. The first relay 6, the second relay 7, and the third relay 8 are connected to CGW5, for example, via Ethernet (registered trademark).

[0040] OTA Center 2 generates and stores update packages containing the software and specification data of the objects to be updated. Additionally, OTA Center 2 stores update packages obtained from external sources such as OEMs (Original Equipment Manufacturers). OTA Center 2 includes: a configuration management function unit that manages the hardware and software configurations of the vehicle side that can be distributed with update packages; and a distribution management function unit that manages the distribution of update packages to the vehicle side. The software includes programs, data, libraries, etc., used to activate the ECU.

[0041] The specification data includes information that identifies the ECU corresponding to the OTA, information that identifies the target ECU to be updated with the software, information that identifies the object to be installed in the installation phase (described later), information that determines the installation order, information that identifies the object to be activated in the activation phase (described later), and information that determines the activation order. The ECU corresponding to the OTA is an ECU capable of implementing OTA. Furthermore, OTA Center 2 may distribute the specification data to the vehicle side including it in the update package, or it may distribute the specification data to the vehicle side separately from the update package.

[0042] DCM4 communicates with OTA Center 2 via a communication network. This communication network may include, for example, mobile communication networks based on 4G or 5G lines, the Internet, or WiFi (Wireless Fidelity) (registered trademark). Alternatively, DCM4 and CGW5 may be integrated, with DCM4's functionality incorporated into CGW5's structure. Alternatively, the functions of DCM4 and CGW5 may be integrated into a display device or similar structure. Upon receiving an update packet from OTA Center 2, DCM4 forwards the received update packet to CGW5. The software distributed from OTA Center 2 to DCM4 is, for example, OTA reprogramming software. For inter-center communication between OTA Center 2 and DCM4, the SOVD format conforming to the SOVD communication specification or the RestAPI format conforming to the Rest (REpresentational State Transfer) API communication specification is used. Software updates based on update packets distributed from OTA Center 2 are called wireless reprogramming. On the other hand, software updates based on update packets distributed from external tools described later are called wired reprogramming.

[0043] The CGW5 features a reprogrammable main controller (9), an in-vehicle HMI (Human Machine Interface) (10), remote diagnostics (11), and an in-vehicle client (hereinafter referred to as OBC) (12). Figure 2As shown, the reprogramming master controller 9 has a downloader 13 and an OTA master controller 14 (equivalent to a master controller device).

[0044] When a download execution request is input from the OTA master controller 14, the downloader 13 instructs the DCM4 to execute the download process. The downloader 13 downloads the update package from the OTA center 2 via the DCM4 by receiving the update package distributed from the OTA center 2 and transferring the received update package from the DCM4. The downloaded update package is temporarily stored in the reprogramming master controller 9 or an external memory, as described later.

[0045] The OTA master controller 14 includes an update control function unit 15, a status management function unit 16, a display control function unit 17, a write control function unit (FlashingAdapter) 18, a power control function unit 19, an OTA-compatible ECU list storage unit 20, and an active target ECU list storage unit 21. These functions are implemented through software processing by the CPU executing computer programs stored in a non-transitory physical storage medium based on a microcomputer, or through hardware processing based on dedicated electronic circuits.

[0046] The update control function unit 15 has the function of controlling software updates. The status management function unit 16 has the function of managing the status of the software update object that accompanies the software update. The display control function unit 17 has the function of controlling the display in the vehicle HMI 10 that accompanies the software update. The write control function unit 18 has the function of controlling the installation of software to the software update object. Hereafter, the write control function unit 18 is sometimes referred to as the installer 18 (equivalent to a diagnostic client).

[0047] The OTA-compatible ECU list storage unit 20 stores information from the specification data that identifies the ECUs compatible with the OTA as an OTA-compatible ECU list. The target ECU list storage unit 21 stores information from the specification data that identifies the target ECU as a target ECU list. ECUs in the target ECU list that are compatible with the OTA are the target ECUs, while ECUs in the target ECU list that are compatible with the OTA but not stored in the target ECU list are ECUs not included in the target ECU list.

[0048] The power control function unit 19 refers to the OTA-compatible ECU list to determine the ECU corresponding to the OTA update. The power control function unit 19 also refers to the target ECU list to determine the target ECU. The power control function unit 19 collaborates with the power control application 22 configured in the second relay 7 to control the power supply to the ECU as the software update progresses. Furthermore, although this embodiment illustrates the case where the power control function unit 19 and the power control application 22 collaborate to control the power supply to the ECU, the configuration could also include a power control ECU that controls the power supply to the ECU. The objects to which the power supply is controlled by the power control function unit 19 include the DCM4, the vehicle HMI 10, the first relay 6, the second relay 7, and the third relay 8.

[0049] The OBC12 includes a mediation function unit 23 and a diagnostic communication function unit 24. The mediation function unit 23 focuses on the diagnostic communication between the reprogramming master controller 9 and the relay unit and ECU, and determines which diagnostic communication to prioritize. The diagnostic communication function unit 24 performs the diagnostic communication between the reprogramming master controller 9 and the relay unit and ECU based on the mediation result of the mediation function unit 23.

[0050] The OBC12 connects to multiple ECUs 25 and 26 (equivalent to service targets or software update targets) via a first relay 6. These multiple ECUs 25 and 26 are connected to the first relay 6, for example, via a CAN bus. CAN communication between the first relay 6 and the multiple ECUs 25 and 26 uses a 29-bit CAN ID for data communication. The ECU among the multiple ECUs 25 and 26 connected to the first relay 6 that is the target for software updates can become the intended ECU. Although the example illustrates two ECUs connected to the first relay 6, the number of ECUs connected to the first relay 6 is not limited to two.

[0051] Similarly, OBC12 is connected to multiple ECUs 27 and 28 (equivalent to service targets or software update targets) via a second relay 7. These multiple ECUs 27 and 28 are connected to the second relay 7, for example, via a CAN bus. CAN communication between the second relay 7 and the multiple ECUs 27 and 28 is data communication using a 29-bit CAN ID. The ECU among the multiple ECUs 27 and 28 connected to the second relay 7 that is the target for software updates can become the intended ECU. Although the example illustrates two ECUs connected to the second relay 7, the number of ECUs connected to the second relay 7 is not limited to two.

[0052] Similarly, OBC12 is connected to multiple ECUs 29 and 30 (equivalent to service targets or software update targets) via a third relay 8. These multiple ECUs 29 and 30 are connected to the third relay 8, for example, via a CAN bus. CAN communication between the third relay 8 and the multiple ECUs 29 and 30 is data communication using a 29-bit CAN ID. The ECU among the multiple ECUs 29 and 30 connected to the third relay 8 that is the target for software updates can become the intended ECU. Although the example illustrates two ECUs connected to the third relay 8, the number of ECUs connected to the third relay 8 is not limited to two.

[0053] Additionally, ECU 31 is connected to OBC12 without a relay connection. The ECU that is the target of a software update among the multiple ECUs connected to OBC12 can become the target ECU. Although the case of one ECU not connected to OBC12 without a relay connection is illustrated, the number of ECUs not connected to OBC12 without a relay connection is not limited to one.

[0054] As described above, the power control application 22 configured in the second relay 7 cooperates with the power control function unit 19 of the OTA master controller 14 to control the power supply to the DCM4, vehicle HMI10, relays 6-8, and ECUs 25-31 as software updates are performed. That is, the OTA master controller 14 enables the power control function unit 19 and the power control application 22 to cooperate in controlling the power supply to the relays 6-8 and ECUs 25-31, which are capable of diagnostic communication through the diagnostic communication function unit 24.

[0055] If a start request is input from the OTA master controller 14 when DCM4, vehicle HMI10, repeaters 6-8, and ECUs 25-31 are all in a stopped state, the system will transition to the start state and begin power supply from the vehicle battery. If a stop request is input from the OTA master controller 14 when DCM4, vehicle HMI10, repeaters 6-8, and ECUs 25-31 are all in a start state, the system will transition to the stop state and cease power supply from the vehicle battery.

[0056] External tool 32 distributes the update package to OTA master controller 14 while installed in the connector configured in the vehicle. External memory 33 functions as an external storage device for OTA master controller 14. As described above, it functions as a temporary storage target for update packages downloaded from OTA center 2, and also functions as a temporary fallback target for the software before the update when the software of relays 6-8 and ECUs 25-31 is updated.

[0057] The software update process involves a series of stages, including the synchronization stage, the download stage, the installation stage, the activation stage, and the update completion notification stage. The synchronization stage involves synchronizing the software and hardware configuration information of the ECU installed in the target vehicle with the OTA center 2.

[0058] The download phase occurs when the OTA controller 14 downloads the update package from the OTA center 2. Before proceeding with the download phase, the OTA controller 14 determines factors such as whether the software to be downloaded is legitimate, and compares the data size of the software with the remaining charge capacity of the vehicle battery to determine if the download can proceed. For example, if the OTA controller 14 determines that the software to be downloaded is legitimate and that the remaining charge capacity of the vehicle battery is sufficient relative to the data size of the software, then the download phase begins.

[0059] The installation phase, within the OTA controller 14, involves installing the software extracted from the update package onto the target ECU. Installation refers to writing the software into the target ECU's storage area. Before proceeding with the installation phase, the OTA controller 14 determines factors such as whether the software to be installed is legitimate, and compares the data volume of the software with the remaining charge capacity of the vehicle's battery to determine if the installation can proceed. For example, if the OTA controller 14 determines that the software to be installed is legitimate and that the remaining charge capacity of the vehicle's battery is sufficient relative to the data volume of the software, then the installation phase begins.

[0060] The activation phase is the phase in which the installed software is activated in the target ECU. Before proceeding with the activation phase, the OTA master controller 14 determines, for example, whether the software to be activated is legitimate, and compares the amount of data in the software with the remaining charge capacity of the vehicle battery to determine whether activation can be performed until the end. For example, if the OTA master controller 14 determines that the software to be activated is legitimate and that the remaining charge capacity of the vehicle battery is sufficient relative to the amount of data in the software to be activated, then the activation phase begins.

[0061] The update completion notification stage is in the OTA master controller 14. When the target ECU receives the update completion notification through activation, it sends the update completion notification to the OTA center 2.

[0062] like Figure 3As shown, OTA Center 2 distributes specification data containing configuration target information, diagnostic service information, permission transfer information, and parallel execution information, along with the installer, to the vehicle side (equivalent to a distribution step). OTA Center 2 performs the distribution step through a data processing method, executing the distribution step through a data processing program. The configuration target information is used by OTA Master 14 to determine the configuration target of the installer. Based on the configuration target information, OTA Master 14 determines the first relay 6, the second relay 7, and the third relay 8 as the configuration targets of the installer, and configures the installer on the first relay 6, the second relay 7, and the third relay 8 as described later.

[0063] The diagnostic service information is used by the OTA master controller 14 to install software onto the target ECU. Based on the diagnostic service information, the OTA master controller 14 determines the target ECU and the order in which the software will be installed onto that target ECU, including whether to use a storage method or a streaming method. As described later, when a transfer of authority from the OTA master controller 14 to the installer occurs, the installer, whose authority has been transferred from the OTA master controller 14, determines the target ECU based on the diagnostic service information, determines the order in which the software will be installed onto that target ECU, including whether to use a storage method or a streaming method, and then performs the installation onto the target ECU.

[0064] The OTA master controller 14 determines the target of the permission transfer to the installer and the order of permission transfer based on the permission transfer information. When installing software to target ECUs 25-28 serially, for example, first installing software to target ECUs 25 and 26 connected to the first relay 6 and then installing software to target ECUs 27 and 28 connected to the second relay 7, the OTA master controller 14 first performs the permission transfer to the installer configured on the first relay 6, and then performs the permission transfer to the installer configured on the second relay 7. When installing software to target ECUs 25-28 in parallel, for example, according to the parallel execution information described later, the OTA master controller 14 simultaneously performs the permission transfer to the installer configured on the first relay 6 and the permission transfer to the installer configured on the second relay 7.

[0065] Parallel execution information is information used by the installer to perform software installation to the target ECUs in parallel. That is, it is information used to perform software installation to target ECUs 25 and 26 by the installer configured in the first relay 6, software installation to target ECUs 27 and 28 by the installer configured in the second relay 7, and software installation to target ECUs 29 and 30 by the installer configured in the third relay 8.

[0066] The parallel execution information contains information that determines whether the installation of software to the target ECU should be performed in parallel, or in other words, simultaneously, by multiple installers. Based on the parallel execution information, the OTA master controller 14 instructs the installers to perform the installation after the transfer of authority. If the installation of software to the target ECU is to be performed in parallel by multiple installers, the OTA master controller 14 instructs the installation of software to the target ECU to be performed simultaneously by multiple installers. Therefore, the OTA master controller 14 may, for example, instruct multiple installers to perform the installation in parallel, or instruct the installation to perform the installation at the same timing.

[0067] The parallel execution information may also include information that determines whether the software installation to the target ECU should be performed serially, or in other words, sequentially, by multiple installers, and information that determines the order in which the installations are performed sequentially. When the OTA master controller 14 causes the software installation to the target ECU to be performed serially by multiple installers, it causes the software installation to be performed sequentially by the multiple installers. Therefore, the OTA master controller 14, for example, instructs one installer to perform the installation, waits for a completion notification from that installer, and after receiving the completion notification, instructs the next installer to perform the installation. Furthermore, when instructing multiple installers to perform the installation in parallel, this waiting for a completion notification is not necessary.

[0068] The parallel execution information may also include information for the installer after the transfer of authority to install software to multiple target ECUs in parallel. Based on the parallel execution information, the installer installs software to multiple target ECUs in parallel or sequentially. When installing software to multiple target ECUs in parallel, the installer installs the software to multiple ECUs simultaneously. When installing software to multiple target ECUs sequentially, the installer installs the software to one target ECU at a time, and after completing the installation of the software to one target ECU, it proceeds to install the software to the next ECU.

[0069] Based on the configuration target information received from the OTA center 2, the OTA master controller 14 configures the installer on relay devices 6-8 (equivalent to the diagnostic client configuration step). The OTA master controller 14 performs the diagnostic client configuration step through a data processing method and executes the diagnostic client configuration step through a data processing program.

[0070] As an example of how the OTA controller 14 configures an installer on a configuration target, one method is to install the installer, which is an application, by appending the executable file of the installer received from the OTA center 2 to the file system of the configuration target. The OTA controller 14 can also remove the configured installer from the configuration target. As an example of how the OTA controller 14 removes the installer, one method is to uninstall the installer, which is an application, by deleting the executable file of the installer appended to the file system of the configuration target. Other methods for configuring or removing the installer by the OTA controller 14 include writing or deleting the binary data containing the installer to the address area of ​​the non-volatile memory of the configuration target, thereby installing or uninstalling the installer.

[0071] The OTA master controller 14 transfers authority to the installers configured in relay devices 6-8 based on the authority transfer information received from the OTA center 2, and instructs the installers to execute the software installation to the target ECU. The OTA master controller 14 executes the software installation to the target ECU in parallel according to the parallel execution information received from the OTA center 2.

[0072] like Figure 4 As shown, the OTA controller 14, as part of a series of processes involved in software updates, performs the following stages: synchronization (S1), download (S2), installation (S3), activation (S4), and update completion notification (S5). Figure 5 As shown, during the installation phase, the OTA master controller 14 configures the installer 18, OBC 12, and specification data to the relay units 6-8, and transfers the authority to the configured installer 18, instructing the installer 18 to execute the software installation to the target ECU.

[0073] That is, when the installer 18 is configured from the OTA master controller 14, the authority is transferred to the installer 18, and the installation is instructed to be executed, the first relay unit 6 performs software installation on the target ECUs 25 and 26 (equivalent to the diagnostic service execution step). The first relay unit 6 performs the diagnostic service execution step through a data processing method and executes the diagnostic service execution step through a data processing program.

[0074] Similarly, when the installer 18 is configured from the OTA master controller 14, and the authority to be transferred to the installer 18 is transferred and the installation is instructed to be executed, the second relay 7 installs the software to the target ECUs 27 and 28. When the installer 18 is configured from the OTA master controller 14, and the authority to be transferred to the installer 18 is transferred and the installation is instructed to be executed, the third relay 8 installs the software to the target ECUs 29 and 30.

[0075] The specification data is explained. When the OTA master controller 14 configures the specification data for repeaters 6-8, there are two scenarios: one where the OTA master controller 14 and repeaters 6-8 are configured with common specification data, and another where each repeater 6-8 is configured with its own specific specification data. In the case where the OTA master controller 14 and repeaters 6-8 are configured with common specification data, such as... Figure 6 As shown, the configuration stores the specification data of each target ECU, including the OTA master controller 14 and relays 6-8. The reference data for relays 6-8 is included in "Sync Group Info A". Relays 6-8 install software to target ECUs 25-30 by referring to the data defined for their own reference objects.

[0076] With the OTA main controller 14 and repeaters 6-8 configured with their inherent specifications, such as Figure 7 As shown, the configuration stores specification data containing information about each target ECU of each of the relay units 6-8. The reference data for the first relay unit 6 is contained in "Sync Group Info B", the reference data for the second relay unit 7 is contained in "Sync Group Info C", and the reference data for the third relay unit 8 is contained in "Sync Group Info D". Relay units 6-8, respectively, refer to the data defined for their reference units to install software onto the target ECUs 25-30.

[0077] Next, refer to Figures 8 to 12 The function of the above structure will be explained. The installer configuration process where the OTA master controller 14 configures the installer 18, OBC12, and specification data to repeaters 6-8, and the permission transfer determination process where repeaters 6-8 determine whether a permission transfer from the OTA master controller 14 to the installer 18 has occurred, will be explained. Furthermore, while the case where the OTA master controller 14 configures the installer 18, OBC12, and specification data to the first repeater 6 will be explained here, the same applies to the second repeater 7 and the third repeater 8.

[0078] (1) Installer configuration processing (refer to) Figure 8 )

[0079] When the OTA master controller 14 completes the download phase and begins the installation phase, it starts the installer configuration process, sending the installer 18, OBC12, and specification data to the first relay 6, and configuring the installer 18, OBC12, and specification data on the first relay 6 (A1). The OTA master controller 14 determines whether it can transfer the authority to the installer 18 configured on the first relay 6 (A2).

[0080] For example, if the OTA controller 14 is unable to install the software to the target ECUs 25 and 26 due to the processing load of the first relay unit 6 exceeding a threshold, and determines that it cannot transfer the authority to the installer 18 configured on the first relay unit 6 (A2: No), it terminates the installer configuration process. Furthermore, if the OTA controller 14 determines that it cannot transfer the authority to the installer 18, it can also wait until it determines that it can transfer the authority to the installer 18.

[0081] For example, when the OTA master controller 14 is in a state where it can execute the installation of software to the target ECUs 25 and 26 due to the processing load of the first relay unit 6 being less than a threshold, and determines that it is possible to transfer the authority to the installer 18 configured on the first relay unit 6 (A2: Yes), it performs the authority transfer to the installer 18 configured on the first relay unit 6 (A3). The OTA master controller 14 instructs the installer 18 to execute the installation (A4) and waits to receive the installation execution completion notification from the first relay unit 6 (A5). When the OTA master controller 14 determines that it has received the installation execution completion notification from the first relay unit 6 (A5: Yes), it sends a deletion instruction notification for the installer 18, OBC12, and specification data to the first relay unit 6, and instructs the first relay unit 6 to delete the installer 18, OBC12, and specification data (A6), ending the installer configuration process.

[0082] In addition, the OTA master controller 14 can perform the installer configuration process of configuring the installer 18 to the first relay 6, the installer configuration process of configuring the installer 18 to the second relay 7, and the installer configuration process of configuring the installer 18 to the third relay 8 in serial order, or in parallel order.

[0083] (2) Handling of authority transfer (refer to) Figure 9 )

[0084] When the installer 18, OBC12, and specification data are configured from the OTA master controller 4, the first relay unit 6 begins the permission transfer determination process and waits for the permission transfer to the installer 18 from the OTA master controller 14 (B1). For example, if the first relay unit 6 determines that no permission transfer from the OTA master controller 14 to the installer 18 has been performed within a specified time after the installer 18, OBC12, and specification data are configured (B1: No), the first relay unit 6 deletes the installer 18, OBC12, and specification data (B8) and sends a status notification to the OTA master controller 4 indicating that the deletion of the installer 18, OBC12, and specification data has been completed (B9), thus ending the permission transfer determination process. By deleting the installer 18, OBC12, and specification data, the first relay unit 6 avoids unnecessary memory usage and prevents improper installations due to unnecessarily remaining installer 18.

[0085] For example, when the first relay 6 determines that the transfer of authority from the OTA master controller 14 to the installer 18 has been performed within a specified time after the installer 18, OBC 12 and specification data have been configured (B1: Yes), it waits for an instruction (B2) to execute the installation of the installer 18 whose authority has been transferred.

[0086] For example, if the first relay unit 6 determines that it has not instructed the installer 18 to perform the installation within a specified time after the transfer of authority to the installer 18 has been completed (B2: No), it performs the above steps S8 and S9 and ends the authority transfer determination process.

[0087] For example, when the first relay unit 6 instructs the installer 18 to perform the installation within a specified time after the transfer of authority to the installer 18 has been completed (B2: Yes), it determines the target ECU based on specification data (B3). The first relay unit 6 installs software to the determined target ECU (B4) and waits for the software installation to the target ECU to complete (B5). That is, the first relay unit 6 installs software to target ECUs 25 and 26 and waits for the software installation to the target ECUs 25 and 26 to complete. In this case, the first relay unit 6 can perform the software installation to target ECU 25 and target ECU 26 either serially or in parallel.

[0088] When the first relay unit 6 determines that the software installation to the target ECUs 25 and 26 has been completed (B5: Yes), it sends an installation completion notification to the OTA master controller 14 (B6) and waits to receive a deletion instruction notification for the installer 18, OBC12, and specification data from the OTA master controller 4 (B7). When the first relay unit 6 determines that it has received a deletion instruction notification for the installer 18, OBC12, and specification data from the OTA master controller 4 (B7: Yes), it performs the above steps S8 and S9 and ends the permission transfer determination process.

[0089] Furthermore, when the transfer of authority to the installer 18 configured in relay units 6-8 is carried out, the installation of software from the first relay unit 6 to the target ECUs 25 and 26, the installation of software from the second relay unit 7 to the target ECUs 27 and 28, and the installation of software from the third relay unit 8 to the target ECUs 29 and 30 can be performed serially or in parallel.

[0090] The above example illustrates the case where the installer 18, OBC12, and specification data configured on repeaters 6 to 8 are deleted based on the completion of software installation. However, the installer 18, OBC12, and specification data configured on repeaters 6 to 8 can also be deleted based on the completion of software activation.

[0091] In this case, such as Figure 10 As shown, the OTA master controller 14 instructs the installer 18 to execute the installation (A4). When the installation is confirmed to be complete, it instructs the activation to be executed (A11) and waits to receive an activation completion notification from the first relay 6 (A12). When the OTA master controller 14 confirms that it has received an activation completion notification from the first relay 6 (A12: Yes), it sends a deletion instruction notification for the installer 18, OBC12, and specification data to the first relay 6, and instructs the first relay 6 to delete the installer 18, OBC12, and specification data (A6), thus ending the installer configuration process.

[0092] like Figures 11 to 12 As shown, the first relay unit 6 waits for the software installation to the target ECU to complete (B5). When it is determined that the software installation is complete (B5: Yes), it waits for the software activation to complete (B11). When it is determined that the software activation is complete (B11: Yes), the first relay unit 6 sends an activation execution completion notification to the OTA master controller 14 (B12) and waits to receive a deletion instruction notification for the installer 18, OBC12, and specification data from the OTA master controller 4 (B7). When the first relay unit 6 determines that it has received the deletion instruction notification for the installer 18, OBC12, and specification data from the OTA master controller 4 (B7: Yes), it performs the above steps S8 and S9 and ends the permission transfer determination process.

[0093] The above illustrates a structure in which the OTA master controller 14 configures the installer to the relay units 6-8 connected to it and performs a transfer of authority to the installer configured in the relay units 6-8. However, it is also possible to configure the installer at multiple levels and perform a transfer of authority to the installer at multiple levels. For example, in a structure where ECUs are hierarchically connected, the OTA master controller 14 can configure the installer to the ECU at the higher level and perform a transfer of authority to the installer configured in the higher level ECU, and then configure the installer from the higher level ECU to the lower level ECU and perform a transfer of authority to the installer configured in the lower level ECU.

[0094] As explained above, the following effects can be achieved according to the implementation method. In the OTA master controller 14, an installer for installing software to the target ECU is configured in relay units 6-8. In relay units 6-8, when the installer is configured from the OTA master controller 14, a transfer of authority to the configured installer is performed, and the software installation is instructed to be executed, the software installation to the target ECU is carried out. This appropriately reduces the constraints of the installer's configuration target and appropriately shortens the time required for installing the software to the target ECU, thus enabling appropriate software installation to the target ECU.

[0095] In OTA center 2, configuration target information for configuring the installer to relay devices 6-8 and diagnostic service information for installing software to the target ECU are distributed to OTA master controller 14. This enables OTA master controller 14 and relay devices 6-8 to properly install software to the target ECU.

[0096] In addition to the description of the scope of the patent claims, this disclosure includes the following disclosures. [1]

[0098] A main control device (14) performs diagnostic services.

[0099] A diagnostic client is configured on a relay device to enable the relay device to provide diagnostic services to the target device. The relay device is connected to the main control device in a manner that enables data communication. [2]

[0101] According to the master control device described in [1], the permission transfer to the diagnostic client configured in the relay device is performed, and the execution of the diagnostic service is instructed to the diagnostic client to which the permission transfer is targeted. [3]

[0103] According to the master control device described in [2], it waits for the completion notification of the execution of the diagnostic service from the relay device of the diagnostic client configured with the permission transfer target. [4]

[0105] According to [3], when the master control device receives a notification of completion of the diagnostic service from the relay device, it instructs the relay device to delete the diagnostic client. [5]

[0107] According to any one of [1] to [4], the master control device configures the diagnostic client on multiple relay devices, performs permission transfer to multiple diagnostic clients configured on the multiple relay devices, and instructs the execution of the diagnostic service in parallel to the multiple diagnostic clients to which the permission transfer is targeted. [6]

[0109] According to any one of [1] to [5], the main control device configures an installer for installing software on the software update target device as the diagnostic client in the relay device, and performs the installation of software on the update target device as the diagnostic service. [7]

[0111] A relay device (6-8) is capable of data communication with the main control device (14) that performs diagnostic services.

[0112] When a diagnostic client for performing the diagnostic service is configured from the main control device, and a transfer of permissions to the diagnostic client is performed and the execution of the diagnostic service is instructed, the diagnostic service is performed on the target device. [8]

[0114] According to the relay device described in [7], after completing the diagnostic service, it sends a notification of completion of the diagnostic service to the main control device. [9]

[0116] According to the relay device described in [7] or [8], the diagnostic client is deleted when the main control device instructs the deletion of the diagnostic client.

[10]

[0118] According to the relay device described in [9], after the deletion of the diagnostic client is completed, a notification that the deletion of the diagnostic client is completed is sent to the main control device.

[11]

[0120] An external device (2) is capable of data communication with the main control device (14) that performs diagnostic services.

[0121] The following information is distributed to the main control device: configuration target information for the main control device to determine the configuration target of the diagnostic client corresponding to the diagnostic service, and diagnostic service information for the main control device to perform the diagnostic service on the service target device.

[12]

[0123] According to the external device described in

[11] , permission transfer information is distributed to the master control device, which is used by the master control device to determine the permission transfer target of the diagnostic client.

[13]

[0125] According to the external device described in

[11] or

[12] , parallel execution information is distributed to the master control device for multiple diagnostic clients configured with different configuration targets to perform the diagnostic service in parallel.

[14]

[0127] The diagnostic client is distributed to the master control device according to any of the external devices described in

[11] to

[13] .

[15]

[0129] According to any one of the external devices described in

[11] to

[14] , as a diagnostic service, the specification data related to the software update of the target device is distributed to the main control device for software update.

[16]

[0131] A data communication system (1) includes a main control device (14) for performing diagnostic services and an external device (2) capable of data communication with the main control device.

[0132] The external device distributes the following information to the main control device: configuration target information for the main control device to determine the configuration target of the diagnostic client corresponding to the diagnostic service, and diagnostic service information for the main control device to provide the diagnostic service to the service target device.

[0133] The main control device configures the diagnostic client on the relay device based on the configuration target information received from the external device, and performs the diagnostic service to the service target device based on the diagnostic service information received from the external device.

[17]

[0135] According to the data communication system described in

[16] ,

[0136] The external device distributes permission transfer information to the main control device. This permission transfer information is used by the main control device to determine the permission transfer target to the diagnostic client.

[0137] The main control device transfers permissions to the diagnostic client based on the permission transfer information received from the external device, and instructs the diagnostic client to execute the diagnostic service.

[18]

[0139] According to the data communication system described in

[17] ,

[0140] The external device distributes parallel execution information to the main control device. This parallel execution information is used to enable multiple diagnostic clients configured with different configuration targets to perform the diagnostic service in parallel.

[0141] The master control device, based on the parallel execution information received from the external device, instructs multiple diagnostic clients of the permission transfer target to execute the diagnostic service in parallel.

[19]

[0143] According to any one of the data communication systems described in

[16] to

[18] ,

[0144] The external device distributes the diagnostic client to the main control device.

[0145] The master control device configures the diagnostic client received from the external device onto the relay device determined by the configuration target information.

[20]

[0147] According to any one of the data communication systems described in

[16] to

[19] ,

[0148] The main control device configures the software installer for the update target device as the diagnostic client in the relay device, and the main control device performs the installation of software to the update target device as the diagnostic service.

[0149] This disclosure is described with reference to embodiments, but it should be understood that this disclosure is not limited to those embodiments or constructions. This disclosure includes various modifications and equivalent variations. Furthermore, various combinations and methods, including only one of these elements, or other combinations and methods including more than one element or the following, are all within the scope and spirit of this disclosure.

[0150] The example of OTA Center 2 as an external device illustrates the case of wireless reprogramming, but it can also be applied to the case of wired reprogramming based on external tool 32 connected to CGW5 via a wired connection. Furthermore, the external device is not limited to OTA Center 2 or external tool 32; it can also be a portable information terminal such as a smartphone or tablet.

[0151] An example is shown in relays 6 to 8, where after the software installation to the target ECU is completed, the installer 18, OBC12, and specification data are deleted on the condition that a deletion instruction notification for the installer 18, OBC12, and specification data is received from the OTA master controller 4. However, it is also possible to delete the installer 18, OBC12, and specification data on the condition that the software installation to the target ECU is completed, without receiving a deletion instruction notification.

[0152] The example shows target ECUs 25-30 as software update targets, but relays 6-8 can also be included as software update targets.

[0153] The control unit and method described in this disclosure can also be implemented by a dedicated computer, which is provided by comprising a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the control unit and method described in this disclosure can also be implemented by a dedicated computer provided by comprising a processor composed of one or more dedicated hardware logic circuits. Alternatively, the control unit and method described in this disclosure can also be implemented by one or more dedicated computers, which are composed of a combination of a processor and memory programmed to perform one or more functions and a processor composed of one or more hardware logic circuits. Furthermore, the computer program can also be stored as instructions to be executed by the computer in a computer-readable non-volatile storage medium.

Claims

1. A master control device (14) for performing diagnostic services, characterized in that, A diagnostic client is configured on a relay device to enable the relay device to perform diagnostic services to the target device. The relay device is connected to the main control device in a manner that enables data communication.

2. The main control device according to claim 1, characterized in that, Perform a permission transfer to the diagnostic client configured on the relay device, and instruct the diagnostic client to perform the diagnostic service to the permission transfer target.

3. The main control device according to claim 2, characterized in that, Waiting for a notification of completion of the diagnostic service from the relay device of the diagnostic client configured with the permission transfer target.

4. The main control device according to claim 3, characterized in that, Upon receiving a notification from the relay device that the diagnostic service has been completed, the relay device is instructed to delete the diagnostic client.

5. The main control device according to claim 1, characterized in that, The diagnostic client is configured on multiple relay devices, and permissions are transferred to multiple diagnostic clients configured on the multiple relay devices. The execution of the diagnostic service is then instructed in parallel to the multiple diagnostic clients to which the permissions are transferred.

6. The main control device according to claim 1, characterized in that, An installer for installing software on the software update target device is configured as the diagnostic client in the relay device, and the software installation on the update target device is performed as the diagnostic service.

7. A relay device (6-8) capable of data communication with a master control device (14) providing diagnostic services, characterized in that, When a diagnostic client for performing the diagnostic service is configured from the main control device, and a transfer of permissions to the diagnostic client is performed and the execution of the diagnostic service is instructed, the diagnostic service is performed on the target device.

8. The relay device according to claim 7, characterized in that, Upon completion of the diagnostic service, a notification of completion of the diagnostic service is sent to the main control device.

9. The relay device according to claim 7, characterized in that, If the main control device instructs the deletion of the diagnostic client, the diagnostic client is deleted.

10. The relay device according to claim 9, characterized in that, Once the diagnostic client has been deleted, a notification indicating that the deletion of the diagnostic client is complete is sent to the main control device.

11. An external device (2) capable of data communication with a main control device (14) performing diagnostic services, characterized in that, The following information is distributed to the main control device: configuration target information for the main control device to determine the configuration target of the diagnostic client corresponding to the diagnostic service, and diagnostic service information for the main control device to perform the diagnostic service on the service target device.

12. The external device according to claim 11, characterized in that, The master control device distributes permission transfer information, which is used by the master control device to determine the permission transfer target of the diagnostic client.

13. The external device according to claim 11, characterized in that, The main control device distributes parallel execution information, which is used to enable multiple diagnostic clients configured with different configuration targets to perform the diagnostic service in parallel.

14. The external device according to claim 11, characterized in that, The diagnostic client is distributed to the main control device.

15. The external device according to claim 11, characterized in that, As part of the diagnostic service, the specification data related to the software update of the target device is distributed to the main control device.

16. A data communication system (1), comprising a main control device (14) for performing diagnostic services and an external device (2) capable of data communication with the main control device, characterized in that, The external device distributes the following information to the main control device: configuration target information for the main control device to determine the configuration target of the diagnostic client corresponding to the diagnostic service, and diagnostic service information for the main control device to provide the diagnostic service to the service target device. The main control device configures the diagnostic client on the relay device based on the configuration target information received from the external device, and performs the diagnostic service to the service target device based on the diagnostic service information received from the external device.

17. The data communication system according to claim 16, characterized in that, The external device distributes permission transfer information to the main control device. This permission transfer information is used by the main control device to determine the permission transfer target to the diagnostic client. The main control device transfers permissions to the diagnostic client based on the permission transfer information received from the external device, and instructs the diagnostic client to execute the diagnostic service.

18. The data communication system according to claim 17, characterized in that, The external device distributes parallel execution information to the main control device. This parallel execution information is used to enable multiple diagnostic clients configured with different configuration targets to perform the diagnostic service in parallel. The master control device, based on the parallel execution information received from the external device, instructs multiple diagnostic clients of the permission transfer target to execute the diagnostic service in parallel.

19. The data communication system according to claim 16, characterized in that, The external device distributes the diagnostic client to the main control device. The master control device configures the diagnostic client received from the external device onto the relay device determined by the configuration target information.

20. The data communication system according to claim 16, characterized in that, The main control device configures the software installer for the update target device as the diagnostic client in the relay device, and the main control device performs the installation of software to the update target device as the diagnostic service.

21. A data processing method, characterized in that, In the main control unit (14) that performs diagnostic services, The diagnostic client configuration step involves configuring the diagnostic client on the relay device. This diagnostic client enables the relay device to provide diagnostic services to the target device. The relay device is connected to the main control device in a manner that allows for data communication.

22. A data processing program, characterized in that, The main control unit (14) that performs diagnostic services shall execute: The diagnostic client configuration steps involve configuring the diagnostic client on the relay device. This diagnostic client is used to enable the relay device to perform diagnostic services to the target device. The relay device is connected to the main control device in a manner that enables data communication.

23. A data processing method, characterized in that, In the relay devices (6-8) that are capable of data communication with the main control device (14) performing diagnostic services, the following diagnostic service execution steps are performed: When a diagnostic client for performing the diagnostic service is configured from the main control device, and a transfer of permissions to the diagnostic client is performed and the execution of the diagnostic service is instructed, the diagnostic service is performed on the target device.

24. A data processing program, characterized in that, The relay devices (6-8) that are capable of data communication with the main control device (14) performing diagnostic services shall execute the following diagnostic service execution steps: When a diagnostic client for performing the diagnostic service is configured from the main control device, and a transfer of permissions to the diagnostic client is performed and the execution of the diagnostic service is instructed, the diagnostic service is performed on the target device.

25. A data processing method, characterized in that, In the external device (2) capable of data communication with the main control device (14) performing diagnostic services, a step is performed to distribute configuration target information and diagnostic service information to the main control device. The configuration target information is used by the main control device to determine the configuration target of the diagnostic client corresponding to the diagnostic service, and the diagnostic service information is used by the main control device to perform the diagnostic service to the service target device.

26. A data processing program, characterized in that, An external device (2) capable of data communication with the main control device (14) providing diagnostic services performs a distribution step of distributing configuration target information and diagnostic service information to the main control device. The configuration target information is used by the main control device to determine the configuration target of the diagnostic client corresponding to the diagnostic service, and the diagnostic service information is used by the main control device to perform the diagnostic service to the service target device.

Images