JP6954422B2 - Concurrency device, concurrency method and concurrency system - Google Patents

Description

The present invention relates to a parallel processing apparatus, a parallel processing method and a parallel processing system.

Conventionally, a processing device that connects an electronic control unit (hereinafter referred to as an ECU (Electronic Control Unit)) and receives processing requests of various independent applications such as a replog application, a failure diagnosis application, and a key management application for the ECU has been provided. (See, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2003-46536

When this type of processing device receives a processing request to the ECU, it executes processing according to the received processing request. In this case, the processing device sequentially executes one-to-one communication with the ECU that is the request destination of the processing request, and executes the processing in order according to the order in which the processing request is received. That is, when the processing device receives one processing request to the ECU, the processing device starts one processing in response to the received one processing request. When the processing device receives another processing request to the ECU before completing one processing, that is, while executing one processing, the processing device waits for the start of another processing according to the received other processing request. Then, when the processing device completes one process, the processing device starts another process waiting for the process.

On the other hand, in recent years, there is an increasing need to execute a plurality of processes by multitasking due to an increase in the program capacity of the ECU due to complicated control and a complicated system. However, in the configuration of waiting for the start of another process until the above-mentioned one process is completed, a plurality of processes cannot be executed by multitasking.

The present invention has been made in view of the above circumstances, and an object of the present invention is to multitask a plurality of processes corresponding to a plurality of received processing requests when a plurality of processing requests of independent applications are simultaneously received. It is an object of the present invention to provide a concurrency processing apparatus, a concurrency processing method, and a concurrency processing system that can be executed by.

According to the invention described in claim 1, the parallel processing device (3) is the first electronic control device and the second electronic control device (11a to 11c, 12a to 12c, 13a to 13c, 14a to 14a) which are the targets of the reprog. 14c) is connected to the data communication module that stores the replog data of the first electronic control device and the replog data of the second electronic control device via a bus (7 to 10).

The processing execution unit (31) transmits a data signal including the riplog data to the first electronic control device and the second electronic control device, and then the riplog response signal from the first electronic control device or the second electronic control device. Is transmitted to the data communication module by transmitting the request signal of the reprog data of the first electronic control device or the second electronic control device within the period until the first electronic control device and the second electronic control device are received. Even within the period from the reception of the riplog response signal from the data communication module to the transmission of the data signal including the riplog data to the first electronic control device or the second electronic control device, the first electronic control device is also used from the data communication module. Alternatively, a data signal including the replog data of the second electronic control device is received.

The figure which shows the structure of the whole system of one Embodiment Functional block diagram showing the configuration of the central gateway device Diagram showing the configuration of the client program Diagram showing the data hierarchy Diagram showing the transition of session state Flowchart showing the whole process The figure which shows the connection mode Sequence Diagram flowchart The figure which shows the connection mode Sequence Diagram flowchart The figure which shows the connection mode Sequence Diagram flowchart The figure which shows the connection mode Sequence Diagram flowchart flowchart The figure which shows the connection mode The figure which shows the connection mode Sequence Diagram Sequence Diagram Sequence Diagram Sequence Diagram Sequence Diagram Sequence Diagram

Hereinafter, an embodiment in which the present invention is applied to a parallel processing device mounted on a vehicle will be described with reference to the drawings.
The master electronic control unit (hereinafter referred to as a master ECU (Electronic Control Unit)) 1 includes a data communication module (hereinafter referred to as a DCM (Data Communication Module)) 2 and a central gateway device (hereinafter referred to as a CGW (Central Gate Way)). (Referred to as) 3 (corresponding to a parallel processing device).

The DCM2 controls data communication between the center 4, the user device 5, and the tool 6 via an external network. That is, the DCM2 controls data communication with the center 4 via a mobile communication network such as a 3G line or a 4G line. Further, the DCM2 controls data communication with the user device 5 via, for example, WiFi (registered trademark) or Bluetooth (registered trademark). Further, the DCM2 controls data communication with the tool 6, for example, by a wired connection. When the DCM2 receives an application from the center 4, the user device 5, the tool 6, or the like, the DCM2 transmits the received application to the CGW 3. For example, when the user operates the tool 6 to start the replog application, the DCM2 receives the replog application from the tool 6 and transmits the received replog application to the CGW 3. Further, for example, when the user operates the tool 6 to activate the failure diagnosis application, the DCM2 receives the failure diagnosis application from the tool 6 and transmits the received failure diagnosis application to the CGW 3.

When the CGW 3 receives the application from the DCM2, the CGW 3 accepts the processing request of the application. When the CGW 3 receives the replog application from, for example, the DCM2, the CGW 3 accepts the processing request of the replog application. Further, when the CGW 3 receives the failure diagnosis application from, for example, the DCM2, the CGW 3 receives the processing request of the failure diagnosis application.

The CGW 3 connects a plurality of buses 7 to 10 and controls data communication with the ECU mounted on the vehicle via the buses 7 to 10. Buses 7 to 10 include, for example, a multimedia bus, a power train bus, a body bus, an environmental bus, a chassis bus, and the like. Buses 7 to 10 include, for example, CAN (Controller Area Network) (registered trademark), LIN (Local Interconnect Network) (registered trademark), CXPI (Clock Extension Peripheral Interface) (registered trademark), FlexRay (registered trademark), MOST (Media). Oriented Systems Transport) (registered trademark), etc., communication protocols are different from each other, and communication speed and signal format are different from each other.

ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c are connected to buses 7 to 10, respectively. For example, a navigation ECU that controls navigation, an ETC ECU that controls communication with an electronic toll collection system (ETC: Electronic Toll Collection System: registered trademark), and the like are connected to a multimedia bus. For example, an engine ECU that controls an engine, a brake ECU that controls a brake, an ECT ECU that controls an automatic transmission, a power steering ECU that controls power steering, and the like are connected to a power steering bus. For example, a door ECU that controls door lock / unlock, a meter ECU that controls meter display, an air conditioner ECU that controls an air conditioner, a window ECU that controls window opening / closing, and the like are connected to a body bus. ing.

As shown in FIG. 2, the CGW 3 includes a microcomputer (hereinafter referred to as a microcomputer) 15, a transceiver 16, and a power supply circuit 17. In the microcomputer 15, the CPU 18, the ROM 19 as a non-transitional recording medium, the RAM 20, and the flash memory 21 are interconnected via an internal bus 22. In the microcomputer 15, the CPU 18 executes a control program stored in the ROM 19 to control the operation of the CGW 3. The transceiver 16 controls the data communication with the DCM2 by the instruction from the microcomputer 15, and also controls the data communication with the ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c via the buses 7 to 10. .. The power supply circuit 17 inputs an accessory signal indicating on / off of the accessory switch and an ignition signal indicating on / off of the ignition switch. When the power supply circuit 17 detects, for example, switching from off to on of the accessory signal, it generates operating power from the power supplied from the battery power supply, and supplies the generated operating power to the microcomputer 15 and the transceiver 16.

The ROM 19 stores a client program as one of the control programs. As shown in FIG. 3, the client program 23 includes a parallel processing program, and as a function of storing various data, the management information master data storage unit 24 for storing the management information master data and the management information for storing the management information bus master data. It has a bus master data storage unit 25 and a management information data storage unit 26 for storing management information data. The management information master data storage unit 24 stores data related to the communication speed of buses 7 to 10, data related to scheduling adjustment, and the like as management information master data. The management information bus master data storage unit 25 stores data related to ECUs 11a to 11c, 12a to 12c, 13a to 13c, 14a to 14c to which management information data has been assigned, data related to bus load adjustment, and the like as management information bus master data. There is. The management information data storage unit 26 includes data regarding the priority of the processing request being accepted, data regarding the status of the buses 7 to 10, data regarding the status of the ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c, and processing. Data related to the progress status, data related to the session status of processing, etc. are stored as management information data. As shown in FIG. 4, the client program 23 manages the management information master data, the management information bus master data, and the management information data in a hierarchical manner.

Further, the client program 23 includes a processing request reception unit 27, a management information master update unit 28, a management information bus master update unit 29, a management information allocation unit 30, a processing execution unit 31, a scheduling adjustment unit 32, a bus load adjustment unit 33, and progress. It has a state determination unit 34 and a session state determination unit 35.

The processing request receiving unit 27 receives processing requests of independent applications for ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c. The application for which the processing request receiving unit 27 receives the processing request is, for example, a riplog application, a failure diagnosis application, a key management application, or the like. The management information master update unit 28 and the management information bus master update unit 29 have the states of the buses 7 to 10 and the ECUs 11a to 11c, 12a to 12c, 13a to 13c, which change according to the processing execution unit 31, respectively. The statuses of 14a to 14c are monitored, and the management information master data and the management information bus master data are updated as the status changes. The management information allocation unit 30 refers to the management information master data and the management information bus master data, and allocates the management information data to the processing request.

The process execution unit 31 refers to the management information master data, the management information bus master data, and the management information data, and mediates the processing requests of a plurality of applications. That is, when the processing execution unit 33 receives the processing request of another application while accepting the processing request of one application, the priority of the processing request of one application and the processing request of another application, and the processing request of another application at that time. The state of the buses 7 to 10 and the states of the ECUs 11a to 11c, 12a to 12c, 13a to 13c, 14a to 14c, etc. are determined, and the processing request of one application and the processing request of another application are arbitrated. For example, if the processing request of one application has a higher priority than the processing request of another application, the processing execution unit 31 mediates so as to give priority to the processing according to the processing request of one application. On the contrary, the processing execution unit 31 arbitrates so that, for example, if the processing request of another application has a higher priority than the processing request of one application, the processing corresponding to the processing request of another application is prioritized. .. Further, the process execution unit 31 arbitrates so as to execute the process if the load of the ECU or the load of the bus, which is the request destination of the process request, is relatively low, and to wait for the execution of the process if the load is relatively high.

The scheduling adjustment unit 32 adjusts the scheduling by using the data related to the adjustment of the scheduling stored in the management information master data storage unit 24. The scheduling adjustment unit 32 adjusts, for example, a signal transmission interval as scheduling adjustment. The bus load adjusting unit 33 adjusts the bus load by using the data related to the bus load adjustment stored in the management information bus master data storage unit 25. The bus load adjusting unit 33 adjusts the data communication amount of the bus as the adjustment of the bus load. The progress status determination unit 34 determines the progress status of the process by using the data related to the progress status stored in the management information data storage unit 26. The session state determination unit 35 determines the session state of processing by using the data related to the session state stored in the management information data storage unit 26.

When the processing execution unit 31 arbitrates the processing requests of a plurality of applications, the progress determined by the progress status determination unit 34 according to the scheduling adjusted by the scheduling adjustment unit 32 and the bus load adjusted by the bus load adjustment unit 33. A plurality of processes are performed in parallel while monitoring the session state determined by the state and session state determination unit 35.

Here, the reason for monitoring the session status will be described. As shown in FIG. 5, when the ECU receives the session transition request signal in the normal state, it shifts from the normal state to the failure diagnosis state, but after that, the time during which the failure diagnosis request signal is not received is a predetermined time (for example). (5 seconds) If it continues, a timeout will occur and the failure diagnosis state will be restored from the normal state. Under these circumstances, the client program 23 periodically transmits the session transition request signal to the ECU to maintain the ECU in the failure diagnosis state even if the interval for transmitting the failure diagnosis request signal exceeds a predetermined time. Is possible.

Further, when the ECU receives the session transition request signal while in the failure diagnosis state, the ECU shifts from the failure diagnosis state to the replog state, but after that, the time during which the data signal including the replog data is not received is a predetermined time (for example, 5 seconds). ) If it continues, a timeout will occur and the replog state will return to the normal state. Under these circumstances, the client program 23 periodically transmits a session transition request signal to the ECU to maintain the ECU in the replog state even if the interval for transmitting the data signal including the replog data exceeds a predetermined time. It becomes possible.

Next, the operation of the above configuration will be described with reference to FIGS. 6 to 27.
In the CGW 3, the microcomputer 15 performs the following control by executing the client program 23 by the CPU 18.

When the processing request receiving unit 24 receives the processing request of the application (S1, the processing request receiving procedure), the microcomputer 15 mediates the processing request of the received application (S2, the arbitration procedure). That is, the microcomputer 15 uses data on the priority of the processing request of the application being accepted, data on the status of the buses 7 to 10, and data on the status of the ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c. It is determined whether or not the processing according to the received processing request can be executed, and the processing request of the application is arbitrated. When the microcomputer 15 determines whether or not the application conflict has been avoided by arbitrating the processing request of the received application (S3), and determines that the application conflict has been avoided (S3: YES), the management information data. Is assigned to the processing request (S4).

When the management information data is assigned to the processing request, the microcomputer 15 updates the management information master data (S5). The microcomputer 15 adjusts the scheduling of a plurality of processes in response to the plurality of processing requests (S6), and updates the management information bus master data when the scheduling of the plurality of processes is adjusted (S7). The microcomputer 15 calculates the bus load (S8), monitors the bus load (S9), and adjusts the transmission interval of the signal to be transmitted to the ECU of the request destination of the processing request (S10). Then, the microcomputer 15 performs a plurality of processes in parallel while monitoring the progress state and the session state (S11, process parallel procedure).

Hereinafter, as the connection mode of the ECU, when a plurality of processing requests for the same ECU connected to the bus are simultaneously received, and when a plurality of processing requests for a plurality of ECUs connected to the same bus are simultaneously received. A case where a plurality of processing requests for a plurality of electronic control units connected to different buses are received at the same time will be described.

(1) When a plurality of processing requests for the same ECU connected to the bus are received at the same time As shown in FIG. 7, in the microcomputer 15, the CGW 3 connects the bus 41 and the engine ECU 51 is connected to the bus 41. When the processing request of the replog application and the processing request of the failure diagnosis application for the engine ECU 51 are simultaneously received, the processing request is arbitrated, and as shown in FIG. 8, the transmission of the data signal including the riplog data and the failure diagnosis are performed. Parallel to the transmission of the request signal. In this case, "accept at the same time" means that the processing request of the failure diagnosis application is received while the reprog processing according to the processing request of the reprolog application is being executed, or the failure diagnosis processing according to the processing request of the failure diagnosis application is being executed. It means when the processing request of the replog application is accepted.

The microcomputer 15 does not interfere with the load of the engine ECU 51 and the load of the bus 41 even if the failure diagnosis request signal is transmitted within the period from the transmission of the data signal including the replog data to the reception of the replog response signal (the load of the engine ECU 51 and the load of the bus 41 are not hindered). For example, it does not interfere with other processing or other bus communication), and a failure diagnosis request signal is transmitted within that period. Further, the microcomputer 15 transmits the data signal including the reprog data within the period from the transmission of the failure diagnosis request signal to the reception of the data signal including the failure diagnosis data (for example, various data such as the DTC code). If it is determined that there is no problem with the load of the engine ECU 51 and the load of the bus 41, a data signal including riplog data is transmitted within that period. In this way, the microcomputer 15 executes the reprog processing and the failure diagnosis processing for the engine ECU 51 by multitasking. That is, the microcomputer 15 multitasks the reprog processing and the failure diagnosis processing for the engine ECU 51 according to the load of the engine ECU 51 and the load of the bus 41, instead of waiting for the completion of one processing and starting the other processing. By executing it as a task, it is possible to shorten the time required to complete those processes.

As shown in FIG. 9, the microcomputer 15 performs the reprog entry process (S21), the erasure of the data stored in the flash memory of the engine ECU 51 (S22), and the data signal including the reprog data as the reprog process for the engine ECU 51. Transmission (S23), reception of the replog response signal (S24), verification of the replog (S25), and initialization of the engine ECU 51 (S26) are executed. Further, the microcomputer 15 executes the transmission of the failure diagnosis request signal (S31) and the reception of the data signal including the failure diagnosis data (S32) as the failure diagnosis process for the engine ECU 51.

Further, the microcomputer 15 may receive the replog data from the DCM2 in parallel in addition to the transmission of the data signal including the replog data and the transmission of the failure diagnosis request signal. That is, as shown in FIG. 10, when the replog data of the engine ECU 51 is stored in the DCM2, as shown in FIG. 11, the microcomputer 15 transmits, for example, a failure diagnosis request signal and then responds to the replog. The request signal of the reprog data is transmitted to the DCM2 within the period until the signal is received, and the reprog data is transmitted from the DCM2 within the period from the reception of the data signal including the failure diagnosis data to the transmission of the data signal including the reprog data. Receives a data signal containing.

In this way, the microcomputer 15 multitasks the replog processing in response to the processing request of the replog application to the engine ECU 51, the failure diagnosis processing in response to the processing request of the failure diagnosis application, and the processing of acquiring the replog data from the DCM2. Run. As shown in FIG. 12, the microcomputer 15 executes the transmission of the data request signal (S41) and the acquisition of the data signal including the replog data (S42) as the acquisition process of the replog data.

In such a configuration, in the CGW 3, since the replog data acquired from the DCM2 is transmitted to the engine ECU 51, the capacity of the storage medium for storing the replog data to be transmitted to the engine ECU 51 can be reduced. The timing of transmitting the data request signal to the DCM2 and the timing of receiving the data signal including the reprog data from the DCM2 may be any timing. Further, the above has illustrated the case where two processing requests to the engine ECU 51 are received at the same time, but the same applies to the case where three or more processing requests to the engine ECU 51 are received at the same time.

(2) When a plurality of processing requests for a plurality of ECUs connected to the same bus are simultaneously received. As shown in FIG. 13, in the microcomputer 15, the CGW 3 connects the bus 42, and the engine ECU 52 and the meter are connected to the bus 42. When the ECU 53 is connected and the processing request of the replog application for the engine ECU 52 and the processing request of the replog application for the meter ECU 53 are simultaneously received, those processing requests are arbitrated, and as shown in FIG. 14, the engine ECU 52 The transmission of the data signal including the replog data and the transmission of the data signal including the replog data of the meter ECU 53 are performed in parallel. In this case, "accepting at the same time" means that the processing request of the replog application to the meter ECU 53 is received while the replog processing corresponding to the processing request of the replog application to the engine ECU 52 is being executed, or the processing request of the replog application to the meter ECU 53 is accepted. This means that a processing request of the replog application to the engine ECU 52 is received while the replog processing is being executed.

Even if the microcomputer 15 transmits the data signal including the replog data of the meter ECU 53 within the period from the transmission of the data signal including the replog data of the engine ECU 52 to the reception of the replog response signal, the load and the bus of the meter ECU 53 If it is determined that the load of 42 is not hindered, a data signal including the replog data of the meter ECU 53 is transmitted within that period. Further, even if the microcomputer 15 transmits the data signal including the replog data of the engine ECU 52 within the period from the transmission of the data signal including the replog data of the meter ECU 53 to the reception of the replog response signal, the load on the engine ECU 52 If it is determined that the load on the bus 42 is not hindered, a data signal including the replog data of the engine ECU 52 is transmitted within that period.

In this way, the microcomputer 15 executes the replog processing for the engine ECU 52 and the replog processing for the meter ECU 53 in a multitasking manner. That is, the microcomputer 15 does not start the reprog processing for the engine ECU 52 and the reprog processing for the meter ECU 53 after waiting for the completion of one process, but starts the other process, but the load of the engine ECU 52, the load of the meter ECU 53, and the bus. By executing multitasking according to the load of 42, it is possible to shorten the time required to complete those processes.

As shown in FIG. 15, the microcomputer 15 performs a replog entry process (S51), an erasure of data stored in the flash memory of the engine ECU 52 (S52), and a data signal including the replog data as the replog process for the engine ECU 52. Transmission (S53), reception of the replog response signal (S54), verification of the replog (S55), and initialization of the engine ECU 52 (S56) are executed. Further, as the replog processing for the meter ECU 53, the microcomputer 15 includes a replog entry process (S61), erasure of data stored in the flash memory of the meter ECU 53 (S62), and transmission of a data signal including the replog data (S63). The reception of the replog response signal (S64), the verification of the replog (S65), and the initialization of the meter ECU 53 (S66) are executed.

In this case as well, the microcomputer 15 may receive the replog data from the DCM2 in parallel in addition to transmitting the data signal including the replog data. That is, as shown in FIG. 16, when the replog data of the engine ECU 52 and the replog data of the meter ECU 53 are stored in the DCM2, the microcomputer 15 relates to the engine ECU 52 as shown in FIGS. 17 to 19. The replog processing, the replog processing for the meter ECU 53, and the acquisition processing of the replog data may be performed in parallel. As shown in FIG. 18, the microcomputer 15 executes a data request signal transmission (S71) and a data signal acquisition including the replog data (S72) as a process of acquiring the replog data of the engine ECU 52. As shown in FIG. 19, the microcomputer 15 executes a data request signal transmission (S81) and a data signal acquisition including the replog data (S82) as a process of acquiring the replog data of the meter ECU 53.

Even with such a configuration, in the CGW 3, the replog data of the engine ECU 52 acquired from the DCM2 is transmitted to the engine ECU 52, and the replog data of the meter ECU 53 acquired from the DCM2 is transmitted to the meter ECU 53. And the capacity of the storage medium for storing the reprog data to be transmitted to the meter ECU 53 can be reduced. Also in this case, the timing of transmitting the data request signal to the DCM2 and the timing of receiving the data signal including the reprog data from the DCM2 may be any timing. Further, the above has illustrated the case where two processing requests for two ECUs 52 and 53 connected to the same bus 42 are simultaneously received, but three or more processing requests for three or more ECUs are simultaneously received. The same applies to the case.

(3) A case where a plurality of processing requests for a plurality of ECUs connected to different buses are received at the same time will be described.
As shown in FIG. 20, in the microcomputer 15, the CGW 3 connects the first bus 43 and the second bus 43, the engine ECU 54 is connected to the first bus 43, and the meter ECU 55 is connected to the second bus 44. Is connected, and when the processing request of the replog application for the engine ECU 54 and the processing request of the replog application for the meter ECU 55 are simultaneously received, those processing requests are arbitrated, and as shown in FIG. 20, the replog data of the engine ECU 54. The transmission of the data signal including the above and the transmission of the data signal including the replog data of the meter ECU 55 are performed in parallel. In this case, since the engine ECU 54 and the meter ECU 55 are connected to separate buses, the microcomputer 15 determines the communication speed of the bus, transmits a data signal including the reprog data of the engine ECU 54, and transmits the data signal of the meter ECU 55. Parallel transmission of data signals including riplog data.

In this case as well, as shown in FIG. 21, the microcomputer 15 may perform the replog processing for the engine ECU 54, the replog processing for the meter ECU 55, and the replog data acquisition processing in parallel. In the above, the case where two processing requests for two ECUs 54 and 55 separately connected to the two buses 43 and 44 are received at the same time is illustrated, but the two buses are connected separately to three or more buses. The same applies when three or more processing requests to the three or more ECUs are received at the same time.

Next, the key management application will be described with reference to FIGS. 22 to 27. Here, a case where the CGW 3 distributes the key to the engine ECU 62 and the meter ECU 63 will be described. The engine ECU 62 and the meter ECU 63 may be connected to the same bus or may be connected to different buses. As shown in FIG. 22, the key management application includes a key generation phase, a key distribution phase, a key confirmation phase, a key center notification phase, and a DTC verification phase.

In the key generation phase, the factory tool 61 may generate the key or the CGW 3 may generate the key. When the factory tool 61 generates a key, as shown in FIG. 23, when the factory tool 61 generates a key, the factory tool 61 transmits a key information signal including key information that can identify the generated key to the CGW 3. In CGW3, when the microcomputer 15 receives the key information signal from the factory tool 61, the microcomputer 15 identifies the key from the key information included in the received key information signal, stores the specified key, and sends the response signal to the factory tool 61. Send. When the CGW 3 generates a key, the factory tool 61 transmits a key generation instruction signal to the CGW 3, as shown in FIG. 24. In the CGW 3, when the microcomputer 15 receives the key generation instruction signal from the factory tool 61, it generates a key, stores the generated key, and transmits a response signal to the factory tool 61.

In the key distribution phase, as shown in FIG. 25, the factory tool 61 transmits a key writing instruction signal to the CGW 3. In the CGW 3, when the microcomputer 15 receives the key writing instruction signal from the factory tool 61, it reads out the stored key and transmits the key writing request signal including the read key to the engine ECU 62 and the meter ECU 63. The microcomputer 15 transmits the key writing request signal to the engine ECU 62 and the meter ECU 63 in parallel. When the engine ECU 62 and the meter ECU 63 each receive the key write request signal from the CGW 3, the engine ECU 62 and the meter ECU 63 acquire and store the key included in the received key write request signal, and transmit the key write response signal to the CGW 3. In this way, the microcomputer 15 executes the key distribution process to the engine ECU 62 and the key distribution process to the meter ECU 63 in a multitasking manner. That is, the microcomputer 15 does not start the key distribution process to the engine ECU 62 and the key distribution process to the meter ECU 63 after waiting for the completion of one process, but starts the other process, but the load of the engine ECU 62 and the meter ECU 63. By executing multitasking according to the load of the bus and the load of the bus, it is possible to shorten the time required to complete those processes.

The key confirmation phase may be a case where the CGW 3 confirms the key or a case where the factory tool 61 confirms the key in the subsequent DTC verification phase. When the CGW 3 confirms the key, as shown in FIG. 26, in the CGW 3, the microcomputer 15 transmits a check value request signal to the engine ECU 62. When the engine ECU 62 receives the check value request signal from the CGW 3, it generates a check value and transmits the check value signal including the generated check value to the CGW 3. When the microcomputer 15 receives the check value signal from the engine ECU 62 in the CGW 3, the microcomputer 15 determines the check value included in the received check value signal and confirms whether or not the writing of the key to the engine ECU 62 is normally completed. do. When the microcomputer 15 completes the confirmation of whether or not the key writing to the engine ECU 62 is normally completed, the microcomputer 15 transmits a check value request signal to the meter ECU 63, and normally completes the key writing to the meter ECU 63. Check if it is present or not according to the same procedure.

When the factory tool 61 confirms the key in the DTC verification phase in the subsequent stage, the factory tool 61 transmits a check instruction signal to the CGW 3, as shown in FIG. 27. In the CGW 3, when the microcomputer 15 receives the check instruction signal from the factory tool 61, the microcomputer 15 transmits the check request signal to the engine ECU 62. When the engine ECU 62 receives the check request signal from the CGW 3, it confirms whether or not the key writing is normally completed, stores the confirmation result, and transmits the check response signal to the CGW 3. In the CGW 3, when the microcomputer 15 receives the check response signal from the engine ECU 62, the microcomputer 15 transmits a check request signal to the meter ECU 63, and confirms whether or not the writing of the key to the meter ECU 63 is normally completed in the same procedure. Therefore, do so. After that, in the DTC verification phase, the factory tool 61 transmits a DTC request to the engine ECU 62, receives a DTC response including the confirmation result from the engine ECU 62, determines the confirmation result included in the received DTC response, and determines the engine. It is confirmed whether or not the writing of the key to the ECU 62 is completed normally. When the factory tool 61 completes the confirmation of whether or not the writing of the key to the engine ECU 62 is completed normally, the factory tool 61 transmits a DTC request to the meter ECU 63 and confirms whether or not the writing of the key to the meter ECU 63 is normally completed. Confirm whether or not it is performed according to the same procedure.

As described above, according to the present embodiment, the following effects can be obtained.
When the CGW3 simultaneously receives processing requests of independent applications for ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c, a plurality of processing requests being accepted are arbitrated, and a plurality of processing requests corresponding to the plurality of processing requests are arbitrated. Processed in parallel. As a result, when a plurality of processing requests of independent applications are received at the same time, a plurality of processes corresponding to the received multiple processing requests can be executed by multitasking.

Further, in CGW3, a plurality of processes corresponding to a plurality of processing requests and a process of acquiring riplog data from DCM2 are performed in parallel. As a result, the replog data can be acquired from the DCM2, and the acquired replog data can be transmitted to the ECUs 11a to 11c, 12a to 12c, 13a to 13c, 14a to 14c, and is a storage medium for storing the replog data. Capacity can be reduced.

Further, in the CGW 3, a plurality of processes are used by using the data regarding the priority of the processing request being accepted, the data regarding the status of the buses 7 to 10, and the data regarding the status of the ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c. Made to arbitrate requests. A plurality of processing requests can be arbitrated using the priority of the processing request being accepted, the status of the buses 7 to 10, and the status of the ECUs 11a to 11c, 12a to 12c, 13a to 13c, and 14a to 14c as indexes.

Further, in CGW3, a plurality of processes are performed in parallel while monitoring the progress status and session status of the processes. It is possible to execute multiple processes by multitasking while appropriately responding to changes in the progress status and session status of the processes.

The present disclosure has been described in accordance with the examples, but it is understood that the present disclosure is not limited to the examples and structures. The present disclosure also includes various modifications and modifications within a uniform range. In addition, various combinations and forms, as well as other combinations and forms containing only one element, more or less, are also within the scope of the present disclosure.
It may be configured to accept applications other than the replog application, the failure diagnosis application, and the key management application.

Although the configuration in which the replog data is stored in the DCM2 is illustrated, the configuration is such that a storage device is provided separately from the DCM2, the replog data is stored in the storage device, and the process of acquiring the replog data from the storage device is performed in parallel. Is also good.

In the drawing, 3 is a central gateway device (parallel processing device), 7 to 10 is a bus, 11a to 11c, 12a to 12c, 13a to 13c, 14a to 14c are electronic control devices, 27 is a processing request receiving unit, and 31 is processing. The execution unit, 32 is a scheduling adjustment unit, 33 is a bus load adjustment unit, 34 is a progress status determination unit, and 35 is a session status determination unit.

Claims (3)

The first electronic control device and the second electronic control device (11a to 11c, 12a to 12c, 13a to 13c, 14a to 14c) which are the targets of the riplog, the riplog data of the first electronic control device, and the second electronic control. A data communication module that stores the replog data of the device and a parallel processing device (3) connected via a bus (7 to 10).
Within the period from the transmission of the data signal including the riplog data to the first electronic control device and the second electronic control device to the reception of the riplog response signal from the first electronic control device or the second electronic control device. , The request signal of the replog data of the first electronic control device or the second electronic control device is transmitted to the data communication module, and the replog response signal is received from the first electronic control device and the second electronic control device. From the data communication module to the first electronic control device or the second electronic control device even within the period from the data communication module to the transmission of the data signal including the riplog data to the first electronic control device or the second electronic control device. A parallel processing device having a processing execution unit (31) for receiving a data signal including riplog data. The first electronic control device and the second electronic control device (11a to 11c, 12a to 12c, 13a to 13c, 14a to 14c) which are the targets of the riplog, the riplog data of the first electronic control device, and the second electronic control. In a method in which a data communication module that stores replog data of an apparatus and a parallel processing apparatus (3) connected via a bus (7 to 10) transmit and receive signals.
Within the period from the transmission of the data signal including the riplog data to the first electronic control device and the second electronic control device to the reception of the riplog response signal from the first electronic control device or the second electronic control device. , The request signal of the replog data of the first electronic control device or the second electronic control device is transmitted to the data communication module, and the replog response signal is received from the first electronic control device and the second electronic control device. From the data communication module to the first electronic control device or the second electronic control device even within the period from the data communication module to the transmission of the data signal including the riplog data to the first electronic control device or the second electronic control device. A parallel processing method that receives a data signal containing riplog data. The first electronic control device and the second electronic control device (11a to 11c, 12a to 12c, 13a to 13c, 14a to 14c), which are the targets of the replog,
A data communication module (2) that stores the replog data of the first electronic control device and the replog data of the second electronic control device, and
Via said bus (7-10) the first electronic control unit, said second electronic control unit, and the parallel processing apparatus connected to the data communication module and (3), a parallel processing system comprising,
The parallel processing device transmits a data signal including riplog data to the first electronic control device and the second electronic control device, and then receives a riplog response signal from the first electronic control device or the second electronic control device. Within the period until the above, the request signal of the replog data of the first electronic control device or the second electronic control device is transmitted to the data communication module, and the riplog is transmitted from the first electronic control device and the second electronic control device. Even within the period from the reception of the response signal to the transmission of the data signal including the riplog data to the first electronic control device or the second electronic control device, the first electronic control device or the first electronic control device or the said A parallel processing system that receives a data signal including replog data of the second electronic control unit.

Images