JP2008078769A - Communicating system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a proper period to be set with respect to a time-out period of waiting for reception. <P>SOLUTION: In a communication system having a plurality of ECUs (Electronic Control Units) connected to an in-vehicle LAN, a remote operation accepting ECU communicates with slave ECUs such as a collating ECU and a body ECU to perform processing relating to remote operations such as door locking/unlocking, in cooperation with other ECUs. On reception of request data from the remote operation accepting ECU, each slave ECU transmits acceptance response data wherein information showing a maximum execution period required for the completion of processing (door locking/unlocking processing or the like) requested by the request data is stored, to a request source ECU before transmitting completion response data showing an execution result of the processing. Meanwhile, on reception of the acceptance response data, the remote operation accepting ECU sets a period corresponding to the maximum execution period of the requested processing, as the time-out period of a reception waiting operation relating to the completion response data, on the basis of information of the maximum execution period shown by the acceptance response data (S250). <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention is a communication system in which a plurality of electronic control devices are connected to a network, and at least one of the plurality of electronic control devices communicates with other electronic control devices in the network. The present invention relates to a communication system that realizes a series of processes in cooperation with the electronic control unit.

  2. Description of the Related Art Conventionally, as a communication system, an in-vehicle LAN system in which a plurality of electronic control devices are connected to a network and a plurality of electronic control devices are operated in cooperation to realize vehicle control is known. .

  In this type of communication system, a node that receives a request signal transmits a response signal to the request signal to a node that has transmitted the request signal, whereby information is exchanged between the nodes, and a series of processes is performed. Is realized.

  Further, in this type of communication system, a time-out process is performed for the response signal reception waiting operation at the request signal transmission source node in case the response signal does not reach the request signal transmission source node. Is common.

  In addition, as a method for setting the timeout time, in order to set an appropriate timeout time according to the network traffic and the processing load on the request signal receiving node, the response signal is received when the previous request signal is transmitted. A method is known in which whether or not it has succeeded is recorded, and when the next request signal is transmitted, the timeout time is changed depending on whether or not the response signal has been successfully received last time (for example, Patent Document 1). reference).

When setting the timeout time for the reception waiting operation, if the timeout time is set redundantly, error processing cannot be executed until the timeout time elapses. It becomes impossible to execute quickly. On the other hand, if the timeout time is set too short, the response signal cannot be received before the timeout time elapses, and useless error processing is frequently executed at the request signal transmission source node. The above setting method is for solving this type of problem.
JP 2002-26908 A

  By the way, in the automobile field, functions related to vehicle control are subdivided, and each subdivided function is realized by an individual electronic control device. Is being made common regardless of the vehicle type.

  However, when the electronic control device is shared in this way and the combination of the electronic control devices is changed according to the vehicle type to configure the in-vehicle LAN system, the request signal transmission source electronic control device is the same electronic control. Even in the case of the device, an in-vehicle LAN system is constructed in which the electronic control devices on the request signal receiving side are not the same.

  Therefore, in the case where the request control signal transmission source electronic control device is made common regardless of the vehicle type, among the electronic control devices combined with this electronic control device, the electronic control device that requires the most time to transmit the response signal. In addition, it is necessary to set a timeout period for the reception waiting operation. For this reason, when the requesting signal transmission source electronic control device is made common regardless of the vehicle type, there is a problem that the time-out time tends to be long and the error processing cannot be executed quickly.

  In addition, when the electronic control device on the request signal receiving side is configured to accept a plurality of types of request signals and when the electronic control device is to execute a plurality of types of processing, the processing is completed for each processing. Since the time is different, even if a request signal is transmitted, the time until the response signal indicating the execution result of the process is transmitted from the electronic control unit on the request signal reception side as the response signal of the request signal There is a problem that it is difficult to set an appropriate time as a timeout time in the electronic control device that is a request signal transmission source.

That is, there is a problem that error processing cannot be executed quickly if a timeout time is set in accordance with the processing that takes the longest time to complete the processing.
The present invention has been made in view of such problems, and provides a communication system capable of setting an appropriate time for the timeout time of the reception waiting operation in accordance with the processing operation of the electronic control device on the request signal receiving side. The purpose is to provide.

  A communication system according to claim 1, which is made to achieve the above object, includes a plurality of electronic control devices connected to a network, and at least one of the electronic control devices A is connected to the network. A series of processing is realized by communicating with another electronic control device B and cooperating with the electronic control device B.

  In this communication system, when the electronic control unit B receives a request signal requesting execution of processing from the electronic control unit A, the electronic control unit B determines the time required until the processing requested by the request signal is completed by the reception response unit. An acknowledgment response signal indicating that the request is accepted is transmitted to the request signal transmission source device.

  Further, when the request signal is received, the process execution means executes the process requested by the request signal. When this process is completed, the completion response means indicates that the process corresponding to the request signal is completed. A completion response signal, which is a response signal and stores information representing the execution result of the process, is transmitted to the request signal transmission source device.

  On the other hand, in response to the occurrence of the event, the electronic control unit A transmits a request signal for requesting execution of the process corresponding to the generated event to the electronic control unit B capable of executing the process, and receives the request signal. The processing means receives a completion response signal corresponding to the request signal from the electronic control unit B, and executes processing corresponding to the event based on the completion response signal. Further, upon reception of the completion response signal, a corresponding completion response signal is sent from the time-out time setting means to the reception processing means based on the information indicating the required time stored in the reception response signal received from the electronic control unit B. Set the timeout period for the reception waiting operation.

  That is, in this communication system, the request signal transmission source electronic control unit A obtains a predicted value of the time required to execute the processing corresponding to the request from the request signal receiving side electronic control unit B, and based on this time Set the timeout period for the reception waiting operation.

  Therefore, according to this communication system, the time-out time is appropriately set according to the processing operation (processing contents) of the electronic control device B as the request signal transmission destination regardless of the type of the electronic control device B as the request signal transmission destination. can do. Further, according to this communication system, an appropriate timeout time can be set individually for each process executed by the electronic control device B that is the request signal transmission destination. As a result, according to this communication system, when the execution result of the process cannot be obtained from the electronic control apparatus B, the electronic control apparatus A can execute the error process quickly. Further, since the timeout time is too short, it is possible to prevent the electronic control device A from frequently performing unnecessary error processing.

  Note that the electronic control device A that is the request signal transmission source cannot receive the completion response signal corresponding to the request signal in the period until the timeout time set by the timeout time setting means elapses. The error processing can be configured to be executed. Specifically, the error process can include a retry process including a procedure for retrying acquisition of the completion response signal.

  Retry processing including a procedure for retrying acquisition of a completion response signal when the completion response signal corresponding to the request signal cannot be received in the period until the timeout time set by the timeout time setting means elapses If the reception processing means is configured to execute the request signal, the request signal transmission source electronic control device cannot receive a response signal from the request signal transmission destination electronic control device due to the influence of noise or the like. In this case, the acquisition of the completion response signal can be retried quickly.

  Specifically, as the retry processing, the reception processing means completes when it cannot receive the completion response signal corresponding to the request signal in the period until the timeout time set by the timeout time setting means elapses. A re-request signal corresponding to the request signal may be transmitted to the transmission destination electronic control apparatus B that has transmitted the request signal corresponding to the response signal. Correspondingly, when the electronic control unit B receives the re-request signal from the electronic control unit A, the process executed by the process execution means upon reception of the request signal corresponding to the re-request signal The completion response signal storing the information indicating the execution result is preferably transmitted to the re-request signal transmission source device by the retry response means.

  In addition, at the time of a re-request, only the completion response signal may be transmitted / received without transmitting / receiving the reception response signal storing the information indicating the required time between the electronic control devices A and B. It is preferable to configure the electronic control unit B so that the reception response signal is transmitted again when the corresponding processing is incomplete.

  That is, when the retry response means receives the re-request signal, the process execution means has started to execute when the request signal corresponding to the re-request signal is received, but the process execution means has not completed the process. Prior to the transmission of the completion response signal, the reception response signal storing information indicating the time required until the processing corresponding to the request signal is completed is transmitted to the re-request signal transmission source device. Good (Claim 4).

  When the first request signal is received, the required time to be notified to the electronic control device A that is the request signal transmission source is a predicted value, and therefore the electronic control device B on the request signal receiving side does not proceed with processing. The processing corresponding to the request signal is executed by the electronic control device B beyond the required time notified to the electronic control device A as the request signal transmission source.

  At this time, if the electronic control device A that is the transmission source of the re-request signal is notified again of the time required for the completion of the processing by the acceptance response signal, the electronic control device A can set the timeout time setting means even during the retry processing. Thus, an appropriate timeout time can be set for the operation of waiting for reception of the completion response signal. Therefore, if the communication system is configured in this way, error processing (retry processing) can be quickly executed again when a completion response signal cannot be received even by retry processing.

  The time-out time setting means is configured to set a default time-out time for the reception processing means when the request response signal cannot be received from the transmission destination electronic control apparatus B after the request signal is transmitted by the request means. However, if the reception response signal cannot be received, the request signal itself may not be received by the electronic control device B that is the request signal transmission destination. The setting means is preferably configured as follows.

  That is, if the time-out time setting means fails to receive the acceptance response signal from the transmission destination electronic control device B within a predetermined time after the transmission of the request signal by the request means, at that time (the predetermined time It is preferable that the reception processing means is configured to start a retry process when the time elapses. As described above, if the electronic control device A is configured, the execution result of the processing corresponding to the request signal can be quickly acquired from the electronic control device B, and the subsequent processing can be performed quickly.

  In addition, when the process corresponding to the re-request signal is not completed by the process execution unit, the electronic control device B generates an acceptance response signal storing information indicating the time required until the process is completed. In this case, the timeout time setting means may be configured as follows.

  That is, the timeout time setting means receives an acceptance response signal from the transmission destination electronic control unit B within a predetermined time in a state where the completion response signal has not been successfully received after the re-request signal is transmitted by the reception processing means. When the predetermined time has not passed, the reception processing means may be configured to execute the retry process again.

  When the processing corresponding to the re-request signal is completed in the electronic control device B, at the same time as the reception response signal is transmitted when the processing corresponding to the re-request signal is not completed Since the completion response signal is transmitted from the electronic control unit B, if the reception response signal or the completion response signal cannot be received even if the reception response signal reception waiting operation is performed for an appropriate time, There is a high possibility that the re-request signal is not accepted by the electronic control unit B.

  Therefore, if the time-out time setting means is configured as in the present invention, when the re-request signal is not accepted by the electronic control device B, the retry process can be executed again quickly. Therefore, according to the present invention, even when the communication between the electronic control units A and B is obstructed by noise or the like, the retry process is efficiently performed and the execution result of the requested process is quickly obtained. Can be obtained from the electronic control unit B.

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a communication system 1 to which the present invention is applied.
As shown in FIG. 1, the communication system 1 according to the present embodiment includes a plurality of electronic control units (hereinafter also referred to as “ECUs”) connected to a network NT (in-vehicle LAN).

  Specifically, the communication system 1 includes an electronic control device for remote operation reception (hereinafter referred to as “remote operation reception ECU”) 10 and an electronic control device (hereinafter referred to as “verification”) having a verification function related to user authentication. ECU ”) 20 and an electronic control device for body control (hereinafter referred to as“ body ECU ”) that performs lock / unlock control of a vehicle door, control of a power window, and on / off control of a light including a hazard. 30) is connected to the network NT.

  The remote operation reception ECU 10 is connected to a wireless communication device 15 capable of wireless communication with a user terminal 40 carried by the user. The remote operation reception ECU 10 is connected to the body system from the user terminal 40 via the wireless communication device 15. When a remote operation signal for a door system, a light system, a power window system, or the like is received, the terminal ID of the transmission source user terminal 40 included in the remote operation signal is transmitted to the verification ECU 20, and this terminal ID is transmitted to the verification ECU 20. Is compared with the terminal ID of the legitimate user terminal to determine whether or not both terminal IDs match.

  Further, when the remote operation reception ECU 10 recognizes that the remote operation signal transmission source user terminal 40 is a valid user terminal based on the collation result, the remote operation reception ECU 10 realizes processing corresponding to the received remote operation signal. Then, request data requesting execution of the process corresponding to the remote operation signal is transmitted to the body ECU 30 via the network NT, and the body ECU 30 is caused to execute the process corresponding to the remote operation signal. Then, the processing result is transmitted to the user terminal 40 via the wireless communication device 15.

  The body ECU 30 is connected to a door device 31 having a vehicle door lock / unlock mechanism, a power window device 33 having a vehicle window automatic opening / closing mechanism, and a light lighting device 35. The ECU 30 controls these devices 31, 33, and 35 according to requests from the remote operation reception ECU 10 and other ECUs (not shown) to lock / unlock the vehicle door, open / close the window, and turn on the light. / Off etc.

  In this way, in the communication system 1 of the present embodiment, the remote operation reception ECU 10 communicates with the verification ECU 20 and the body ECU 30 in the network NT, and cooperates with these ECUs 20 and 30 to perform a series of remote operations. Realize processing.

By the way, the communication system 1 of the present embodiment is characterized by a communication process that is executed when a series of processes related to a remote operation are realized by a plurality of ECUs 10, 20, and 30 in cooperation.
FIG. 2 is a ladder chart showing a form of communication processing performed in the communication system 1 of the present embodiment. FIG. 3 shows request data, reception response data, and completion response data transmitted and received during this communication. It is explanatory drawing showing a structure. Specifically, FIG. 3A is a diagram illustrating the configuration of request data, FIG. 3B is a diagram illustrating the configuration of reception response data, and FIG. 3C is a diagram illustrating completion response data. It is a figure showing a structure.

  In the present embodiment, in the communication process, a master ECU (specifically, remote operation reception ECU 10) as a requesting ECU that requests other ECUs to execute various processes is a slave ECU (specifically, a requesting ECU). Transmits the request data shown in FIG. 3A to the verification ECU 20 and the body ECU 30) via the network NT.

  In this embodiment, the communication data transmitted / received between the master ECU and the slave ECU is 8-byte data, and the request data is service identification information, data identification information, command information, instruction target information in the upper 6 bytes. And a request synchronization counter.

  The service identification information is information representing a service (processing) system. For example, when requesting the body ECU 30 to execute a process related to a vehicle door, “door system” is used as service identification information in the request data. Is described. In addition, when requesting execution of processing related to opening / closing of a window, a code representing “power window system” is described as service identification information, and when requesting execution of processing related to light, service identification is performed. As information, a code representing “light system” is described.

When requesting the verification ECU 20 to execute the verification process, a code representing “verification system” is described as the service identification information in the request data.
The data identification information is information indicating whether the communication data corresponds to request data, reception response data, or completion response data. In the request data, the data identification information includes A code indicating that the communication data is request data is described.

  In addition, the command information is information indicating the specific contents of the service (process). For example, when requesting the body ECU 30 to execute the unlocking process of the vehicle door, in the request data, A code representing “door system” is described as service identification information, and a code representing “unlock” is described as command information. On the other hand, when requesting the body ECU 30 to execute a vehicle door lock (locking) process, a code representing “lock” is described as command information in the request data (see FIG. 8).

  When requesting the body ECU 30 to execute the window closing process, a code representing “power window system” is described as service identification information, and a code representing “fully closed” is described as command information. The In addition, when the body ECU 30 is requested to execute a window opening process, a code representing “open” is described as command information.

  The instruction target information is information for instructing a target to be subjected to service (processing). When the body ECU 30 is requested to execute the lock / unlock process of the vehicle door, the instruction target information is “vehicle door”. When the body ECU 30 is requested to execute the window opening / closing process, a code representing the position of the window to be opened / closed is described as the instruction target information.

  For example, when the opening / closing process is requested for the window on the driver's seat (D seat) side, a code representing “D seat” is described as the instruction target information. In addition, when the opening / closing process is requested for the window on the passenger seat (P seat) side, a code representing “P seat” is described as the instruction target information, and the window on the rear right seat (RR seat) side is described. When requesting the execution of the opening / closing process, a code indicating “RR seat” is described as the instruction target information, and when requesting the execution of the opening / closing process for the window on the rear left seat (RL seat) side, As the target information, a code representing “RL seat” is described (see FIG. 8).

  In addition, the request synchronization counter is identification information of request data, and each time request data is generated, a unique value is described as the request synchronization counter for the request data. The request synchronization counter is used to establish a correspondence relationship between the reception response data, the completion response data, and the request data. Further, the slave ECU knows whether the request data has been retransmitted. It is for making it happen. In other words, in the present embodiment, the request data to be retransmitted describes the same value as the previously transmitted request data as the request synchronization counter.

  When the master ECU transmits the request data having such a configuration to the slave ECU, the reception response data shown in FIG. 3B is normally transmitted from the slave ECU to the master ECU. When the master ECU receives the reception response data, the master ECU sets a timeout time T1 for the operation of waiting for reception of completion response data scheduled to be continuously transmitted from the slave ECU based on the received reception response data.

  As shown in FIG. 3B, the reception response data includes the above-described service identification information, data identification information, command information, instruction target information, request synchronization counter, and maximum execution time information.

  In the reception response data, a code indicating that the communication data is reception response data is described as the data identification information, and the reception response is used as service identification information, command information, instruction target information, and a request synchronization counter. The same value as the request data corresponding to the data is described. Also, in this reception response data, the time required to execute the process is described as the maximum execution time information regarding the process specified by the service identification information, the command information, and the instruction target information.

  That is, when receiving the reception response data, the master ECU sets the timeout time T1 for the operation of waiting for reception of the completion response data scheduled to be transmitted from the slave ECU, based on the maximum execution time information included in the received reception response data. .

  When this process is finished, the master ECU waits until the timeout time T1 elapses or the completion response data having the configuration shown in FIG. 3C is received from the slave ECU. When the completion response data is received, the remote operation execution result is transmitted to the remote operation source user terminal 40 via the wireless communication device 15 based on the execution result of the process indicated by the completion response data.

  As shown in FIG. 3C, the completion response data includes service identification information, data identification information, command information, instruction target information, a request synchronization counter, as well as request data and reception response data. Information and auxiliary information.

  In this completion response data, a code indicating that the communication data is completion response data is described as data identification information, and the completion response is used as service identification information, command information, instruction target information, and request synchronization counter. The same value as the request data corresponding to the data is described. In the completion response data, the execution success / failure information includes an execution result of the process executed by the slave ECU by transmitting the request data, and a value indicating the success of the process or a value indicating the failure of the process. Described. Further, detailed information regarding the execution result of the process is described as auxiliary information.

  That is, when the master ECU receives the completion response data, the master ECU sends the remote operation execution result to the remote operation source user terminal 40 via the wireless communication device 15 based on the execution success / failure information and auxiliary information included in the completion response data. Send.

  Specific processing executed by the master ECU (remote operation receiving ECU 10) and the slave ECU (verification ECU 20, body ECU 30), such as processing when the completion response data cannot be received within the timeout time T1. Specific contents will be described in detail below with reference to FIGS.

  First, the remote operation reception process executed by the remote operation reception ECU 10 will be described. FIG. 4 is a flowchart showing a remote operation reception process repeatedly executed by the remote operation reception ECU 10. This remote operation reception process is executed by a microcomputer (not shown) in the remote operation reception ECU 10 based on a program that the remote operation reception ECU 10 has.

  When the remote operation acceptance process is started, the remote operation acceptance ECU 10 waits until a remote operation signal is received from the external user terminal 40 via the wireless communication device 15 (S110), and upon receiving the remote operation signal (in S110). Yes), the process proceeds to S120.

  In S120, the remote operation reception ECU 10 sets the verification ECU 20 as a transmission destination (that is, a request destination) of request data related to the remote operation, and transmits a remote operation signal to the verification ECU 20 of the request destination. Request data for requesting the terminal ID of the original user terminal 40 to be compared with the terminal ID of the legitimate user terminal is generated (S130).

  Specifically, a code representing “collation” is described as service identification information, a code representing “request data” is described as data identification information, and a code representing “collation” is described as command information. Then, request data describing the terminal ID of the remote operation signal transmission source user terminal 40 is generated as the instruction target information. At this time, a unique value is described in the request data as a request synchronization counter.

  When the request data is generated in this way, the remote operation acceptance ECU 10 proceeds to S140, and executes the communication process shown in FIG. 5 to transmit the generated request data to the requesting collation ECU 20 and the network NT. And the collation ECU 20 collates the terminal ID of the user terminal 40 that is the remote operation signal transmission source with the terminal ID of the legitimate user terminal.

  When the communication process in S140 is completed, the remote operation reception ECU 10 determines whether or not the remote operation signal transmission source user terminal 40 is a valid user terminal based on the communication result (S150). If the execution success / failure information of the completion response data received in the communication processing of S140 indicates “success”, the terminal ID of the remote operation signal transmission source user terminal 40 matches the terminal ID of the valid user terminal. In this case, it is determined that the user terminal 40 that is the remote operation signal transmission source is a valid user terminal.

  On the other hand, when the execution success / failure information of the completion response data indicates “failure” or when the completion response data cannot be received from the verification ECU 20, the user terminal 40 that is the remote operation signal transmission source is authorized Judge that it is not a terminal.

  If the remote operation signal transmission source user terminal 40 determines in S150 that the user terminal 40 is not a valid user terminal, the remote operation reception ECU 10 sends error information indicating that the authentication has failed via the wireless communication device 15 to the remote operation. The signal is transmitted to the user terminal 40 of the signal transmission source (S155), and the remote operation acceptance process is temporarily terminated. Then, it waits until it receives the next remote control signal (S110).

  In addition, when it is determined in S150 that the user terminal 40 that is the remote operation signal transmission source is a valid user terminal, the remote operation reception ECU 10 proceeds to S160 and transmits the request data transmission destination (request destination for remote operation). ), Instead of the verification ECU 20, the body ECU 30 is set, and request data for requesting the request body ECU 30 to execute processing corresponding to the remote operation signal (body control) is generated (S170). .

  For example, when an unlocking operation of the vehicle door is performed at the user terminal 40 and a corresponding remote operation signal is received from the user terminal 40, a code representing “door system” is described as service identification information, and data As identification information, describe a code representing “request data”, as command information, describe a code representing “unlock”, as instruction target information, describe a code representing “vehicle door”, and as a request synchronization counter , Request data describing a unique value is generated.

  In addition, when a driver's side window opening operation is performed at the user terminal 40 and a corresponding remote operation signal is received from the user terminal 40, a code representing "power window system" is described as service identification information The code indicating “request data” is described as the data identification information, the code indicating “open” is described as the command information, the code indicating “D seat” is described as the instruction target information, and the request synchronization Request data describing a unique value is generated as a counter.

  When the request data is generated in this way, the remote operation reception ECU 10 executes the communication process shown in FIG. 5 (S180), and sends the request data generated in S170 to the requesting body ECU 30 in the network NT. To cause the body ECU 30 to execute processing (body control) corresponding to the remote operation signal.

  When the process in S180 is completed, the remote operation reception ECU 10 determines whether the requested process (body control) is successful in the body ECU 30 based on the communication result (S190). Specifically, when the success / failure information of the completion response data received in S180 indicates “success”, it is determined that the requested process has been successful. On the other hand, when the execution success / failure information of the received completion response data indicates “failure”, or when the completion response data cannot be received from the body ECU 30, it is determined that the process requested in the body ECU 30 has failed. .

  If it is determined in S190 that the requested process is determined to have failed in the body ECU 30 (No in S190), the remote operation acceptance ECU 10 transmits error information indicating that the remote operation has failed via the wireless communication device 15 to the remote operation. The signal is transmitted to the user terminal 40 of the signal transmission source (S195), and then the remote operation acceptance process is temporarily terminated.

  In addition, when it is determined in S190 that the requested process is determined to have been successful in the body ECU 30, the remote operation reception ECU 10 proceeds to S200 and indicates information indicating that the remote operation has been successful and the content of the successful remote operation. Information is transmitted to the user terminal 40 that is the remote operation signal transmission source via the wireless communication device 15. Thereafter, the remote operation acceptance process is temporarily terminated.

  Next, the communication process executed in S140 and S180 will be described. FIG. 5 is a flowchart showing communication processing executed by the remote operation reception ECU 10. This communication process is executed by a microcomputer (not shown) in the remote operation reception ECU 10 based on a program that the remote operation reception ECU 10 has.

  When the communication process shown in FIG. 5 is started, the remote operation reception ECU 10 transmits the request data generated in advance to the preset request destination ECU via the network NT (S210). That is, when the communication process is executed in S140, the request data generated in S130 is transmitted to the verification ECU 20 set in the request destination ECU in S120. On the other hand, when the communication process is executed in S180, the request data generated in S170 is transmitted to the body ECU 30 set in the request destination ECU in S160.

  When the process in S210 is completed, the remote operation acceptance ECU 10 proceeds to S220, and determines whether or not a predetermined time T0 has elapsed after executing the process in S210. The time T0 is set to a fixed value (for example, about 4 seconds) in advance at the design stage. Specifically, it is set to a necessary and sufficient time so that the reception response data can be properly received.

  If it is determined in S220 that the predetermined time T0 has elapsed (Yes in S220), the remote operation acceptance ECU 10 proceeds to S300, and if it is determined that the predetermined time T0 has not elapsed (No in S220), the process proceeds to S230. .

  In S230, the remote operation reception ECU 10 determines whether or not the completion response data corresponding to the request data transmitted in S210 is received from the request destination ECU via the network NT (S230). If it is determined that the data is received from the request destination ECU (Yes in S230), the process proceeds to S280, and if it is determined that the completion response data is not received from the request destination ECU (No in S230), the process proceeds to S240.

  In S240, the remote operation reception ECU 10 determines whether or not reception response data corresponding to the request data transmitted in S210 has been received from the request destination ECU via the network NT, and requests reception response data. If it is determined that it has not been received from the previous ECU (No in S240), the process proceeds to S220 and waits until a predetermined time T0 elapses or reception response data or completion response data corresponding to the request data is received.

  On the other hand, when it is determined that the reception response data has been received from the request destination ECU (Yes in S240), the remote operation reception ECU 10 proceeds to S250, and based on the maximum execution time information included in the received reception response data, this maximum execution time A value obtained by adding a certain time α to the value represented by the information is set as the timeout time T1 for the operation of waiting for reception of the completion response data.

T1 = Maximum execution time + α
Note that the time α can be set to an arbitrary value greater than or equal to zero. However, since the time α is for setting the time-out time T1 with a margin slightly longer than the maximum execution time notified from the request destination ECU, it is not set to a value larger than necessary.

  When the processing in S250 is completed, the remote operation acceptance ECU 10 determines whether or not the timeout time T1 has elapsed since the time-out time T1 was set in S250 (S260), and the timeout time T1 has elapsed. (Yes in S260), the process proceeds to S300, and if it is determined that the timeout time T1 has not elapsed (No in S260), the completion response data corresponding to the request data transmitted in S210 is obtained from the request destination ECU. It is determined whether it is received via the network NT (S270). If it is determined that the completion response data is not received from the request destination ECU (No in S270), the process waits until the timeout time T1 elapses or the completion response data is received.

  In addition, when it is determined that the completion response data has been received from the request destination ECU (Yes in S270), the remote operation reception ECU 10 outputs the execution success / failure information and the auxiliary information indicated by the completion response data as return values. Is provided to the remote operation reception processing task (S280). Thereafter, the communication process ends.

  In S300, the remote operation reception ECU 10 executes a retry process shown in FIG. FIG. 6 is a flowchart showing a retry process executed by the remote operation reception ECU 10.

  When the retry process is started, the remote operation reception ECU 10 first initializes a parameter n representing the number of retries to zero in S310. Thereafter, the process proceeds to S320, and the same request data as the request data transmitted in S210 is retransmitted to the request destination ECU. Then, after retransmission, 1 is added to the parameter n in S330 (n ← n + 1).

  When this processing is completed, the remote operation acceptance ECU 10 sends a completion response data corresponding to the request data transmitted in S320 via the network NT after the predetermined time T0 has elapsed after the retransmission in S320. The system waits until reception response data corresponding to the request data received from the ECU or transmitted in S320 is received from the request destination ECU via the network NT (S340 to S360), and determines that the predetermined time T0 has passed ( If it is determined that the completion response data is received from the requested ECU (Yes in S350), the process proceeds to S400 and if it is determined that the reception response data is received from the requested ECU (S360). Yes), the process proceeds to S370.

  In S370, the remote operation acceptance ECU 10 sets a value obtained by adding a fixed time α to the value represented by the maximum execution time information based on the maximum execution time information included in the received reception response data. The timeout time T1 for the reception waiting operation is set.

  When this processing is finished, the remote operation acceptance ECU 10 sends the completion response data corresponding to the request data transmitted in S320 after the timeout time T1 has elapsed from the time when the timeout time T1 is set in S370 or the network NT. Until the time-out period T1 has elapsed (Yes in S380), the process proceeds to S410, and it is determined that the completion response data has been received from the request-destination ECU. Then (Yes in S390), the process proceeds to S400.

  In S400, the remote operation reception ECU 10 outputs execution success / failure information and auxiliary information indicated by the received completion response data as return values, and provides these information to the remote operation reception processing task. Thereafter, the retry process is terminated. In S300, when the retry process is finished, the communication process is finished.

  On the other hand, when the process proceeds to S410, the remote operation reception ECU 10 determines whether or not the value of the parameter n indicating the number of retries is less than a predetermined upper limit (for example, value 2) of the number of retries, and parameter n If the value is less than the upper limit (Yes in S410), the process proceeds to S320, and the request data is retransmitted again. Then, the value of the parameter n is incremented by 1 (S330), and the processes after S340 are executed.

  If it is determined that the number of retries is equal to or greater than the upper limit value (No in S410), the remote operation reception ECU 10 outputs error information indicating a communication failure as a return value, and these information is sent to the remote operation reception processing task. Provide (S420). Thereafter, the retry process is terminated. In S300, when this retry process is completed, the remote operation reception ECU 10 ends the communication process.

  Next, a request receiving process executed by the slave ECU (specifically, the verification ECU 20 and the body ECU 30) that receives the request data transmitted from the master ECU will be described. FIG. 7 is a flowchart showing a request receiving process repeatedly executed by the slave ECU. This request reception process is executed by a microcomputer (not shown) in the slave ECU based on a program that the slave ECU has.

  When the request acceptance process is started, the slave ECU first waits until request data is received from the master ECU (remote operation acceptance ECU 10) (S510). When the request data is received (Yes in S510), the received request data is received. Is request data that can be accepted (S520). That is, based on the service identification information, command information, and instruction target information indicated by the received request data, it is determined whether or not the process corresponding to the request data can be executed by the own apparatus.

  If it is determined that the received request data is not acceptable request data (No in S520), the slave ECU generates completion response data in which information indicating execution failure has been described (S530).

  Specifically, in S530, a code representing "completion response data" is written as the data identification information, and the same code as the received request data is used as the service identification information, command information, instruction target information, and request synchronization counter. In addition, a completion response data in which a code indicating “failure” is described as the execution success / failure information and a code indicating that the request cannot be accepted is generated as auxiliary information is generated. When the completion response data having such a configuration is generated, the generated completion response data is transmitted to the requesting master ECU via the network NT (S535). Thereafter, the request acceptance process is temporarily ended, and the process waits until the next request data is received (S510).

  On the other hand, if the slave ECU determines in S520 that the received request data is acceptable request data (Yes in S520), the slave ECU proceeds to S540 and has the same value as the request synchronization counter described in the received request data. The process execution history data having the request synchronization counter is searched in the execution history file (see FIG. 9) stored in the RAM of the slave ECU.

  The execution history file stored in the slave ECU stores the processing execution history data corresponding to the request data for each request data for which the corresponding processing is completed and the corresponding completion response data is transmitted. is there. As shown in FIG. 9, the process execution history data included in the execution history file includes a registration time of the process execution history data and information indicating transmission contents of the completion response data. Specifically, the process execution history data includes each piece of information (execution success / failure information, auxiliary information, request synchronization counter, etc.) described in the transmitted completion response data as information indicating the transmission content of the completion response data.

  If it is determined that the process execution history data having the request synchronization counter having the same value as the request synchronization counter described in the received request data is present in the execution history file based on the search result in S540 (S550), the slave ECU Completion response data is generated based on the process execution history data (S560), and the generated completion response data is transmitted to the requesting master ECU via the network NT (S565). The process execution history data already contains the contents of the completion response data transmitted last time, so in S560 to S565, the completion of the same contents as the previously transmitted completion response data is based on the contents of the process execution history data. The response data is transmitted to the requesting master ECU. When the process in S565 is finished, the slave ECU ends the request reception process and waits until the next request data is received (S510).

  In addition, if the slave ECU determines in S550 that the process execution history data having the request synchronization counter having the same value as the request synchronization counter described in the received request data does not exist in the execution history file (No in S550). , The process proceeds to S570, and it is determined whether or not the processing corresponding to the received request data has already been started. This determination is made by determining whether or not execution management data having a request synchronization counter having the same value as the request synchronization counter described in the received request data exists in the execution management table described later. Done.

  If it is determined in S570 that the corresponding process has not yet been started (No in S570), the slave ECU determines the process requested to be executed by the received request data from the processing time table stored in the ROM of its own device. Processing time information is acquired (S580). FIG. 8 is a diagram showing a configuration of the processing time table, and more specifically, a diagram showing a configuration of the processing time table that the body ECU 30 has.

  As shown in FIG. 8, in the processing time table, the time required to execute the processing is described as processing time Tc for each type of processing that can be executed based on the request data. In other words, in the processing time table, for each combination of service, command, and instruction target described in the acceptable request data, the time required to execute the processing corresponding to the combination is described as the processing time Tc. Is.

  For example, when the body ECU 30 receives data requesting the unlocking process of the vehicle door as request data from the remote operation reception ECU 10, the code representing the “door system” described as service identification information in the request data, Based on the code indicating “unlock” described as command information and the code indicating “vehicle door” described as instruction target information, as the corresponding processing time information, among the processing time information shown in FIG. To the second stage processing time information (value of “2 seconds”).

  In S580, when the processing time information is acquired from the processing time table as described above, the slave ECU proceeds to S583 and accepts response data that describes the value Tc indicated by the acquired processing time information as the maximum execution time information. Is generated. Specifically, as the service identification information, command information, instruction target information, and request synchronization counter, the same value as the request data received in S510 is described, and the value Tc indicated by the processing time information acquired in S580 is set as the maximum execution time. The reception response data described as information is generated.

  When this process is completed, the slave ECU starts executing the process requested by the request data (S587) and transmits the generated reception response data to the requesting master ECU (S600). For example, in S587, when execution of the vehicle door unlock process is requested by the request data, the slave ECU executes the vehicle door unlock process and controls the door device 31 to unlock the vehicle door. Lock it.

  When the execution of the process requested by the request data is started, a process ID is assigned to the process to be executed, and the process ID and the received content of the request data that causes the process to be executed. Is recorded in the execution management table stored in the RAM of the slave ECU. The information indicating the reception contents of the request data described in the record includes information on the request data transmission source ECU in addition to the information included in the request data.

  In S600, when the reception response data is transmitted to the requesting master ECU, the slave ECU temporarily ends the request reception process in a state where the process started in S587 is continued, and the next request Wait until data is received.

  On the other hand, if the slave ECU determines in S570 that the process corresponding to the received request data has already been started (Yes in S570), the process proceeds to S590, and from the processing time table stored in the ROM of the slave ECU. The processing time information about the processing requested to be executed by the received request data is acquired.

  In addition, when the processing time information is acquired from the processing time table, the slave ECU proceeds to S593, and the value Tc indicated by the acquired processing time information and the progress r of the process being executed (r is 0 or more and less than 1). Value), a remaining processing time Tr until the processing is completed is derived (Tr = Tc · (1−r)).

  Then, reception response data in which the derived remaining processing time Tr is described as maximum execution time information is generated (S597). Specifically, in S597, the same value as the request data received in S510 is described as service identification information, command information, instruction target information, and request synchronization counter, and the remaining processing time Tr derived in S593 is used as the maximum execution time information. The reception response data described as is generated.

  When this process ends, the slave ECU proceeds to S600, transmits the generated reception response data to the requesting master ECU, and then ends the request reception process once.

  Subsequently, a response control process executed by the slave ECU to transmit completion response data will be described. FIG. 9 is a flowchart showing a response control process repeatedly executed by the slave ECU.

  When the response control process is started, the slave ECU monitors the progress of each process that has been requested to be executed based on the request data, and detects the end timing of the process (S610). That is, here, the process that is requested to be executed by the request data is monitored and the progress of execution of each process that has started execution is monitored, and any of the monitored processes transitions from the execution state to the execution end state. Wait until.

  When any of the processes to be monitored transitions from the execution state to the execution end state (Yes in S610), the slave ECU proceeds to S620 and completes the execution result of the process transitioned to the execution end state Generate response data.

  Specifically, the execution management data relating to the process transitioned to the execution end state is read from the execution management table, and based on the received content of the request data indicated by the execution management data, service identification information, command information, instruction target information, In addition, as the request synchronization counter, completion response data indicating the same value as the request data is generated, and whether or not the process has been successfully executed based on the execution result of the process transitioned to the execution end state. Execution success / failure information and auxiliary information indicating the above are described.

  In addition, when the processing in S620 is completed in this way, the slave ECU proceeds to S630, and the completion response data generated in S620 is transmitted to the master ECU of the request source (request data transmission source indicated by the execution management data). Send. When the completion response data is transmitted, the read execution management data is deleted from the execution management table.

  When the processing in S630 is completed, the slave ECU proceeds to S640, and generates processing execution history data describing the transmission content of the transmitted completion response data and the current time. Register to a file. After that, the response control process is temporarily ended, and a new one of the monitoring target processes waits until the transition from the execution state to the execution end state (S610). The process execution history data registered in the execution history file is deleted from the execution history file by the operation of the slave ECU after a predetermined time has elapsed from the registration time.

  The operations of the master ECU and the slave ECU have been described above. With such a communication method, when the master ECU according to the present embodiment requests the slave ECU to execute the process, the completion indicating the execution result of the process is completed. The reception waiting operation for the response data is executed for a period corresponding to the maximum execution time notified from the slave ECU. If the completion response data cannot be received within this period, retry processing is performed, and acquisition of the completion response data is retried. Similarly, when the reception response data transmitted prior to the completion response data cannot be received within the predetermined time T0, the retry process is performed in the same manner.

  For example, the request data transmitted from the master ECU is not received by the slave ECU due to the influence of noise or the like, or the reception response data transmitted from the slave ECU is not received by the master ECU due to the influence of noise or the like. In this case, as shown in FIG. 10A, the request data is retransmitted from the master ECU after a predetermined time T0 has elapsed since the request data was transmitted (retry process).

  As another example, as shown in FIG. 10 (b), the processing requested from the master ECU in the slave ECU despite the successful transmission and reception of the request data and the reception response data between the master ECU and the slave ECU. The execution of the above process does not progress, and the execution of the above process is continued beyond the maximum execution time notified from the slave ECU to the master ECU, and the master ECU receives the completion response data within the timeout time T1. If not, the request data is retransmitted from the master ECU after a lapse of time T1 from the reception of the reception response data (retry process). When the slave ECU receives the request data retransmitted from the master ECU, the slave ECU derives the remaining processing time Tr for the process being executed, and accepts response data in which the remaining processing time Tr is described as maximum execution time information. Is transmitted to the master ECU. In the master ECU, a time corresponding to the maximum execution time information described in the reception response data is set as the timeout time T1. Then, during the period until the time T1 elapses, the master ECU performs an operation of waiting for reception of completion response data.

  As another example, as shown in FIG. 10 (c), the master ECU and the slave ECU have successfully exchanged the request response data and the reception response data, and the slave ECU has transmitted the completion response data. First, when the completion response data is not received by the master ECU due to the influence of noise or the like, the request data is retransmitted from the master ECU after the timeout time T1 has elapsed (retry processing). At this time, since the requested processing has already been completed in the slave ECU, the completion response data is immediately transmitted from the slave ECU instead of the reception response data.

  As another example, as shown in FIG. 10 (d), the master ECU and the slave ECU succeeded in receiving and receiving the acceptance response data and the completion response data is transmitted from the slave ECU. First, the completion response data is not received by the master ECU due to the influence of noise or the like, and the completion response data is received by the master ECU due to the influence of noise or the like even during the retry process. If not, the request data is retransmitted again after a predetermined time T0 from the execution time of the first retry process (second retry process).

  During the retry process, only the predetermined time T0 waits for reception of the reception response data and the completion response data when neither the reception response data nor the completion response data can be received within the predetermined time T0. This is because there is a high possibility that a problem has occurred in the transmission process of communication data, and there is a low possibility that the completion response data can be received even when waiting for longer.

  That is, when the processing corresponding to the request data is completed, it does not take time to transmit the completion response data due to the waiting for processing, and the completion response data is as long as the reception waiting time of the reception response data. Therefore, when neither the reception response data nor the completion response data can be received within the predetermined time T0, the master ECU performs a second retry process.

  As described above, the predetermined time T0 should be set to a necessary and sufficient time so that the reception response data can be properly received. However, the time T0 is completed when the completion response data is retransmitted. It is also necessary to set the response data so that it can be received appropriately. However, if the time T0 is set too long, there is no point in setting the timeout time T1, so it is necessary to set the time in consideration of this.

  The communication system 1 of the present embodiment has been described above. However, in the communication system 1 of the present embodiment, the remote operation reception ECU 10 communicates with the verification ECU 20 and the body ECU 30 that are other ECUs in the network NT, and these ECUs 20 , 30 to realize a series of processes related to remote operation. Specifically, when the verification ECU 20 or the body ECU 30 receives the request data from the remote operation reception ECU 10, the verification ECU 20 or the body ECU 30 is response data that stores maximum execution time information indicating a time required for completing the process requested by the request data. Then, the reception response data indicating that the request has been received is transmitted to the remote operation reception ECU 10 as the request source.

  On the other hand, in the communication system 1 of the present embodiment, when a remote operation signal is input from the user terminal 40, the remote operation reception ECU 10 sends request data to the verification ECU 20 and the body ECU 30 in order to realize processing for the remote operation. Send. The remote operation reception ECU 10 then transmits a process that is transmitted after the process requested by the verification ECU 20 or the body ECU 30 is completed based on the maximum execution time information indicated by the reception response data transmitted from the verification ECU 20 or the body ECU 30 at this time. A timeout period is set for the operation of waiting for reception of the completion response data representing the execution result of.

  When the completion response data can be received within the timeout time, the execution result of the process related to the remote operation is transmitted to the user terminal 40, and the completion response data cannot be received within the timeout time. If it does, retry processing is executed.

  Therefore, according to this communication system 1, it is possible to set an appropriate time-out period for the operation of waiting for reception of completion response data for each process to be executed by the slave ECU. For example, if a time-out period common to each service is set in accordance with a power window service that takes time to complete processing (in other words, it takes time to send completion response data), When requesting a door-type service with a short time, the timeout time will be set redundantly, and it will take time to execute the retry process, but according to this embodiment, for each requested process, Since an appropriate time-out period can be set, the time required for executing the retry process can be shortened.

  In the communication system 1 of the present embodiment, the master ECU that requests the slave ECU to execute the process acquires the maximum execution time information related to the execution time of the process from the slave ECU that executes the requested process. Even when the combination of the master ECU and the slave ECU is different, the master ECU can set an appropriate time-out time in accordance with the processing contents and processing capability of the slave ECU.

  Therefore, if the in-vehicle LAN system is configured by the method of this embodiment, the ECU is subdivided for each function, and each subdivided function is realized by an individual electronic ECU. For an ECU that realizes a general-purpose function, it is necessary to set a time-out period for the processing result waiting operation for the master ECU in advance in consideration of the combination of the ECUs when the ECU is shared regardless of the vehicle type. In the master ECU, the time-out time can always be set appropriately regardless of the type of the slave ECU.

  In addition, in this embodiment, when the slave ECU receives the request data retransmitted from the master ECU, if the processing corresponding to the request data is not completed in the slave ECU, the remaining processing time Tr is related to this processing. And receiving response data storing this time Tr as maximum execution time information is transmitted to the requesting master ECU. Therefore, according to this embodiment zero, even during the retry process, the master ECU can set an appropriate time-out period for the operation of waiting for reception of the completion response data. Therefore, according to the communication system 1 of the present embodiment, when the completion response data cannot be received even by the retry process, the retry process can be quickly executed again.

  Further, in this embodiment, after the request data is transmitted, if the reception response data cannot be received within the predetermined time T0, the retry process is immediately performed without waiting for the completion response data to be received. I tried to run. In addition, after the request data is retransmitted by the retry process, if there is no response from the slave ECU within the predetermined time T0, the retry process is immediately performed again. Therefore, according to the present embodiment, the retry process can be efficiently performed, and the execution result of the requested process can be quickly acquired from the slave ECU.

  The acceptance response means of the present invention is realized by the processes of S580, S583, S600, the process execution means is realized by the process of S587, and the completion response means is a response control process (see FIG. 9). It has been realized. Further, the request means is realized by the processing of S120 to S130, S160 to S170, S210, the reception processing means is realized by the processing of S260 to S300, S200, etc., and the timeout time setting means is S220 to S250, This is realized by the processing of S340 to S370. The retry response means is realized by the processing of S540 to S570 and S590 to S600 and the response control processing.

Further, the communication system of the present invention is not limited to the above-described embodiments, and can take various forms.
For example, in the above-described embodiment, when a window opening / closing process request is received from the remote operation reception ECU 10, the maximum execution is performed based on the reception response data based on the processing time table without considering the current opening of the window. Although the time information is notified from the body ECU 30 to the remote operation reception ECU 10, the time required for opening and closing the window depends on the opening of the window at the start of opening and closing. In consideration of this, the maximum execution time described in the reception response data may be calculated.

  Further, in the above embodiment, when the request data corresponding to the currently executed process is received from the master ECU, the slave ECU derives the remaining processing time Tr, and the derived remaining processing time Tr is maximized. Although it is described in the reception response data as time information, the slave ECU receives request data for a process that is not being executed from the master ECU even when request data corresponding to the process that is currently being executed is received from the master ECU. Similarly to the case, the processing time Tc read from the processing time table may be described in the reception response data as the maximum execution time information.

  In addition, in the said Example, although the remote operation reception ECU10, collation ECU20, and body ECU30 cooperated, the example which applied this invention to the system which implement | achieves the process which concerns on remote operation was shown, The communication system of this invention Needless to say, the combination of the ECUs is not limited to this.

It is a block diagram showing the structure of the communication system 1 of a present Example. It is the ladder chart which showed the communication form of a present Example. It is explanatory drawing which showed the structure of the request data (a), reception response data (b), and completion response data (c) transmitted / received in the case of communication. It is a flowchart showing the remote operation reception process which remote operation reception ECU10 performs. It is a flowchart showing the communication process which remote operation reception ECU10 performs. It is a flowchart showing the retry process which remote control reception ECU10 performs. It is a flowchart showing the request | requirement reception process which slave ECU performs. It is a figure showing the structure of a processing time table. It is a flowchart showing the response control process which slave ECU performs. It is the ladder chart which showed the communication form of a present Example.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Communication system, 10 ... Remote operation reception ECU, 15 ... Wireless communication apparatus, 20 ... Collation ECU, 30 ... Body ECU, 31 ... Door apparatus, 33 ... Power window apparatus, 35 ... Lighting apparatus, 40 ... User terminal, NT …network

Claims (6)

A plurality of electronic control devices are connected to the network, and at least one of the plurality of electronic control devices A communicates with another electronic control device B in the network, and the other electronic control device B A communication system that realizes a series of processing in cooperation with
The electronic control unit B is
When a request signal for requesting execution of processing is received from the electronic control unit A, the response signal stores information indicating a time required until the processing requested by the received request signal is completed, An acceptance response means for transmitting an acceptance response signal indicating that the request has been accepted to a transmission source device of the request signal;
When a request signal for requesting execution of processing is received from the electronic control unit A, processing execution means for executing processing requested by the received request signal;
When the process corresponding to the request signal is completed by the process execution means, a response signal indicating that the process corresponding to the request signal is completed, and a completion response signal storing information indicating the result of the process is stored. A completion response means for transmitting the request signal to a transmission source device;
With
The electronic control unit A includes
Request means for transmitting a request signal for requesting execution of a process corresponding to the generated event to the electronic control unit B capable of executing the process in response to the occurrence of the event;
A reception processing means for receiving a completion response signal corresponding to the request signal transmitted by the request means from the electronic control device B, and executing a process corresponding to the event based on the received completion response signal;
Upon receipt of an acceptance response signal from the electronic control unit B, a completion response corresponding to the received acceptance response signal is sent to the reception processing means based on information representing the required time stored in the received acceptance response signal. A timeout time setting means for setting a timeout time for the signal reception waiting operation;
A communication system comprising:   The reception processing unit obtains the completion response signal when the completion response signal corresponding to the request signal cannot be received in a period until the timeout time set by the timeout time setting unit elapses. The communication system according to claim 1, wherein the communication system is configured to execute a retry process including a procedure for retrying. When the reception processing unit cannot receive a completion response signal corresponding to the request signal in a period until the timeout time set by the timeout time setting unit elapses, as the retry processing, A re-request signal corresponding to the request signal is transmitted to the electronic control device B that has transmitted the request signal corresponding to the completion response signal;
The electronic control unit B is
When a re-request signal is received from the electronic control unit A, a completion response signal storing information indicating the execution result of the process started by the process execution means when receiving the request signal corresponding to the re-request signal Retry response means for transmitting to the transmission source device of the re-request signal,
The communication system according to claim 2, further comprising:   The retry response means, at the time of receiving the re-request signal, the process executed by the process execution means when receiving the request signal corresponding to the re-request signal has been completed by the process execution means. If not, prior to transmission of the completion response signal, an acceptance response signal storing information indicating a time required until the processing corresponding to the request signal is completed is transmitted to the re-request signal transmission source device. The communication system according to claim 3, wherein the communication system is configured.   The time-out time setting means, if the reception response signal cannot be received from the electronic control device B as the transmission destination within a predetermined time after the transmission of the request signal by the request means, The communication system according to any one of claims 2 to 4, wherein the retry process is started when the predetermined time has elapsed.   The time-out time setting means receives an acceptance response signal from the electronic control device B as a transmission destination within a predetermined time in a state where the completion response signal has not been successfully received after transmission of the re-request signal by the reception processing means 5. The communication system according to claim 4, wherein when the predetermined time has not been received, the reception processing means is made to execute the retry processing again when the predetermined time has elapsed. .

Images