In-vehicle network system and program

Abstract

To obtain an in-vehicle network system with higher performance than conventional ones.SOLUTION: An in-vehicle network system includes an integrated ECU and multiple ECUs respectively arranged in multiple zones, and is applied to an in-vehicle network that performs data communication between the multiple zones and the integrated ECU via switches installed in the multiple zones. The network connection between the integrated ECU and the multiple zones includes a redundant system, and the switches installed in the multiple zones have a remote port mirroring function. The integrated ECU makes it possible to change the settings of the switches installed in the multiple zones.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an in-vehicle network system and a program. [Background technology]

[0002] Conventionally, a plurality of ECUs (Electronic Control Units) installed in a vehicle are connected via a communication network, and each ECU transmits and receives various vehicle data via the communication network. In addition, each ECU may communicate with the outside world via a mobile phone connected to the in-vehicle information terminal. The in-vehicle network that connects these ECUs is prone to increasing communication traffic, so efforts have been made to reduce the communication traffic in order to reduce the communication load on the in-vehicle network.

[0003] In recent years, as vehicles have come to be constantly connected to external networks, new services that utilize information inside the vehicle have been created. In addition, with the spread of the fifth generation mobile communication system, so-called 5G (5th Generation), and the shift to Ethernet (Ethernet is a registered trademark) in in-vehicle networks, in-vehicle networks are now capable of high-speed, large-volume, low-latency communication both inside and outside the vehicle. This has made it possible for in-vehicle networks to collect real-time vehicle information and the large volumes of data required for AI (Artificial Intelligence) learning.

[0004] Meanwhile, the trend for vehicle system architectures is toward a zonal architecture consisting of an integrated ECU and zone ECUs, based on the premise of high-performance ECUs and Ethernet capable of high-speed, large-volume communication. An integrated ECU is an integrated implementation of software that spans each domain of the vehicle. A zonal architecture is composed of zone ECUs that collect information from each location on the vehicle, such as the front, rear, left, and right, without depending on the domain.

[0005] Patent Document 1 describes a technique for reconstructing communication routes between ECUs while ensuring safety by determining the power supply state of a vehicle in order to reduce the communication load of an in-vehicle network system. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2020-88717 A Summary of the Invention [Problem to be solved by the invention]

[0007] However, in recent years, with the development of ADAS (Advanced Driver-Assistance Systems) and AD (Autonomous Driving) and the introduction of AI, there is a demand for more accurate understanding and simulation of vehicle conditions. In particular, there is a demand for collecting and utilizing raw data from on-board sensors and other sources via high-speed, large-volume, low-latency in-vehicle and out-of-vehicle communication networks.

[0008] In view of the above, an object of the present invention is to provide an in-vehicle network system with higher performance than conventional ones, and a program that can be applied to the in-vehicle network system. [Means for solving the problem]

[0009] In order to solve the above problems, for example, the configurations described in the claims are adopted. The present application includes multiple means for solving the above-mentioned problems. One example is an in-vehicle network that is mounted on a vehicle and includes an integrated ECU and multiple ECUs arranged in each of multiple zones, and performs data communication between the multiple zones and the integrated ECU via switches installed in the multiple zones, wherein the network connection between the integrated ECU and the multiple zones includes a redundant system, the switches installed in the multiple zones have a remote port mirroring function, and the integrated ECU enables settings of the switches installed in the multiple zones to be changed. Effect of the Invention

[0010] According to the present invention, the integrated ECU can obtain raw data from sensors and the like arranged in each zone without interfering with other communications within the in-vehicle network. Therefore, the raw data from sensors and the like arranged in each zone can be transmitted directly to the cloud through a high-speed, large-capacity, low-latency network. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing an overall configuration of an in-vehicle network system according to a first embodiment of the present invention. [Diagram 2] 1 is a functional block diagram of an integrated ECU of an in-vehicle network system according to a first embodiment of the present invention. [Diagram 3] FIG. 11 is a diagram showing the communication flow of raw sensor data, taking zone 1 as an example, when collection of raw sensor data is not requested from the cloud in accordance with a first embodiment of the present invention, and the communication flow of raw sensor data, taking zone 1 as an example, when collection of raw sensor data is requested from the cloud. [Figure 4] 5 is a flowchart showing an example of a server request process in an integrated ECU of the in-vehicle network system according to the first embodiment of the present invention. [Diagram 5]5 is a flowchart showing an example of a network configuration management process in an integrated ECU of the in-vehicle network system according to the first embodiment of the present invention. [Figure 6] 13 is a flowchart showing an example of a case where a zone is specified in a server request determination process in an integrated ECU of an in-vehicle network system according to a second embodiment of the present invention. [Figure 7] 13 is a flowchart showing an example of a case where a zone is specified in the network configuration management process in the integrated ECU of the in-vehicle network system according to the second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] <First embodiment> Hereinafter, an in-vehicle network system and a program according to a first embodiment of the present invention will be described with reference to the accompanying drawings.

[0013] FIG. 1 shows the overall configuration of an in-vehicle network system according to this embodiment. The vehicle 100 includes an integrated ECU 101, ECUs 113, 123, 133, and 143, devices 111, 112, 121, 122, 131, 132, 141, and 142 such as sensors, a communication device 102, and an in-vehicle network system 300 that interconnects them. The ECUs 113, 123, 133, and 143 are disposed in their respective zones (zone 1 to zone 4). The communication device 102 communicates with a cloud 200 that is outside the vehicle. In the following description, the multiple devices 111, 112, 121, 122, 131, 132, 141, and 142 are collectively referred to as "devices 111, etc." unless it is necessary to identify each individual device.

[0014] The in-vehicle network system 300 is composed of switches 110, 120, 130, and 140 arranged in each zone, a main switch 103 connected to an integrated ECU 101, and a secondary switch 104 as a redundant system. The secondary switch 104 connected to the integrated ECU 101 as a redundant system, and the switches 110, 120, 130, and 140 arranged in each zone have a remote port mirroring function.

[0015] When there is no request to acquire raw sensor data from the cloud 200, raw sensor data from devices 111 such as sensors arranged in each zone is transmitted to ECUs 113, 123, 133, 143 arranged in each zone through switches 110, 120, 130, 140 arranged in each zone. The raw sensor data is then processed in the ECUs 113, 123, 133, 143 arranged in each zone, and the processed data is sent to the integrated ECU 101 via the main switch 103.

[0016] An SDN (Software-Defined Network) controller 1 is disposed in the integrated ECU 101. This SDN controller 1 performs remote port mirroring settings for the switches 110, 120, 130, and 140 and the secondary switch 104 disposed in each zone. By implementing this remote port mirroring setting, the following output process of raw sensor data is performed: Raw sensor data from devices 111, such as sensors, arranged in each zone is output to the mirroring ports of the switches 110, 120, 130, and 140 arranged in each zone, and further, a copy of the raw sensor data is output to the port connected to the secondary switch 104.

[0017] By transmitting the received raw sensor data to the integrated ECU 101, the secondary switch 104 can transmit the data to the integrated ECU 101 without interfering with the communication of data processed by the ECUs 113, 123, 133, and 143 located in each zone and without increasing the communication load. The integrated ECU 101 transmits the raw sensor data to the communication device 102 via the secondary switch 104 , and the communication device 102 transmits the received raw sensor data to the cloud 200 .

[0018] FIG. 2 shows a configuration seen from the perspective of a function for transmitting raw sensor data arranged in the integrated ECU 101 to the cloud 200 using a remote port mirroring function. 2, the integrated ECU 101 is configured as a so-called computer, including a memory 10 and a CPU 20. The memory 10 and the CPU 20 are connected to each other via an internal bus or an adapter. The memory 10 is a storage unit that stores various information including various programs that define the operation of the CPU 20. In this embodiment, a server request judging program 2, a network configuration management program 3, a raw sensor data receiving program 4, and a raw sensor data transmitting program 5 are stored.

[0019] The server request determination program 2 is a program for determining the contents of a vehicle data collection request obtained from the server via the cloud 200 . The network configuration management program 3 is a program that manages the configuration of the in-vehicle network system 300 . The raw sensor data receiving program 4 is a program for the SDN controller 1 to change the settings of the switches 103, 104, 110, 120, 130, and 140 of the in-vehicle network system 300 and to receive raw sensor data via the secondary switch 104. The raw sensor data transmission program 5 is a program for transmitting the received raw sensor data to the cloud 200 .

[0020] The CPU 20 is a control unit that reads the program stored in the memory 10 and executes the read program to perform control. Specifically, the CPU 20 receives an instruction regarding vehicle data collection transmitted from the cloud 200 via the communication device 102, and executes a judgment using the server request judgment program 2. Then, the CPU 20 instructs the network configuration management program 3 to change the network configuration based on the judgment result. Furthermore, the CPU 20 instructs the SDN controller 1 to change the network configuration according to the contents of the instruction in the network configuration management program 3.

[0021] The SDN controller 1, in accordance with an instruction from the network configuration management program 3, sets or cancels remote port mirroring for the secondary switch 104 and the switches 110, 120, 130, and 140 arranged in each zone.

[0022] FIG. 3 illustrates how raw sensor data flows from a device 112, such as a sensor located in zone 1, when the raw sensor data has not been requested to be sent to the cloud 200 and when the raw sensor data has been requested to be sent to the cloud, using zone 1 as an example. When raw sensor data is not requested, as shown by the dashed line at the top of Figure 3, raw sensor data from a device 112 such as a sensor located in zone 1 is transmitted to an ECU 113 located in zone 1 via a switch 110 located in zone 1.

[0023] When raw sensor data is requested, the SDN controller 1 performs remote port mirroring setting processing on the switch 110 and the secondary switch 104 arranged in the zone, and remote port mirroring is set. As a result, as shown by the dashed line at the bottom of Fig. 3, raw sensor data of the device 112 such as a sensor arranged in zone 1 is transmitted to the ECU 113 arranged in zone 1 via the switch 110 arranged in zone 1. Furthermore, as shown by the thick dashed line at the bottom of Fig. 3, the raw sensor data is copied by the switch 110 arranged in zone 1 and transmitted to the secondary switch 104, and transmitted from the secondary switch 104 set with remote port mirroring to the integrated ECU 101. As a result, the integrated ECU 101 performs raw sensor data acquisition processing.

[0024] FIG. 4 is a flowchart showing an example of processing performed when the server request determination program 2 runs on the integrated ECU 101. In FIG. An instruction regarding vehicle data collection transmitted from the cloud 200 is received by the server request determination program 2 of the integrated ECU 101 via the communication device 102 (step S101). The server request determination program 2 determines whether the received server request is a request to start transmitting raw sensor data or a request to stop transmitting raw sensor data (step S102).

[0025] If the server request received in step S102 is a request to transmit raw sensor data ("start request" in step S102), the server request determination program 2 instructs the network configuration management program 3 to start remote port mirroring (step S104). Furthermore, if the request is a request to end transmission of raw sensor data in step S102 ("end request" in step S102), the server request determination program 2 instructs the network configuration management program 3 to end remote port mirroring (step S103). After issuing the instruction in step S103 or step S104, the server request judgment program 2 returns to the reception in step S101.

[0026] FIG. 5 is a flowchart showing an example of processing performed when the network configuration management program 3 runs on the integrated ECU 101. The network configuration management program 3 receives an instruction from the server request determination program 2 (step S201). The network configuration management program 3 determines whether the instruction received from the server request determination program in step S201 is a remote port mirroring start request or a remote port mirroring end request (step S202).

[0027] If the instruction determined in step S202 is an instruction to start remote port mirroring ("start request" in step S102), the network configuration management program 3 instructs the SDN controller 1 to set remote port mirroring (step S204). If the instruction determined in step S202 is an instruction to end remote port mirroring ("end request" in step S102), the network configuration management program 3 instructs the SDN controller 1 to set the end of remote port mirroring (step S203). After issuing the instruction in step S203 or step S204, the network configuration management program 3 returns to the reception in step S201.

[0028] As described above, according to this embodiment, the integrated ECU 101 can transmit raw data obtained by the devices 111 such as sensors arranged in each zone to the cloud 200 as is through a high-speed, large-capacity, low-latency network. That is, the network connection from each zone to the integrated ECU 101 is configured with a redundant system having the sub switch 104 in addition to the main switch 103, and further, each of the switches 110, 120, 130, and 140 has a remote port mirroring function. Therefore, the integrated ECU 101 can transmit raw sensor data obtained by the devices 111 such as sensors to the communication device 102 via the sub switch 104, and transmit the raw sensor data to the cloud 200. This communication with the cloud 200 is communication using the sub switch 104, which is a redundant system, and can transmit the raw sensor data as is to the cloud 200 through a high-speed, large-capacity, low-latency network without impeding other communications in the in-vehicle network.

[0029] 4 and 5, remote port mirroring is set based on a request to send raw sensor data from the server or a request to end transmission, so that remote port mirroring is set only when necessary. In particular, the integrated ECU 101 issues an instruction to set remote port mirroring when a request to start collecting raw sensor data is made, and issues an instruction to cancel the remote port mirroring setting when a request to end collecting raw sensor data is made, thereby enabling appropriate setting and cancellation.

[0030] <Second embodiment> Next, a second embodiment of the present invention will be described with reference to Figures 6 and 7. The second embodiment shown in Figures 6 and 7 applies the configuration explained in the first embodiment using Figures 1 to 3, and the reference symbols of the respective components are the same as those explained in the first embodiment. In this embodiment, the processing when the server request determination program 2 is executed in the integrated ECU 101 and the processing when the network configuration management program 3 is executed in the integrated ECU 101 are different.

[0031] FIG. 6 is a flowchart in the case where the server request determination program 2 in this embodiment runs on the integrated ECU 101, and is a flowchart in the case where a request to start and end transmission of raw sensor data is made individually to each zone. The server request determination program 2 of the integrated ECU 101 receives an instruction regarding vehicle data collection transmitted from the cloud 200 via the communication device 102 (step S301).

[0032] The server request determination program 2 determines whether the received server request is a request to transmit raw sensor data or a request to end transmission of raw sensor data (step S302). If the request is for sending raw sensor data in step S302 ("request to start" in step S302), the server request determination program 2 determines whether a zone is specified (step S304). If no zone is specified in step S304 ("none" in step S302), the server request determination program 2 instructs the network configuration management program 3 to start remote port mirroring for all zones (step S307). If a zone is specified in step S304 (YES in step S302), the server request determination program 2 instructs the network configuration management program 3 to start remote port mirroring of the specified zone (step S308).

[0033] If it is determined in step S302 that the request is for ending transmission of raw sensor data ("end request" in step S302), the server request judgment program 2 judges whether a zone is specified (step S303). If no zone is specified in step S303 ("None" in step S303), the server request determination program 2 instructs the network configuration management program 3 to end remote port mirroring for all zones (step S305). If a zone is specified in step S303 (YES in step S303), the server request determination program 2 instructs the network configuration management program 3 to end remote port mirroring for the specified zone (step S306). After issuing an instruction to end remote port mirroring for the specified zone in step S306, and after issuing an instruction to start remote port mirroring for the specified zone in step S308, the server request judgment program 2 returns to the receiving process in step S301.

[0034] FIG. 7 is a flowchart when the network configuration management program 3 runs on the integrated ECU (101), and when a request to start and end remote port mirroring is made individually for each zone.

[0035] The network configuration management program 3 receives an instruction from the server request determination program 2 (step S401). The network configuration management program 3 determines whether the instruction received from the server request determination program is a remote port mirroring start request or a remote port mirroring end request (step S402). If the command is to start remote port mirroring in step S402 ("START REQUEST" in step S402), the network configuration management program 3 determines whether a zone is specified (step S404). If no zone is specified in step S404 ("NONE" in step S404), the network configuration management program 3 instructs the SDN controller 1 to set remote port mirroring for all zones (step S407). If a zone is specified in step S404 (YES in step S404), the network configuration management program 3 instructs the SDN controller 1 to set remote port mirroring for the specified zone (step S408).

[0036] If the command is to end remote port mirroring in step S402 ("end request" in step S402), the network configuration management program 3 determines the zone designation (step S403). If no zone is specified in step S403 ("None" in step S403), the network configuration management program 3 instructs the SDN controller 1 to end the remote port mirroring setting for all zones (step S405). If a zone is specified in step S403 (YES in step S403), the network configuration management program 3 instructs the SDN controller 1 to set the end of remote port mirroring for the specified zone (step S406). After instructing the end of remote port mirroring for the specified zone in step S406, and after instructing the setting of remote port mirroring for the specified zone in step S408, the network configuration management program 3 returns to the receiving process in step S401.

[0037] As described above, according to this embodiment, similarly to the first embodiment, the integrated ECU 101 can transmit raw data obtained from devices 111 such as sensors arranged in each zone directly to the cloud 200 via a high-speed, large-capacity, low-latency network. In the case of the second embodiment, remote port mirroring can be configured individually for each zone, and raw data obtained from devices 111 such as sensors placed in each zone can be more appropriately transmitted to the cloud 200.

[0038] <Modification> It should be noted that the embodiment examples described so far have been described in detail in order to explain the present invention in an easily understandable manner, and are not necessarily limited to those having all of the configurations described.

[0039] For example, the configuration of the integrated ECU 101 and each zone, and the configuration including the primary switch 103 and secondary switch 104 shown in Fig. 1 are only examples, and the present invention can be applied to other configurations. Also, in Fig. 3, an example has been described in which the SDN controller 1 performs remote port mirroring settings for the switches 110, 120, 130, and 140 in each zone and the secondary switch 104, but the remote port mirroring setting may be performed for the primary switch 103.

[0040] 1 to 3, only control lines and information lines that are considered necessary for explanation are shown, and not all control lines and information lines in the product are shown. In reality, it can be considered that almost all components are connected to each other. Furthermore, the process flows shown in the flowcharts of FIGS. 4 to 7 are also examples, and so long as the process results are the same, the order of some processes may be changed or multiple processes may be executed simultaneously.

[0041] In this embodiment, the CPU 20 in the integrated ECU 101 performs processing under the control of the CPU 20, and the programs 2, 3, 4, and 5 stored in the memory 10 and the SDN controller 1. Alternatively, some or all of the functions performed by the programs 2, 3, 4, and 5 and the SDN controller 1 may be realized by hardware such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). In addition, each program 2, 3, 4, 5 and the SDN controller 1 may be stored in a non-volatile storage or memory within the computer device that constitutes the integrated ECU 101, or may be stored and transferred on a recording medium such as an external memory, an IC card, an SD card, or an optical disk. [Explanation of symbols]

[0042] 1. SDN controller 2...Server request judgment program 3. Network configuration management program 4…Raw sensor data reception program 5…Raw sensor data transmission program 10. Memory 20…CPU 100…Vehicle 101…Integrated ECU 102...Communication equipment 103…Positive switch 104…Secondary switch 110…Switch located in Zone 1 111: Sensors etc. located in Zone 1 112: Sensors etc. located in Zone 1 113…ECU located in Zone 1 120…Switch located in Zone 2 121: Sensors etc. located in Zone 2 122: Sensors etc. located in Zone 2 123…ECU located in Zone 2 130…Switch located in Zone 3 131...Sensors etc. located in Zone 3 132: Sensors etc. located in Zone 3 133…ECU located in Zone 3 140…Switch located in Zone 4 141...Sensors etc. located in Zone 4 142...Sensors etc. located in Zone 4 143…ECU located in Zone 4 200…Cloud 300…In-vehicle network system

Claims

1. An in-vehicle network is mounted on a vehicle, and includes an integrated ECU and a plurality of ECUs disposed in a plurality of zones, and performs data communication between the plurality of zones and the integrated ECU via switches disposed in the plurality of zones, The network connection between the integrated ECU and the plurality of zones includes a redundant system, The switches installed in the plurality of zones have a remote port mirroring function, The integrated ECU enables changing the settings of the switches installed in the plurality of zones. In-vehicle network system.

2. A communication device that communicates with an external server is connected to the in-vehicle network, The integrated ECU transmits raw sensor data obtained in any one of the plurality of zones and copied by the remote port mirroring function to the communication device using the redundant network configuration, and the communication device transmits the raw sensor data to the server. The in-vehicle network system according to claim 1 .

3. The integrated ECU determines whether the request from the server is a raw sensor data collection request start request or a raw sensor data collection request end request, and issues an instruction to change the network configuration. The in-vehicle network system according to claim 2 .

4. The instruction to change the network configuration instructs the switch to set remote port mirroring when a request to start collecting raw sensor data is made, and instructs the switch to cancel the setting of remote port mirroring when a request to end collecting raw sensor data is made. The in-vehicle network system according to claim 3 .

5. A program for controlling, by a computer, communication between an integrated ECU mounted on a vehicle and a plurality of ECUs arranged in each of a plurality of zones, the communication being carried out over a network via switches installed in the plurality of zones, and the network connection between the integrated ECU and the plurality of zones being provided with a redundant system, a remote port mirroring setting process for setting remote port mirroring in the switches installed in the plurality of zones; a raw sensor data acquisition process in which the integrated ECU acquires the raw sensor data copied by the remote port mirroring set in the setting process. program.

Images