Communication network system, monitoring device, and monitoring program
The communication network system addresses the challenge of failure recovery by using a monitoring device to identify and manage abnormal devices, restricting communication, and lifting restrictions based on scheduled periods, thus enhancing recovery speed and reliability.
Patent Information
- Application Number
- JP2021066348
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-04-09
- Publication Date
- 2024-12-03
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing communication network systems, such as those in vehicles, face challenges in efficiently recovering from communication failures, particularly in terms of timely and efficient restoration of communication after detecting abnormal devices.
A communication network system with a monitoring device that checks connections to multiple devices, identifies abnormal devices, and restricts communication with them, then lifts restrictions based on individually set scheduled failure recovery periods to facilitate faster recovery.
The system effectively reduces the time required to restore communication after a failure by suppressing unnecessary communication with abnormal devices and lifting restrictions according to predefined recovery periods, thereby enhancing communication reliability and efficiency.
Smart Images

Figure 0007593867000001 
Figure 0007593867000002 
Figure 0007593867000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication network system, a monitoring device, and a monitoring program. [Background technology]
[0002] As an example of a conventional communication network system mounted on a vehicle or the like, Patent Document 1 discloses a switch device mounted on the vehicle. The switch device includes a holding unit, a switch unit, and a control unit. The holding unit holds communication data to be relayed. The switch unit relays the communication data. When communication data to be transmitted to a device in which an abnormality is detected is held in the holding unit, the control unit transmits stop request data to at least one communication device mounted on the vehicle and on a path from its own switch device to the source of the communication data, requesting the stop of transmission of communication data to its own switch device and the holding of the communication data to be transmitted to its own switch device. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2018-113505 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, there is still room for improvement in such a switch device, for example, in terms of recovery from a communication failure.
[0005] The present invention has been made in consideration of the above circumstances, and has an object to provide a communication network system, a monitoring device, and a monitoring program that are capable of properly restoring communications. [Means for solving the problem]
[0006] In order to achieve the above-mentioned object, the communication network system of the present invention comprises a communication-capable network, a plurality of communication devices connected to the network, and a monitoring device connected to the network and capable of performing a process of checking connections to the plurality of communication devices, detecting an abnormal device from the plurality of communication devices, and restricting communications involving the abnormal device for other communication devices other than the abnormal device, wherein the monitoring device is capable of performing a process of lifting the restriction on communications for the other communication devices based on a planned fault recovery period set for the abnormal device out of a planned fault recovery period expected for fault recovery which is a period that is individually set in advance for the plurality of communication devices.
[0007] In order to achieve the above-mentioned object, the monitoring device of the present invention comprises a communication connection unit connected to a network, and a processing unit capable of performing a process of performing connection checks on a plurality of communication devices connected to the network, detecting an abnormal device from the plurality of communication devices, and restricting communications involving the abnormal device for other communication devices other than the abnormal device, and the processing unit is characterized in that it is capable of performing a process of lifting the restriction on communications for the other communication devices based on the planned fault recovery period set for the abnormal device out of the planned fault recovery period expected for fault recovery, which is a period that is individually set in advance for the plurality of communication devices.
[0008] In order to achieve the above-mentioned object, the monitoring program of the present invention is characterized in having a computer execute each of the following processes: performing connection checks for multiple communication devices connected to a network, detecting an abnormal device from the multiple communication devices, restricting communications involving the abnormal device for other communication devices other than the abnormal device, and lifting the restriction on communications for the other communication devices based on the planned fault recovery period set for the abnormal device out of the planned fault recovery period expected for fault recovery, which is a period that is individually set in advance for the multiple communication devices. Effect of the Invention
[0009] The communication network system, monitoring device, and monitoring program according to the present invention perform connection checks on multiple communication devices connected to a network and detects an abnormal device from the multiple communication devices. When the communication network system, monitoring device, and monitoring program detect an abnormal device, they restrict communications involving the abnormal device with other communication devices other than the abnormal device. Thereafter, the communication network system, monitoring device, and monitoring program release the restriction on communications with the other communication devices based on a planned failure recovery period that is individually set in advance for the abnormal device. As a result, the communication network system, monitoring device, and monitoring program achieve the effect of being able to properly restore communications. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a block diagram showing a schematic configuration of a communication network system according to the first embodiment. [Diagram 2] FIG. 2 is a block diagram showing a schematic configuration of the monitoring device according to the first embodiment. [Diagram 3] FIG. 3 is a flowchart illustrating an example of a process performed by the communication network system according to the first embodiment. [Figure 4] FIG. 4 is a time chart illustrating an example of the operation of the communication network system according to the comparative example. [Diagram 5] FIG. 5 is a time chart illustrating an example of the operation of the communication network system according to the first embodiment. [Figure 6] FIG. 6 is a flowchart illustrating an example of a process performed by the communication network system according to the second embodiment. [Figure 7] FIG. 7 is a time chart illustrating an example of the operation of the communication network system according to the comparative example. [Figure 8] FIG. 8 is a time chart illustrating an example of the operation of the communication network system according to the second embodiment. [Figure 9] FIG. 9 is a block diagram showing a schematic configuration of a monitoring device according to the third embodiment. [Figure 10] FIG. 10 is a flowchart illustrating an example of a process performed by the communication network system according to the third embodiment. [Figure 11] FIG. 11 is a time chart illustrating an example of the operation of the communication network system according to the comparative example. [Figure 12] FIG. 12 is a time chart illustrating an example of the operation of the communication network system according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment. In addition, the components in the following embodiments include those that are replaceable and easy for a person skilled in the art, or those that are substantially the same.
[0012] [Embodiment 1] The communication network system 1 of the present embodiment shown in Fig. 1 is, for example, mounted on a vehicle and constitutes an in-vehicle network system that connects in-vehicle devices provided on the vehicle so that they can communicate with each other. The communication network system 1 is realized by mounting the components shown in Fig. 1 on a vehicle.
[0013] In recent years, in-vehicle applications related to autonomous driving, ADAS (Advanced Driver-Assistance Systems), and the like have been developed and spread in in-vehicle network systems such as the communication network system 1. Such in-vehicle network systems are required to have higher real-time capabilities and reliability.
[0014] In light of this background, the communication network system 1 of this embodiment is a system that identifies an abnormal device from among multiple communication devices 2 connected to a network N and regulates communications involving the abnormal device, and achieves faster recovery of communications based on various periods that are individually set in advance for each communication device 2. The configuration of the communication network system 1 will be described in detail below with reference to the various drawings.
[0015] Specifically, the communication network system 1 includes a network N, a plurality of communication devices 2, and a monitoring device 3.
[0016] The network N constitutes a communication network that connects a plurality of devices so that they can communicate with each other. The network N enables communication by various known communication methods that can be applied to this system.
[0017] The communication device 2 is an electronic device connected to the network N. The multiple communication devices 2 include, for example, an ECU (Electronic Control Unit) 2A constituting an in-vehicle device and a HUB 2B constituting a network device. The ECU 2A is an electronic control unit that controls the in-vehicle device mounted on the vehicle to realize various functions. Here, multiple ECUs 2A are connected to the HUB 2B and the monitoring device 3 via the network N. The HUB 2B is a relay device that relays mutual communication between the multiple communication devices 2 and the monitoring device 3 on the network N. The HUB 2B is interposed between the monitoring device 3 and the multiple communication devices 2 (here, the ECU 2A) and constitutes a concentrator that consolidates the connection destinations of the multiple communication devices 2, and relays signals (information). Each communication device 2 is configured to be able to transmit a response to the connection confirmation to the monitoring device 3 via the network N when it receives a connection confirmation (request) from the monitoring device 3 via the network N.
[0018] The monitoring device 3 is an electronic device connected to the network N, which monitors communication failures in the network N and regulates communication as necessary. In general, the monitoring device 3 checks the connection of each communication device 2 via the network N at a fixed period or at an arbitrary timing to detect a failure, and instructs the communication devices 2 other than the abnormal device in which the failure was detected to regulate communications involving the abnormal device. The monitoring device 3 of this embodiment is configured by a gateway that constitutes a network device. In other words, the monitoring device 3 has a GW function that performs protocol conversion as well as a network monitoring function.
[0019] 2, the monitoring device 3 includes a communication connection unit 31, a storage unit 32, and a processing unit 33. The communication connection unit 31, the storage unit 32, and the processing unit 33 are connected to each other so as to be able to communicate with each other and to transmit and receive various information to and from each other.
[0020] The communication connection unit 31 is a communication interface that is connected to the network N and that communicates with the communication device 2 on the network N by transmitting and receiving signals (information).
[0021] The storage unit 32 is a storage device that stores various data (information). The storage unit 32 is realized by, for example, a semiconductor memory element such as a RAM or a flash memory, a hard disk, an optical disk, or the like. The storage unit 32 stores, for example, programs for the surveillance device 3 to realize various functions. The programs stored in the storage unit 32 include a program for causing the communication connection unit 31 to function, a program for causing the processing unit 33 to function, and the like. The storage unit 32 also stores various data such as data necessary for various processes in the processing unit 33. These various data are read out of the storage unit 32 by the processing unit 33, etc., as necessary.
[0022] The processing unit 33 is a computing device that realizes various processing functions in the monitoring device 3. The processing unit 33 is configured with an electronic circuit mainly including a well-known microcomputer including a central processing unit such as a CPU (Central Processing Unit). The processing unit 33 realizes each processing function by executing a program read from the storage unit 32, for example.
[0023] The above describes an overview of the overall configuration of the communication network system 1 and the monitoring device 3 according to this embodiment. With such a configuration, the processing unit 33 of the monitoring device 3 according to this embodiment has a function of detecting a communication failure in the network N, restricting communication, and executing various processes for lifting the communication restriction based on various periods that are individually set in advance for each communication device 2. In addition, the storage unit 32 of the monitoring device 3 according to this embodiment has a storage area for storing various data.
[0024] Specifically, the storage unit 32 of this embodiment is configured to include, functionally and conceptually, a failure recovery planned period storage area 32A in order to realize various processing functions by the processing unit 33, as shown in FIG.
[0025] The planned failure recovery period storage area 32A is a storage area for storing a planned failure recovery period used in a process related to the release of communication restriction by the processing unit 33. The planned failure recovery period is a period that is individually set in advance for a plurality of communication devices 2 (each ECU 2A, each HUB 2B, etc.), and is a period expected for recovery from a communication failure when the communication failure occurs.
[0026] The communication failure referred to here refers to software failures such as buffer write errors that can be restored to a normal state by software resetting, and does not include hardware failures such as disconnections or physical breakdowns. In other words, this planned failure recovery period typically corresponds to the period required for software resetting of the communication device 2 and devices on the communication path, and is set in advance individually as a period according to each communication device 2 based on, for example, actual device evaluation.
[0027] The planned failure recovery period may be registered in advance in the planned failure recovery period storage area 32A, or may be notified from the communication device 2 to the monitoring device 3 when starting communication with each communication device 2, and may be registered in the planned failure recovery period storage area 32A. Also, the planned failure recovery period may be determined by learning the time from an actual failure to recovery.
[0028] 2, in order to realize the above-mentioned various processing functions, the processing unit 33 of this embodiment is functionally configured to include a GW processing unit 33A, a monitoring processing unit 33B, and a communication restriction processing unit 33C. The processing unit 33 realizes each processing function of the GW processing unit 33A, the monitoring processing unit 33B, and the communication restriction processing unit 33C by executing a program read from the storage unit 32, for example.
[0029] The GW processing unit 33A is a part having a function capable of executing a protocol conversion process. The GW processing unit 33A executes a protocol conversion process for converting different protocols used in the network N into each other when relaying communication between devices on the network N.
[0030] The monitoring processing unit 33B is a part having a function capable of executing a monitoring process. The monitoring process executed by the monitoring processing unit 33B is a process of checking the connection to a plurality of communication devices 2 via the network N and detecting an abnormal device from the plurality of communication devices 2.
[0031] More specifically, in the monitoring process, the monitoring processor 33B transmits a connection confirmation (request) to each of the multiple communication devices 2 from the communication connection unit 31 via the network N, and executes a process of confirming the existence of each communication device 2. The connection confirmation (request) is, for example, Ethernet (registered trademark) OAM (Operations Administration Maintenance) or ping, which is a command capable of confirming a connection in a communication network. The monitoring processor 33B may identify the destination communication device 2 based on various addresses, etc., and may transmit the connection confirmation at regular intervals, or may transmit the connection confirmation at any timing.
[0032] In the monitoring process, the monitoring processor 33B executes a process of receiving a response to the connection confirmation from each communication device 2 via the network N. The monitoring processor 33B judges the presence or absence of a response from each communication device 2 for each control period, and judges whether or not there has been a response to the connection confirmation for each communication device 2 based on various addresses, identifiers, etc. included in the response. The monitoring processor 33B judges a communication device 2 that has responded to the connection confirmation to be in a normal state (a state in which the existence of the device has been confirmed). On the other hand, the monitoring processor 33B judges a communication device 2 that has not responded to the connection confirmation to be in an abnormal state (a state in which the existence of the device has not been confirmed), and detects the communication device 2 as an abnormal device in which a communication failure (a failure in which the device cannot respond to a request) has occurred. The monitoring processor 33B identifies the abnormal device in which a communication failure has occurred based on various addresses, identifiers, etc.
[0033] In this manner, the monitoring processor 33B identifies an abnormal device in which a communication failure has occurred from among the multiple communication devices 2 through monitoring processing.
[0034] The communication restriction processing unit 33C is a part having a function capable of executing communication restriction processing and communication restriction release processing.
[0035] The communication restriction process executed by the communication restriction processing unit 33C is a process of restricting communications involving the abnormal device other than the abnormal device detected by the above-mentioned monitoring process, for the communication devices 2 other than the abnormal device.
[0036] More specifically, in the communication restriction process, the communication restriction processing unit 33C transmits a communication restriction instruction from the communication connection unit 31 via the network N to the other communication devices 2 other than the abnormal device in which the communication failure has occurred, and executes a process of restricting communication between the abnormal device and the other communication devices 2. Through this communication restriction process, the communication network system 1 can prevent communication to the abnormal device from being repeated unnecessarily, and for example, can prevent the communication band in the network N from being used unnecessarily.
[0037] On the other hand, the communication restriction release process executed by the communication restriction processing unit 33C is a process for releasing the restriction on communication with the communication devices 2 other than the abnormal device executed by the above-mentioned communication restriction process.
[0038] In the communication restriction release process, the communication restriction processing unit 33C of this embodiment executes a process of releasing the restriction on communication with other communication devices 2 based on the planned failure recovery period set for the abnormal device among the planned failure recovery periods set individually in advance for the multiple communication devices 2. In this case, the communication restriction processing unit 33C reads out the planned failure recovery period set for the abnormal device detected by the above-mentioned monitoring process from the planned failure recovery periods of each communication device 2 stored in the planned failure recovery period storage area 32A, and uses it for the communication restriction release process. In addition, the communication restriction processing unit 33C executes the communication restriction release process for the communication device 2 whose communication with the abnormal device is restricted by the above-mentioned communication restriction process.
[0039] More specifically, after the monitoring processing unit 33B detects an abnormal device, the communication restriction processing unit 33C of this embodiment executes a process of lifting the restriction on communication with the other communication device 2 when the planned failure recovery period set for the abnormal device has elapsed without performing another connection check for the abnormal device. In this case, the communication restriction processing unit 33C transmits a communication restriction lift instruction from the communication connection unit 31 via the network N to the communication device 2 for which communication restriction is being imposed, and executes a process of lifting the restriction on communication with the communication device 2. With this communication restriction lifting process, the communication network system 1 can lift the restriction on communication with the other communication device 2 without waiting for the next control period for connection check when the planned failure recovery period for the abnormal device has elapsed since the abnormal device was detected, thereby restoring communication.
[0040] Next, a processing procedure of a monitoring method in the communication network system 1 will be described with reference to the flowchart of FIG.
[0041] 3 includes a monitoring step (S1 to S3), a communication restriction step (S4), and a communication restriction release step (S5 to S6). Here, the processing for each of the above steps is executed by the processing unit 33 of the monitoring device 3.
[0042] First, the monitoring processing unit 33B of the processing unit 33 executes a step (S1) of transmitting a connection confirmation (request) to each of the multiple communication devices 2 from the communication connection unit 31 via the network N. In this example, the monitoring processing unit 33B transmits the connection confirmation at regular intervals.
[0043] Next, the monitoring processor 33B executes a step (S2) of determining whether or not a response to the connection confirmation has been received from each communication device 2 via the network N, that is, whether or not a response has been received.
[0044] If the monitoring processing unit 33B determines that a response has been received from the communication device 2, i.e., if it determines that a response has been received (S2: Yes), it determines that the communication device 2 is in a normal state, ends the current control cycle, and moves on to the next control cycle.
[0045] If the monitoring processing unit 33B determines that it has not received a response from the communication device 2, i.e., if it determines that there was no response (S2: No), it executes a step (S3) of detecting the communication device 2 as an abnormal device in which a communication failure has occurred.
[0046] The above-mentioned steps (S1 to S3) correspond to a monitoring step of checking the connections of multiple communication devices 2 connected to the network N and detecting abnormal devices from the multiple communication devices 2, and are executed for all communication devices 2 on the network N.
[0047] Then, the communication restriction processing unit 33C of the processing unit 33 executes a step (S4) of transmitting a communication restriction instruction from the communication connection unit 31 via the network N to the other communication devices 2 other than the abnormal device detected in the above-mentioned monitoring steps (S1 to S3).
[0048] This step (S4) corresponds to a communication restriction step for restricting communications involving the abnormal device other than the communication devices 2 detected in the above-mentioned monitoring steps (S1 to S3), and is executed for all communication devices 2 other than the abnormal device.
[0049] Then, the communication restriction processing unit 33C reads out the planned fault recovery period of the abnormal device detected in the above-mentioned monitoring steps (S1 to S3) from the planned fault recovery period memory area 32A, and executes a step (S5) of determining whether the planned fault recovery period has elapsed since the abnormal device was detected.
[0050] If the communication restriction processing unit 33C determines that the scheduled failure recovery period has not elapsed, it repeatedly executes step (S5).
[0051] If the communication restriction processing unit 33C determines that the planned fault recovery period has elapsed, it executes a step (S6) of sending a communication restriction lift instruction from the communication connection unit 31 via the network N to the communication device 2 on which communication restriction was executed in the above-mentioned communication restriction step (S4), ends the current control cycle, and moves on to the next control cycle.
[0052] The above-mentioned steps (S5 to S6) correspond to a communication restriction lifting step for lifting the restriction on communication for other communication devices 2 based on the planned fault recovery period set for the abnormal device, and are executed for all communication devices 2 for which communication restriction has been implemented.
[0053] The above-mentioned monitoring method can be realized by executing a prepared monitoring program on a computer constituting the monitoring device 3. This monitoring program causes the computer to execute each process such as the above-mentioned monitoring steps (S1 to S3), communication restriction step (S4), and communication restriction release step (S5 to S6).
[0054] Next, an example of the operation of the communication network system 1 configured as above will be described. Here, in order to easily explain the operation of the communication network system 1, first, the operation of the communication network system according to a comparative example will be described with reference to Fig. 4, and then the operation of the communication network system 1 according to the present embodiment will be described with reference to Fig. 5. The monitoring device 1003 of the communication network system according to the comparative example described in Fig. 4 does not perform the communication restriction release process based on the planned failure recovery period as described above, but performs connection confirmation, and releases the communication restriction after actually confirming the recovery of the abnormal device.
[0055] 4 and 5, for the sake of convenience, one of the ECUs 2A connected to the monitoring device (GW) 3, 1003 without going through the HUB 2B is denoted as "ECU2A-1," and one of the ECUs 2A connected to the HUB 2B is denoted as "ECU2A-2." In addition, in this description, it is assumed that the first ECU 2A, "ECU2A-1," is the communication device 2 subject to communication restrictions, and the second ECU 2A, "ECU2A-2," is the abnormal device.
[0056] The monitoring device 1003 according to the comparative example illustrated in Fig. 4 transmits a connection confirmation to each of the ECU2A-1, ECU2A-2, and HUB2B in a period T, and confirms the existence of each communication device 2 (ECU2A-1, ECU2A-2, and HUB2B). When a communication failure occurs in the ECU2A-2 at a point (time) t11, the monitoring device 1003 detects that a communication failure has occurred in the ECU2A-2 at a point t12 because there is no response to the connection confirmation transmitted to the ECU2A-2 in the next period T, and detects the ECU2A-2 as an abnormal device. After that, the monitoring device 1003 transmits a communication restriction instruction to the ECU2A-1 at a point t13, and restricts communication involving the ECU2A-2 to the ECU2A-1. If there is no response to the connection confirmation transmitted to the ECU 2A-2 in the next cycle T, the monitoring device 1003 determines that the communication failure of the ECU 2A-2 is still ongoing.
[0057] Then, immediately after that, at time t14, when the ECU2A-2 recovers from the communication failure, the monitoring device 1003 does not transmit a connection confirmation to the ECU2A-2 until the next cycle T, even in such a case, and therefore cannot detect the recovery of the ECU2A-2 from the communication failure until then. The monitoring device 1003 can finally detect the recovery of the ECU2A-2 from the communication failure at time t15 based on the response to the connection confirmation transmitted to the ECU2A-2 in the next cycle T. That is, in the communication network system according to the comparative example, depending on the timing of the connection confirmation, a delay T0 of up to the cycle T may occur between the actual recovery of the ECU2A-2 from the communication failure (time t14) and the detection of the recovery (time t15).
[0058] Thereafter, when the monitoring device 1003 detects recovery from the communication failure of the ECU 2A-2, it transmits a communication restriction lift instruction to the ECU 2A-1 that is implementing the communication restriction at time t16, and lifts the restriction on communications for that ECU 2A-1.
[0059] As described above, in the communication network system according to the comparative example, the period from time t11 to time t16 corresponds to the period T1 required from the occurrence of a communication failure in ECU 2A-2 to the recovery of communication in the entire system.
[0060] 5 detects that a communication failure has occurred in the ECU2A-2 at time t12, detects the ECU2A-2 as an abnormal device, and does not check the connection to the ECU2A-2 again. Then, at time t14-1, which is the elapse of the planned failure recovery period TA set for the ECU2A-2 from time 12 when the monitoring device 3 detects that a communication failure has occurred in the ECU2A-2, the monitoring device 3 transmits a communication restriction release instruction to the ECU2A-1 that is implementing the communication restriction, and releases the restriction on communication for the ECU2A-1.
[0061] As a result, in the communication network system 1 of this embodiment, the period from time t11 to time t14-1 is the period T2 required from the occurrence of a communication failure in ECU2A-2 to the restoration of communication in the entire system, which is relatively short compared to the above-mentioned period T1.
[0062] In addition, in the communication network system 1, if the failure in the communication device 2 is due to a hardware failure such as a broken wire or a physical breakdown, the detection of the communication failure, the restriction of communication, and the release of the restriction of communication will be repeated even if the above-mentioned processing is performed. In such a case, the monitoring device 3 can determine that it is a hardware failure and move to another processing.
[0063] The communication network system 1, monitoring device 3, and monitoring program described above perform connection checks on multiple communication devices 2 connected to the network N and detects an abnormal device from the multiple communication devices 2. When the monitoring device 3 detects an abnormal device, it restricts communications involving the abnormal device to other communication devices 2 other than the abnormal device. Through this processing, the communication network system 1 can prevent communication to the abnormal device from being repeated unnecessarily, and can, for example, prevent the communication bandwidth in the network N from being used unnecessarily.
[0064] Thereafter, the monitoring device 3 lifts the restriction on communication with other communication devices 2 based on the planned failure recovery period that is individually set in advance for the abnormal device. With this process, the communication network system 1 can automatically lift the restriction on communication with other communication devices 2 according to the planned failure recovery period that is expected to be required for the communication device 2 that has become the abnormal device to recover from the failure, and recover the communication. As a result, the communication network system 1 can relatively shorten the period required from the occurrence of a communication failure, through the communication restriction, to the lifting of the communication restriction. This allows the communication network system 1 to realize faster recovery of communication while suppressing costs, without implementing additional functions such as a self-diagnosis function or a function for notifying recovery from a communication failure.
[0065] As described above, the communication network system 1, the monitoring device 3, and the monitoring program can properly restore communications, for example, by shortening the time that communications are suppressed in the event of a network failure, and achieving faster restoration of communications.
[0066] More specifically, the communication network system 1, the monitoring device 3, and the monitoring program can lift the restriction on communication with other communication devices 2 and restore communication without waiting for the next connection confirmation cycle when the planned failure recovery period for the abnormal device has elapsed from the time when the abnormal device is detected. This process enables the communication network system 1 to suppress delays between the recovery of the communication failure of the actual abnormal device and the lifting of the communication restriction for other communication devices 2, regardless of the timing of the connection confirmation. As a result, the communication network system 1, the monitoring device 3, and the monitoring program can properly restore communication as described above.
[0067] [Embodiment 2] The communication network system, monitoring device, and monitoring program according to the second embodiment differ from those according to the first embodiment in the execution conditions of the communication restriction process. In the following, the same components as those in the above-mentioned embodiments are given the same reference numerals, and the duplicated explanations of the common configurations, actions, and effects are omitted as much as possible (the same applies below).
[0068] The communication network system 1, the monitoring device 3, and the monitoring program of this embodiment differ from those of the first embodiment in terms of the execution conditions for the communication restriction process, as shown in Fig. 6. The other configurations of the communication network system 1, the monitoring device 3, and the monitoring program of this embodiment are substantially the same as those of the first embodiment.
[0069] The communication restriction processing unit 33C of the monitoring device 3 of this embodiment does not restrict communications with other communication devices 2 when the planned failure recovery period set for the abnormal device is shorter than a preset first determination period.
[0070] For example, as shown in the flowchart of FIG. 6, after detecting an abnormal device (S3), the communication restriction processing unit 33C reads out the expected failure recovery period of the detected abnormal device from the expected failure recovery period storage area 32A. Then, the communication restriction processing unit 33C executes a step (S4A) of judging whether or not the expected failure recovery period set for the abnormal device is shorter than a first judgment period set in advance. If the communication restriction processing unit 33C judges that the expected failure recovery period is equal to or longer than the first judgment period (S4A: No), it proceeds to step (S4) and executes communication restriction processing on the communication devices 2 other than the abnormal device. On the other hand, if the communication restriction processing unit 33C judges that the expected failure recovery period is shorter than the first judgment period (S4A: Yes), it does not execute communication restriction processing on the communication devices 2 other than the abnormal device, does not restrict communication, ends the current control period, and proceeds to the next control period.
[0071] Here, as described above, in the communication restriction process, a process of restricting communication is executed by transmitting a communication restriction instruction to the communication devices 2 other than the abnormal device. For example, the monitoring device 1003 according to the comparative example of FIG. 7 detects the abnormal device and then executes the communication restriction process on the other communication devices 2. In this case, in the communication network system according to the comparative example, if the planned failure recovery period of the abnormal device is relatively short compared to the connection confirmation period T, the communication restriction may be performed even though the abnormal device has already recovered, which may result in a longer period required for communication recovery in the entire system. For example, in the communication network system according to the comparative example illustrated in FIG. 7, the communication failure of the ECU2A-2 has already been recovered at time t22 immediately after the abnormal device is detected at time t21. Therefore, in the communication network system according to this comparative example, the subsequent communication restriction process results in a relatively longer period T3 required for communication recovery in the entire system by the period T00 from time t22 when the communication failure of the ECU2A-2 is actually recovered to time t23 when the communication restriction release process is performed.
[0072] In contrast, the communication restriction processing unit 33C of this embodiment does not restrict communication with other communication devices 2 when the failure recovery planned period set for the abnormal device is shorter than the first judgment period. In other words, the communication restriction processing unit 33C does not perform the communication restriction processing when the failure recovery planned period is relatively short and it is highly likely that the failure has already been recovered when the communication restriction processing is performed. With this processing, the communication network system 1 can set the period T4 required from the occurrence of a communication failure in the ECU 2A-2 to the communication recovery of the entire system to a period relatively shorter than the above-mentioned period T3 in the case where the period required for communication recovery of the entire system would be longer if communication restriction were performed, as exemplified in FIG. 8.
[0073] Here, the first judgment period described above is a judgment threshold value that is set in advance for the expected period of failure recovery of the abnormal device in order to judge whether or not to execute the communication restriction process. For example, in the communication network system 1, it is considered that the communication restriction is not performed if the expected period of failure recovery of the abnormal device is shorter than the connection confirmation cycle T even if only slightly. For example, in the communication network system 1, if the connection confirmation cycle T is 300 msec and the expected period of failure recovery of the abnormal device is 200 msec, when the communication restriction is performed, the communication is stopped for at least about 300 msec, but when the communication restriction is not performed, the communication is resumed in at most 200 msec. From the above viewpoint, the first judgment period is set in advance as a sufficiently short period by actual device evaluation, etc., based on the connection confirmation cycle T, etc., and taking into account the allowable range of unnecessary communication to the abnormal device due to not performing the communication restriction.
[0074] The communication network system 1, the monitoring device 3, and the monitoring program of the present embodiment described above can properly restore communication, similarly to the first embodiment.
[0075] Furthermore, when the planned failure recovery period set for the abnormal device is shorter than the first judgment period, the communication network system 1, monitoring device 3, and monitoring program of this embodiment do not restrict communication with other communication devices 2. This process enables the communication network system 1 to prevent communication restriction from lengthening the period required for communication recovery in the entire system. As a result, the communication network system 1, monitoring device 3, and monitoring program of this embodiment can more appropriately restore communication.
[0076] [Embodiment 3] The communication network system, monitoring device, and monitoring program according to the third embodiment differ from those of the second embodiment in the execution conditions of the communication restriction process.
[0077] The communication network system 1, monitoring device 3, and monitoring program of this embodiment shown in Fig. 9 differ from those of the above-mentioned embodiment 2 in terms of the execution conditions for the communication restriction process, as shown in Fig. 10. Other configurations of the communication network system 1, monitoring device 3, and monitoring program of this embodiment are substantially the same as those of the above-mentioned embodiment 2.
[0078] The storage unit 32 of this embodiment is conceptually configured to include a storage area 232B for a period required for lifting communication restriction in addition to a storage area 32A for a planned period for recovery from a failure.
[0079] The communication restriction lifting period storage area 232B is a storage area for storing a communication restriction lifting period used by the processing unit 33 to determine whether or not it is necessary to implement communication restriction. The communication restriction lifting period is a period that is individually set in advance for a plurality of communication devices 2 (each ECU 2A, each HUB 2B, etc.), and is a period expected from the transmission of a communication restriction lifting instruction until the restriction on communication is lifted when communication restriction is implemented. The communication restriction lifting period is individually set in advance as a period corresponding to each communication device 2, for example, by actual device evaluation or the like.
[0080] The period required for lifting communication restriction may be registered in advance in the storage area 232B for period required for lifting communication restriction, or may be notified from the communication device 2 to the monitoring device 3 when starting communication with each communication device 2, and may be registered in the storage area 232B for period required for lifting communication restriction. Also, the period required for lifting communication restriction may be learned by learning the time from the transmission of an actual instruction to lift communication restriction to the lifting of restriction.
[0081] In addition, the communication restriction processing unit 33C of the monitoring device 3 in this embodiment does not restrict communication with the other communication devices 2 if the communication restriction lifting period set for the other communication devices 2 other than the abnormal device, among the communication restriction lifting periods set individually in advance for the multiple communication devices 2, is longer than the preset second judgment period.
[0082] For example, as shown in the flowchart of FIG. 10, when the communication restriction processing unit 33C determines that the expected failure recovery period is equal to or longer than the first judgment period (S4A: No), it reads out the required period for lifting the communication restriction of the communication devices 2 other than the abnormal device from the required period for lifting the communication restriction storage area 232B. Then, the communication restriction processing unit 33C executes a step (S4B) of determining whether the required period for lifting the communication restriction set for the communication devices 2 that may be subject to the communication restriction is longer than the second judgment period set in advance. When the communication restriction processing unit 33C determines that the required period for lifting the communication restriction is equal to or shorter than the second judgment period (S4B: No), it proceeds to step (S4) and executes the communication restriction process for the communication devices 2 other than the abnormal device. On the other hand, when the communication restriction processing unit 33C determines that the required period for lifting the communication restriction is longer than the second judgment period (S4B: Yes), it does not execute the communication restriction process for the communication devices 2 other than the abnormal device, does not restrict communication, ends the current control period, and proceeds to the next control period. The communication restriction processing unit 33C performs the determination of step (S4B) for each of the communications devices 2 that may be subject to communication restriction, and executes step (S4) and subsequent steps for each of the communications devices 2 as necessary.
[0083] Here, as described above, in the communication restriction release process, a communication restriction release instruction is sent to the communication device 2 that is performing the communication restriction, and a process of releasing the communication restriction is executed. For example, the monitoring device 1003 according to the comparative example of FIG. 11 detects the recovery of the abnormal device, and then transmits a communication restriction release instruction to the other communication device 2 and executes the communication restriction release process. At this time, in the communication network system according to the comparative example, if the period required for the communication restriction release of the communication device 2 is relatively long, the period required for the communication recovery of the entire system may be longer by restricting the communication. For example, in the communication network system according to the comparative example illustrated in FIG. 11, the period T000 (corresponding to the above-mentioned period required for the communication restriction release) from the time t31 when the communication restriction release instruction is sent to the communication device 2 to the time t32 when the communication of the communication device 2 is actually resumed tends to be relatively long. Therefore, in the communication network system according to this comparative example, the period T4 required for the communication recovery of the entire system may be relatively longer depending on the length of the period T000 by performing the communication restriction process.
[0084] In contrast, when the period required for lifting the communication restriction set for the communication devices 2 other than the abnormal device is longer than the second determination period, the communication restriction processing unit 33C of this embodiment does not restrict communication with the other communication devices 2. In other words, the communication restriction processing unit 33C does not perform the communication restriction process for the communication devices 2 that require a relatively long period to lift the communication restriction. With this process, the communication network system 1 can set the period T6 required from the occurrence of a communication failure in the ECU 2A-2 to the recovery of communication in the entire system to a period relatively shorter than the above-mentioned period T5 when there is a communication device 2 that requires a relatively long period to lift the communication restriction, as exemplified in Fig. 12.
[0085] Here, the second determination period described above is a determination threshold value that is set in advance for a period required for lifting communication restriction of the communication device 2 in order to determine whether or not to execute communication restriction processing. The second determination period is set, for example, according to an allowable communication cutoff time due to a communication failure in the entire system.
[0086] For example, assume that in communication network system 1, the cycle T of connection confirmation is 50 msec, the planned fault recovery period of the abnormal device is 150 msec, the period required to lift the communication restriction of communication device 2 that may be subject to communication restriction is 70 msec, and the allowable communication cutoff time due to communication failure in the entire system is 250 msec. In this case, in communication network system 1, if communication restriction is imposed on communication device 2 that may be subject to communication restriction, the period required from the occurrence of communication failure to communication recovery in the entire system is [planned fault recovery period: 150 msec] + [time required to lift communication restriction: 70 msec] = 220 msec, and recovery is possible within the allowable communication cutoff time, so communication restriction processing is allowable.
[0087] On the other hand, for example, assume that in the communication network system 1, the connection confirmation period T is 50 msec, the planned failure recovery period of the abnormal device is 150 msec, the period required to lift the communication restriction of the communication device 2 that may be subject to the communication restriction is 120 msec, and the allowable communication cutoff time due to a communication failure in the entire system is 250 msec. In this case, in the communication network system 1, if communication restriction is imposed on the communication device 2 that may be subject to the communication restriction, the period required from the occurrence of the communication failure to the recovery of communication in the entire system will be [planned failure recovery period: 150 msec] + [time required to lift the communication restriction: 120 msec] = 270 msec, and recovery within the allowable communication cutoff time is not possible, so the communication restriction process is not executed.
[0088] From the viewpoint described above, the second judgment period is set in advance through actual equipment evaluation, etc., based on, for example, the allowable time for communication interruption due to communication failure in the entire system, while also taking into account the allowable range of unnecessary communication to abnormal devices due to not restricting communication.
[0089] The communication network system 1, the monitoring device 3, and the monitoring program of the present embodiment described above can properly restore communication, similarly to the second embodiment.
[0090] Furthermore, when the period required for lifting the communication restriction set for the communication devices 2 other than the abnormal device is longer than the second judgment period, the communication network system 1, monitoring device 3, and monitoring program of this embodiment do not restrict communication with the other communication devices 2. This process enables the communication network system 1 to prevent the period required for communication recovery in the entire system from being lengthened by restricting communication. As a result, the communication network system 1, monitoring device 3, and monitoring program of this embodiment can more appropriately restore communication.
[0091] The communication network system, monitoring equipment, and monitoring program according to the above-described embodiments of the present invention are not limited to the above-described embodiments, and various modifications are possible within the scope of the claims.
[0092] In the above description, the monitoring device 3 is configured by a gateway constituting a network device, and has a GW function for performing protocol conversion as well as a network monitoring function, but this is not limited thereto. The monitoring device 3 may be configured separately from the gateway.
[0093] In the above description, the communication network system 1 is described as being mounted on a vehicle and constituting an in-vehicle network system, but the present invention is not limited to this.
[0094] The processing unit 33 described above has been described as having each processing function realized by a single electronic circuit, but this is not limited to the above. The processing unit 33 may be realized by combining multiple independent electronic circuits and having each electronic circuit execute a program. The processing functions of the processing unit 33 may be realized by appropriately distributing or integrating them into a single or multiple processing circuits. The processing functions of the processing unit 33 may be realized in whole or in part by a program, or may be realized as hardware using wired logic or the like.
[0095] The program executed by the processing unit 33 described above is provided by being preinstalled in the storage unit 32 or the like. This program may be provided by being recorded on a computer-readable storage medium in a format that can be installed on these devices or in a format that can be executed. This program may also be provided or distributed by being stored on a computer connected to a network such as the Internet and downloaded via the network.
[0096] The communication network system, monitoring device, and monitoring program according to this embodiment may be configured by appropriately combining the components of the embodiments and modified examples described above. [Explanation of symbols]
[0097] 1. Communication network systems 2. Communications equipment 2A, 2A-1, 2A-2 ECU 2B HUB 3 Monitoring equipment 31 Communication connection 32 Storage section 32A Disaster recovery period storage area 232B Storage area for the period required for lifting communication restrictions 33 Processing section 33A GW Processing Unit 33B Monitoring processing section 33C Communication Restriction Processing Unit N Network TA Disaster Recovery Schedule
Claims
1. A network capable of communicating; A plurality of communication devices connected to the network; a monitoring device connected to the network, performing connection confirmation for the plurality of communication devices, detecting an abnormal device from the plurality of communication devices, and executing a process of restricting communications involving the abnormal device for the other communication devices other than the abnormal device; The monitoring device is capable of executing a process of releasing the restriction on communication with the other communication devices based on a planned failure recovery period set for the abnormal device among planned failure recovery periods that are individually set in advance for the plurality of communication devices and are expected to be required for failure recovery. Communication network system.
2. After detecting the abnormal device, the monitoring device executes a process of lifting the restriction on communication with the other communication devices when the planned failure recovery period set for the abnormal device has elapsed without performing the connection check for the abnormal device again. The communication network system according to claim 1 .
3. When the planned failure recovery period set for the abnormal device is shorter than a first determination period set in advance, the monitoring device does not restrict the communication with the other communication devices.
3. The communication network system according to claim 1 or 2.
4. the monitoring device does not restrict communication with the other communication device when the communication restriction lift required period set for the other communication device among periods that are individually set in advance for the multiple communication devices and are expected to be lifted for the restriction on communication, is longer than a second determination period set in advance; The communication network system according to any one of claims 1 to 3.
5. A communication connection unit connected to a network; a processing unit capable of executing a process of performing a connection check for a plurality of communication devices connected to the network, detecting an abnormal device from the plurality of communication devices, and restricting communications involving the abnormal device for the communication devices other than the abnormal device, The processing unit is capable of executing a process of releasing the restriction on communication with the other communication devices based on a planned failure recovery period set for the abnormal device among planned failure recovery periods that are individually set in advance for the multiple communication devices and are expected to be required for failure recovery. Surveillance equipment.
6. A connection check is performed for multiple communication devices connected to the network, and an abnormal device is detected from the multiple communication devices. Restricting communications involving the abnormal device with respect to other communication devices other than the abnormal device; lifting the restriction on communication with the other communication devices based on a planned failure recovery period set for the abnormal device among planned failure recovery periods expected for failure recovery, which are periods individually set in advance for the plurality of communication devices; Each process is executed by a computer. Surveillance program.
Citation Information
Patent Citations
Fault restoration method for distributed node system
JP1997083611A
Communication control method of packet switching system
JP1998013464A
Vehicle communication system and vehicle communication apparatus
JP2009105828A
Router device
JP2013179678A
Switch device, communication control method, and communication control program
JP2018113505A
