Vehicle-mounted communication system, vehicle-mounted communication method, and computer program
The in-vehicle communication system addresses the lack of virtual networks in CAN by processing frames with logical IDs, ensuring secure and efficient communication across mixed protocols, enabling virtual network management and safety in Software Defined Vehicles.
Patent Information
- Application Number
- PCT/JP2026/014715
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-04-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing in-vehicle communication networks, such as CAN, lack a mechanism for implementing virtual networks, which is necessary for the transition to Software Defined Vehicles and the coexistence of CAN and Ethernet protocols, and there is a need to separate vehicle control communications for safety and security, especially with third-party software involvement.
An in-vehicle communication system that utilizes a receiver to process communication frames with logical network IDs, enabling filtering and routing based on these IDs, even in protocols without specified logical network mechanisms, using modules like vCID and vNet processing to manage virtual networks over CAN and Ethernet.
Enables the use of virtual networks in existing communication protocols, enhancing security by isolating networks, managing multiple applications independently, and facilitating the transition from CAN to Ethernet while maintaining communication integrity.
Smart Images

Figure 00000026_0000 
Figure 00000028_0000 
Figure 00000029_0000
Abstract
Description
In-vehicle communication system, in-vehicle communication method, and computer program Cross-reference to related applications
[0001] This application is based on Japanese Application No. 2025-78021 filed on May 8, 2025, the entire content of which is incorporated herein by reference.
[0002] The present disclosure relates to a communication system mounted on a vehicle, an in-vehicle communication method, and a computer program.
[0003] In Ethernet (registered trademark), a virtual or logical network mechanism using vLAN (Virtual LAN) technology exists. In contrast, for example, the standard specification of CAN (Controller Area Network), which is widely used for in-vehicle communication, does not provide a mechanism for implementing a virtual network.
[0004] Japanese Unexamined Patent Application Publication No. 2018-229405
[0005] Currently, the concept of vehicles referred to as SDV (Software Defined Vehicle), in which various functions are implemented by software, is being advanced. Under such circumstances, there is a possibility that the in-vehicle communication network will be opened to third parties who develop software. In that case, it is desirable that communications related to vehicle control are separated on the network from the viewpoint of safety and security.
[0006] It is also assumed that the amount of information transmitted within the vehicle will increase, and there is a possibility that the IDs used in CAN communication will be insufficient. Furthermore, although the in-vehicle communication network protocol is expected to shift from CAN to in-vehicle Ethernet, platforms in which CAN and Ethernet coexist may also appear during this transition period. In that case, if a virtual network corresponding to the VLAN on the Ethernet side can also be implemented in CAN, coexistence should be facilitated.
[0007] This disclosure is made in view of the above circumstances, and its purpose is to provide an in-vehicle communication system, an in-vehicle communication method, and a computer program that enable the use of a logical network even in communication protocols that do not have a mechanism for utilizing a logical network.
[0008] The in-vehicle communication system according to claim 1 includes a receiver that receives a communication frame in a format based on a predetermined in-vehicle communication protocol from a communication bus. A portion of the fields of the communication frame stores a logical network ID, which is an identifier of a logical network implemented on the in-vehicle communication protocol. When the receiver receives a communication frame, the logical network ID processing unit identifies the logical network ID and performs either filtering or routing of the communication frame, or both, according to the identified logical network ID.
[0009] With this configuration, even in communications conforming to in-vehicle communication protocols where the use of a logical network is not specified in the specifications, it becomes possible to use a logical network by processing the communication frame according to the logical network ID stored in the communication frame.
[0010] According to the in-vehicle communication system described in claim 2, the communication based on the in-vehicle communication protocol is a multi-master communication. According to the in-vehicle communication system described in claim 3, the communication frame stores a logical frame ID, which is an identifier defined for each logical communication frame in the logical network, in part of its field. When the receiver receives a communication frame, the logical frame ID processing unit identifies the logical frame ID and filters the logical communication frame according to the identified logical frame ID.
[0011] According to the in-vehicle communication system described in claim 4, a communication frame contains a logical identifier in a part of its field that indicates that the communication frame is associated with the logical network. When the receiver receives a communication frame and recognizes the logical identifier, it forwards the communication frame to the logical network ID processing unit. This makes it possible for the logical network ID processing unit to process the communication frame containing the logical identifier within the logical network.
[0012] The above-mentioned objectives and other objectives, features and advantages of this disclosure will become clearer from the following detailed description with reference to the attached drawings. The drawings are as follows: Figure 1 is a diagram showing the configuration of a vehicle ECU in a first embodiment; Figure 2 is a diagram (part 1) showing an example of how vNetID and vCID are stored in the data field of a CAN communication frame; Figure 3 is a diagram (part 2) showing an example of how vNetID and vCID are stored in the data field of a CAN communication frame; Figure 4 is a flowchart showing the processing when a CAN communication frame is transmitted; Figure 5 is a flowchart showing the processing when a CAN communication frame is received; Figure 6 is a flowchart showing the subroutine processing of step S20; and Figure 7 shows the CAN controller / Figure 13 is a diagram showing the state of CAN communication frames processed between transceivers. Figure 8 shows the configuration of the vehicle ECU in the second embodiment. Figure 9 shows the configuration of the in-vehicle communication system in the third embodiment. Figure 10 shows the mode of mutual conversion when transferring CAN communication frames between normal CAN communication and a virtual network. Figure 11 shows the configuration of the in-vehicle communication system in the fourth embodiment. Figure 12 shows the correspondence between each physical port and their respective virtual network IDs, vNetID and vLANID. Figure 13 shows the configuration of the in-vehicle communication system in the fifth embodiment.
[0013] (First Embodiment) As shown in Figure 1, the vehicle ECU 1 in the in-vehicle communication system is an electronic control device and communication unit that performs in-vehicle communication with other ECUs in accordance with the CAN in-vehicle communication protocol. The vehicle ECU 1 includes an application program 2, a CAN parser / composer 3, a vCID processing module 4, a vNet processing module 5, a security module 6, and a CAN controller / transceiver 7. The vehicle ECU 1 in this embodiment is configured to enable the realization of a virtual network over CAN communication.
[0014] App 2 is an application program that operates by sending and receiving vehicle information with the CAN communication bus 8. For example, it could be a control application for an OEM or an application developed by a third party. The CAN analysis and configuration unit 3 analyzes the "payload" portion of the CAN communication frame received by the vehicle ECU, extracts parameters, performs necessary processing such as unit conversion and variable casting, and then transfers them to App 2. The CAN analysis and configuration unit 3 also performs an inverse transformation to configure the information generated by App 2 to match the definition of the CAN communication frame.
[0015] The vCID processing module 4 analyzes the vCID, which is the logical frame ID on the virtual network frame passed through by the vNet processing module 5, and filters it by referring to a predefined vCID filtering profile 9 to determine whether or not to pass it on to the CAN analysis / configuration unit 3. It also adds the appropriate vCID to the CAN communication frame generated by the CAN analysis / configuration unit 3 and forwards it to the vNet processing module 5. Note that virtual network and logical network are synonymous. The vCID processing module 4 corresponds to the logical frame ID processing unit.
[0016] The vNet processing module 5 analyzes the vNetID, which is the logical network ID on the virtual network frame passed by the CAN controller / transceiver 7, and performs filtering by referring to a predefined vNetID filtering profile 10 to determine whether or not to pass it on to the vCID processing module 4. The vNet processing module 5 also adds the appropriate vNetID to the CAN communication frame generated by the vCID processing module 4 and forwards it to the CAN controller / transceiver 7. If there are multiple physical ports for CAN communication, the vNet processing module 5 also associates the vNetID with a physical port and sends and receives data on the appropriate physical port. The vNet processing module 5 corresponds to the logical network ID processing unit. The communication frame in which the logical network ID is stored is a logical communication frame.
[0017] Furthermore, the vCID processing module 4 and the vNet processing module 5 may be implemented in software or in hardware as accelerators. Also, vCIDs may overlap if they have different vNetIDs. In other words, an independent vCID space can be constructed for each vNetID.
[0018] The security module 6 monitors communication frames flowing through the vehicle ECU or CAN communication bus 8, and if it detects an anomaly, it uses the vNetID filtering profile 10 and the vNet processing module 5 to block the virtual network. In other words, it blocks the communication frame containing the vNetID that detected the anomaly from passing between the CAN communication bus 8 and the application 2, and also causes the communication frame to be discarded. The security module 6 corresponds to the anomaly response processing unit.
[0019] Security module 6 identifies the logical network ID of the logical network to be blocked by referring to information that has been pre-associated with the type and / or location of the anomaly. Security module 6 also identifies the logical frame ID of the logical communication frame to be blocked by referring to information that has been pre-associated with the type and / or location of the anomaly.
[0020] Furthermore, the security module 6 broadcasts a security frame containing the vNetID to the CAN communication bus 8, causing other ECUs that are configuring vNet with the same ID to similarly block the network. The security module 6 may be installed in each ECU, or it may be located on an independent, dedicated ECU.
[0021] The CAN controller / transceiver 7, which is a transceiver, performs bit stuffing, communication arbitration, error handling and CRC (Cyclic Redundancy Check), generates bus transmission voltage and ensures operating current, and filters IDs on the standard frame in CAN communication. When performing this filtering, it refers to the CAN communication filtering profile 15. The CAN communication filtering profile 15 corresponds to the profile for non-logical networks.
[0022] The CAN controller / transceiver 7 forwards the vNet instruction CANID and security frame (described later) to the vNet processing module 5, and processes all other frames as normal CAN communication frames. Since CAN communication uses a multi-master system, other vehicle ECUs are also connected to the CAN communication bus 8, but their diagrams are omitted.
[0023] Figure 2 shows an example of a configuration in which the vNetID and vCID are stored in the data field of the CAN communication frame to realize a virtual network. <ID> In normal CAN communication, the CANID for receiving settings is stored for the CAN controller / transceiver of all ECUs connected to the CAN network. In this embodiment, a specific value, for example 0x6FF, is defined as the vNet instruction CANID and is stored there. The specific value 0x6FF corresponds to a logical identifier.
[0024] <vNetID> vNetID (virtual network ID) is an ID used to identify a virtual network. If you allocate, for example, 4 bits for the size of the vNetID, you can configure 16 different networks.
[0025] <vCID> vCID (virtual CAN ID) is a CAN ID defined for each vNetID. vCID can be defined individually for each vNet, or it can be defined commonly for all vNets. If the size of the vCID is set to match the CAN, it will be 11 bits, and if it is set to match the CAN-FD (Flexible Data rate), it will be 29 bits.
[0026] <Payload> The payload is information transmitted and received between ECUs and is defined by the OEM or third party. The same approach can be used to define the frame when basing it on the CAN-FD standard.
[0027] Figure 3 shows the case where the vNetID and vCID are stored in the 11-bit ID field at the beginning of the CAN communication frame. For example, the first 4 bits may be assigned to the vNetID and the following 7 bits to the vCID. However, since there are standard specifications such as diagnostic protocols (ISO15765-4, etc.) and IDs defined independently by each automobile company, settings should be configured to avoid conflicts and disputes with these. The bit length ratio between vNetID and vCID should be adjusted according to the number of virtual networks to be secured and the size of the CANID space. In the configuration shown in Figure 2, a large number of CIDs can be secured. On the other hand, in the configuration shown in Figure 3, a larger payload length can be secured.
[0028] Next, the operation of this embodiment will be described. Figure 4 shows the processing procedure when the vehicle ECU 1 transmits a communication frame on a virtual network. First, the CAN analysis and configuration unit 3 configures the information generated by the application 2 according to the definition of a CAN communication frame and passes it to the vCID processing module 4 (S1). The vCID processing module 4 adds a vCID to the CAN communication frame and passes it to the vNet processing module 5 (S2).
[0029] The vNet processing module 5 adds the vNetID to the CAN communication frame and passes it to the CAN controller / transceiver 7 (S3). The CAN controller / transceiver 7 adds ID=0x6FF to the CAN communication frame and transmits it to the CAN communication bus 8 (S4).
[0030] Figure 5 shows the processing procedure when the vehicle ECU 1 receives a communication frame on the virtual network. When the CAN controller / transceiver 7 receives a CAN communication frame from the CAN communication bus 8 (S11), it determines whether the initial ID is 0x6FF, which indicates the vNet instruction CANID (S12). If the ID is 0x6FF (Yes), it forwards the CAN communication frame to the vNet processing module 5 (S13). On the other hand, if the ID is not 0x6FF (No), it moves to the processing shown in Figure 6, and the CAN communication frame is processed as a normal CAN communication frame by referring to the CAN communication filtering profile 15 (S20). In other words, it is forwarded to the CAN analysis / configuration unit 3.
[0031] In step S20, as shown in Figure 6, the CAN controller / transceiver 7 analyzes the CAN ID (S21) and determines whether to receive it or not (S22). If it is received (Yes), it forwards the CAN communication frame to the CAN analysis / configuration unit 3 (S23); if it determines not to receive it (No), it discards the CAN communication frame (S25). The CAN analysis / configuration unit 3 analyzes and processes the payload of the CAN communication frame and forwards it to the application 2 (S24). After steps S24 and S25 are executed, the process returns to the one shown in Figure 5.
[0032] Refer to Figure 5 again. The vNet processing module 5 analyzes the vNetID stored in the CAN communication frame (S13) and determines whether to receive it or not (S14). If it determines to receive it (Yes), it forwards the CAN communication frame to the vCID processing module 4 (S15). On the other hand, if it determines not to receive it (No), it discards the CAN communication frame (S21).
[0033] The vCID processing module 4 analyzes the vCID stored in the CAN communication frame (S16) and determines whether or not to receive it (S17). If it determines to receive it (Yes), it forwards the CAN communication frame to the CAN analysis / configuration unit 3 (S18); if it determines not to receive it (No), it proceeds to step S21.
[0034] Figure 7 shows the state of the CAN communication frame processed between the CAN analysis / configuration unit 3 and the CAN controller / transceiver 7. In the case of transmission, the vCID is added to the payload transferred from application 2 to the vCID processing module 4, the vNetID is added when it is transferred to the vNet processing module 5, and the ID is added when it is transferred to the CAN controller / transceiver 7. In the case of reception, the process is the reverse of the above.
[0035] As described above, according to this embodiment, when the CAN controller / transceiver 7 in the vehicle ECU 1 receives a CAN communication frame from the CAN communication bus 8, the vNet processing module 5 identifies the vNetID and performs filtering and routing of the CAN communication frame according to the identified vNetID.
[0036] With this configuration, even for CAN-compliant communications where the use of a virtual network is not specified in the specifications, it becomes possible to use a virtual network by processing the CAN communication frame according to the vNetID stored in the CAN communication frame.
[0037] Furthermore, the vCID processing module 4 identifies the vCID and filters the logical communication frame according to the identified vCID. In addition, when the CAN controller / transceiver 7 receives a CAN communication frame, it determines whether the ID is a specific value 0x6FF, and if it is 0x6FF, it forwards the CAN communication frame to the vNet processing module 5. This makes it possible for the vNet processing module 5 to process CAN communication frames containing ID=0x6FF in the logical network.
[0038] (Second Embodiment) Hereinafter, the same reference numerals are used for parts identical to those in the first embodiment, and their descriptions are omitted. The different parts will be described. As shown in Figure 8, in the vehicle ECU 11 of the second embodiment, two applications 2A and 2B are in operation, and CAN analysis and configuration units 3A and 3B, and vCID processing modules 4A and 4B are provided corresponding to each application 2A and 2B. The vNet processing module 12 is common and performs filtering and routing based on the vNetID filtering profile 13.
[0039] For example, the vNetID for application 2A is set to 0x1, and the vNetID for application 2B is set to 0x2. The vNet processing module 12 may switch communication frames to the virtual communication buses 8vA and 8vB to which applications 2A and 2B belong, and transmit them separately for applications 2A and 2B. Alternatively, for a specific combination of vNetID and vCID, switching or routing may occur across different vNets.
[0040] For example, if a security incident occurs with application 2A, security module 6 will instruct vNet processing module 12 to close vNetID=0x1 and keep only vNetID=0x2 running. This protects application 2B and vNetID=0x2. Here, the area enclosed by the dashed line on the application 2A side is designated as communication module 14A, and the area enclosed by the dashed line on the application 2B side is designated as communication module 14B. These communication modules 14A and 14B may be physical machines implemented in hardware, or virtual machines implemented in software. Physical machines are sometimes referred to as native environments or bare-metal environments. Virtual machines are sometimes referred to as virtual environments such as host-based, hypervisor-based, or container-based environments.
[0041] As described above, according to the second embodiment, by managing on a network-by-network basis, unlike simply switching the destination application using CID, it becomes unnecessary to have a large map showing the correspondence between applications and CIDs.
[0042] (Third Embodiment) As shown in Figure 9, the in-vehicle communication system 21 of the third embodiment is assumed to be applied to a zone architecture or zone network in which, for example, a front portion, a rear portion and the like in a vehicle are defined as respective zones, and communication is performed between ECUs arranged for each zone. However, ECUs as communication nodes are not illustrated, and zone switchers 22(1) to 22(3) that switch and route the flow of communication frames are shown.
[0043] The zone switcher 22 includes CAN analyzers / constructors 23(1) to 23(3), vCID processing modules 24(1) to 24(3), and a vNet processing module 25. The vCID processing modules 24(1) to 24(3) perform filtering with reference to vCID filtering profiles 26(1) to 26(3), respectively. The vNet processing module 25 performs filtering with reference to a vNet filtering profile 27.
[0044] The CAN analyzer / constructor 23(1) and the vCID processing module 24(1) route communication frames in the virtual network with vNetID=0x1 indicated by the broken line in the figure. The CAN analyzer / constructor 23(2) and the vCID processing module 24(2) route communication frames in the virtual network with vNetID=0x2 indicated by the one-dot chain line in the figure. The CAN analyzer / constructor 23(3) and the vCID processing module 24(3) route communication frames in the virtual network with vNetID=0x3 indicated by the two-dot chain line in the figure. vNetID=0x1 to 0x3 correspond to the zones to which they respectively belong.
[0045] The zone switcher 22 performs routing between the CAN communication bus 8 through which normal CAN communication frames flow and the virtual communication buses 8v(1) to 8v(3) through which communication frames of a virtual network flow. Further, the virtual communication buses 28v(1) to 28v(3) are arranged in zones 0x1 to 0x3 that are physically separated from the CAN communication bus 8 and the like. Similarly, virtual communication buses respectively routed from the CAN communication bus 8 and the like via zone switchers 22(2) and 23(3) are also arranged in physically separated zones. Therefore, the CAN communication buses 8 and 8v(1) to 8v(3) serve as a backbone bus that relays between physically separated zones.
[0046] Then, the zone switcher 22(1) is arranged at the boundary between the backbone bus and the plurality of communication buses. The zone switcher 22 converts communication frames by adding or removing the vNetID and vCID adapted to each zone in accordance with input and output between the zones and the backbone bus.
[0047] For example, as shown in FIG. 10, in order to transmit a CAN communication frame with ID=0x123 to the virtual network with vNetID=0x01, the vNetID=0x01 is added, and conversion is performed by setting vCID=0x123. Conversely, when transmitting a communication frame received from the virtual network to the CAN communication side, reverse conversion is performed so that vNetID=0x01 is deleted, and vCID=0x123 is set as ID=0x123. These processes correspond to processing operations corresponding to the routing destination.
[0048] According to the third embodiment configured as described above, a zone network can be logically constructed without being restricted by the physical arrangement of ECUs.
[0049] (Fourth Embodiment) As shown in Figure 11, the communication system 31 of the fourth embodiment uses a CAN-Ethernet converter 32. The CAN-Ethernet converter 32 converts communication frames between the virtual network vNet on the CAN communication side and the virtual network vLAN on the Ethernet communication side. This creates a virtual network that mixes Ethernet communication and CAN communication.
[0050] The CAN-Ethernet converter 32 comprises an Ethernet communication unit 33, a CAN communication unit 34, and a CANvNet-EthervLAN conversion module 35. Hereinafter, it will simply be referred to as the conversion module 35. The Ethernet communication unit 33 comprises two sets of Ethernet physical ports 36, PHY / MAC interfaces 37, and Ethernet communication control units 38, and each set is indicated by the symbols (1) and (2), respectively. The Ethernet physical port 36(1) is a port with vLANID = 0x02 and is connected to the Ethernet virtual communication bus 39v(1). The Ethernet physical port 36(2) is a port with vLANID = 0x01 and is connected to the same virtual communication bus 39v(2).
[0051] On the other hand, the CAN communication unit 34 is equipped with two sets of CAN physical ports 40, CAN controllers / transceivers 41, vCID processing modules 43, and CAN analysis / configuration units 44. A common vNet processing module 42 handles communication between the CAN controllers / transceivers 41(1) and 41(2) and the vCID processing modules 43(1) and 43(2).
[0052] CAN physical port 40(1) is the port with vNetID=0x1 and is connected to the CAN virtual communication bus 8v(1). CAN physical port 40(2) is the port with vNetID=0x2 and is connected to the same virtual communication bus 8v(2). Figure 11 shows the correspondence between each of the above-mentioned physical ports and their respective virtual network IDs, vNetID and vLANID. Virtual communication bus 8v corresponds to the first communication bus, and virtual communication bus 39v corresponds to the second communication bus.
[0053] The conversion module 35 performs protocol conversion between CAN communication and Ethernet communication, based on the vNetID-vLANID compatible profile 45 which stores the correspondence table shown in Figure 12, and converts the communication frame between the CAN-side physical port 40 and the Ethernet-side physical port 36.
[0054] Furthermore, the above configuration is not limited to the configuration shown in Figure 11, where a vNet communication bus 8v is separated for each physical port 40, and a vLANID is separated for each physical port 36. Alternatively, there may be only one physical port 40, or one physical port 36 with tagged vLAN, or both. As described above, according to the fourth embodiment, a logical network can be constructed in a form that mixes different communication protocols of CAN and Ethernet.
[0055] (Fifth Embodiment) As shown in Figure 13, the in-vehicle communication system 51 of the fifth embodiment is configured in which the vehicle ECUs 52(1) to 52(3) are connected to the CAN communication bus 8, in the configuration of the second embodiment. These vehicle ECUs 52 do not support a virtual communication network using vNetID and vCID, and are configured to only perform communication using normal CANID. Therefore, when a vehicle ECU 52 receives a communication frame to which vNetID and vCID have been added via the CAN communication bus 8, it discards that communication frame.
[0056] This disclosure includes, in addition to the claims, the following disclosures: [1] An in-vehicle communication system comprising: a receiver (7, 41) that receives a communication frame in a format based on a predetermined in-vehicle communication protocol from a communication bus, wherein a logical network ID, which is an identifier of a logical network implemented on the in-vehicle communication protocol, is stored in part of the field of the communication frame; and a logical network ID processing unit (5, 12, 25, 42) that, upon receiving the communication frame, identifies the logical network ID and performs either filtering or routing of the communication frame or both according to the identified logical network ID. [2] The in-vehicle communication system according to [1], wherein the communication based on the in-vehicle communication protocol is a multi-master communication. [3] The in-vehicle communication system according to [1] or [2], wherein the communication frame in which the logical network ID is stored is defined as a logical communication frame, the communication frame has a logical frame ID stored in a part of its field, which is an identifier defined for a logical communication frame in each logical network, and the receiver, upon receiving the communication frame, identifies the logical frame ID and filters the logical communication frame according to the identified logical frame ID. [4] The in-vehicle communication system according to any one of [1] to [3], wherein the communication frame has a logical identifier stored in a part of its field, which indicates that the communication frame is a communication frame associated with the logical network, and the receiver, upon receiving the communication frame and recognizing the logical identifier, forwards the communication frame to the logical network ID processing unit. [5] The in-vehicle communication system according to [4], wherein the receiver, upon receiving a communication frame in which the logical identifier is not stored, filters the communication frame using a non-logical network profile (15) and processes it according to a format based on the in-vehicle communication protocol.[6] An in-vehicle communication system according to any one of [1] to [5], comprising a transmitter that transmits a communication frame in a format based on the in-vehicle communication protocol to a communication bus (8), wherein the logical network ID processing unit stores the logical network ID in a part of the field of the communication frame transmitted by the transmitter. [7] An in-vehicle communication system according to [3], wherein the logical frame ID processing unit stores the logical frame ID in a part of the field of the communication frame transmitted by the transmitter. [8] An in-vehicle communication system according to any one of claims [1] to [7], comprising an abnormality response processing unit (6) that, when an abnormality is detected, identifies the logical network ID of a logical network to be blocked, and causes the logical network ID processing unit to discard the communication frame in which the identified logical network ID is stored. [9] An in-vehicle communication system according to [3], comprising an abnormality response processing unit (6) that, when an abnormality is detected, identifies the logical frame ID of a logical communication frame to be blocked, and causes the logical frame ID processing unit to discard the communication frame in which the identified logical frame ID is stored.
[10] An in-vehicle communication system according to [3] or [7], comprising a plurality of logical frame ID processing units (4A, 4B, 24(1) to 24(3), 43(1), 43(2)), wherein the logical network ID processing unit (12, 25, 42) determines which of the plurality of logical frame ID processing units to route to according to the identified logical network ID and performs routing.
[11] An in-vehicle communication system according to
[10] , wherein the plurality of logical frame ID processing units are mounted in one communication unit (11, 22, 32).
[12] An in-vehicle communication system according to any one of [3], [7],
[10] and
[11] , comprising a plurality of communication modules (14A, 14B), wherein the logical network ID processing unit (12) determines which of the plurality of communication modules to route to according to the identified logical network ID and performs routing.
[13] The in-vehicle communication system according to
[12] , wherein the plurality of communication modules are mounted on a single communication unit (11).
[14] An in-vehicle communication system according to any one of [1] to
[13] , comprising a plurality of communication buses (8v(1) to 8v(3)) that perform communication based on the in-vehicle communication protocol, and a network switch (22) that determines which of the plurality of communication buses to route to and performs routing, wherein the logical network ID processing unit (25) is provided on the network switch and determines which of the plurality of communication buses to route to according to the logical network ID and performs routing.
[15] An in-vehicle communication system according to
[14] , wherein the network switch performs processing corresponding to the routing destination on the communication frame that is the target of the routing.
[16] An in-vehicle communication system according to
[15] , wherein when the routing destination is a predetermined communication bus among the plurality of communication buses, the processing includes deleting the logical network ID.
[17] The in-vehicle communication system according to any one of
[14] to
[16] , wherein the vehicle equipped with the in-vehicle communication system employs a zone architecture in which multiple communication modules are separated to belong to one of multiple zones that divide the inside of the vehicle, and comprises a backbone bus (8, 8v(1) to 8v(3)) that relays the transfer of the communication frames between the multiple zones, and a multiple communication bus (28v(1) to 28v(3)) provided separately from the backbone bus, wherein the network switch is located at the boundary between the backbone bus and the multiple communication buses, and determines which of the multiple communication buses to route the communication frames received from the backbone bus to according to the logical network ID and routes them.
[18] The in-vehicle communication system according to any one of [1] to
[17] , wherein the in-vehicle communication protocol is designated as the first protocol, the communication bus that performs communication based on the first protocol is designated as the first communication bus (8v), the in-vehicle communication protocol different from the first protocol is designated as the second protocol, and the communication bus that performs communication based on the second protocol is designated as the second communication bus (39v), and the system includes a converter (32) that performs protocol conversion and routing between the first protocol and the second protocol, and the logical network ID processing unit (42) is provided in the converter.
[19] The in-vehicle communication system according to
[18] , wherein the converter performs protocol conversion and routing using a profile (45) that shows the correspondence between a logical network ID stored in a communication frame based on the first protocol and a logical network ID stored in a communication frame based on the second protocol.
[20] The in-vehicle communication system according to
[18] or
[19] , wherein the first protocol is CAN and the second protocol is Ethernet®.
[21] The in-vehicle communication system according to [4] or [5], further comprising a receiver (52) that discards a communication frame when it receives a communication frame in which the logical identifier is stored.
[0057] (Other Embodiments) The CAN controller / transceiver 7 may be replaced with a CAN controller / receiver, and only the receiving side processing for the virtual network may be performed. The first protocol and the second protocol are not limited to CAN and Ethernet, respectively. The first protocol may be any in-vehicle communication protocol that does not specify the use of a logical network in its specifications. It may be applied not only to multi-master communication but also to single-master communication such as LIN. In the fourth embodiment, there may be three or more physical ports.
[0058] This disclosure is described in accordance with the embodiments, but it is understood that this disclosure is not limited to such embodiments or structures. This disclosure also includes various modifications and variations within the equivalence. In addition, various combinations and forms, as well as other combinations and forms that include only one, more, or fewer of those elements, fall within the scope and concept of this disclosure.
[0059] The means and / or functions provided by each device may be provided by software recorded in a physical memory device and the computer that runs it, by software only, by hardware only, or by a combination thereof. For example, if a control device is provided by an electronic circuit which is hardware, it may be provided by a digital circuit including a large number of logic circuits, or by an analog circuit.
[0060] The control unit and its method described herein may be implemented by a dedicated computer provided by configuring a processor and memory programmed to perform one or more functions embodied by a computer program. Alternatively, the control unit and its method described herein may be implemented by a dedicated computer provided by configuring a processor by one or more dedicated hardware logic circuits. Alternatively, the control unit and its method described herein may be implemented by one or more dedicated computers configured by a combination of a processor and memory programmed to perform one or more functions and a processor configured by one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by the computer on a computer-readable non-transitional tangible recording medium.
Claims
The system includes receivers (7, 41) that receive communication frames in a format based on a predetermined in-vehicle communication protocol from a communication bus (8), The aforementioned communication frame contains a logical network ID, which is an identifier for the logical network implemented on the in-vehicle communication protocol, in a portion of its fields. An in-vehicle communication system comprising a logical network ID processing unit (5, 12, 25, 42) that, upon receiving the communication frame from the receiver, identifies the logical network ID and performs either filtering or routing of the communication frame, or both, according to the identified logical network ID. The in-vehicle communication system according to claim 1, wherein the communication based on the aforementioned in-vehicle communication protocol is a multi-master communication system. If we define a communication frame containing the aforementioned logical network ID as a logical communication frame, The aforementioned communication frame contains a logical frame ID, which is an identifier defined for each logical communication frame in the logical network, in a portion of its fields. The in-vehicle communication system according to claim 1, further comprising a logical frame ID processing unit (4, 24, 43) that, upon receiving the communication frame of the receiver, identifies the logical frame ID and filters the logical communication frame according to the identified logical frame ID. The aforementioned communication frame contains a logical identifier in a part of its field, which indicates that the communication frame is associated with the logical network. The in-vehicle communication system according to claim 3, wherein the receiver, upon receiving the communication frame and recognizing the logical identifier, forwards the communication frame to the logical network ID processing unit. The in-vehicle communication system according to claim 4, wherein when the receiver receives a communication frame in which the logical identifier is not stored, it filters the communication frame using a non-logical network profile (15) and processes it in accordance with a format based on an in-vehicle communication protocol. The system includes a transmitter that transmits a communication frame in a format based on the aforementioned in-vehicle communication protocol to a communication bus (8), The in-vehicle communication system according to claim 3, wherein the logical network ID processing unit stores the logical network ID in a part of the field of the communication frame transmitted by the transmitter. The in-vehicle communication system according to claim 6, wherein the logical frame ID processing unit stores the logical frame ID in a part of the field of the communication frame transmitted by the transmitter. The in-vehicle communication system according to claim 1, further comprising an abnormality response processing unit (6) that, when an abnormality is detected, identifies the logical network ID of the logical network to be blocked and causes the logical network ID processing unit to discard the communication frame in which the identified logical network ID is stored. The in-vehicle communication system according to claim 3, further comprising an abnormality response processing unit (6) that, when an abnormality is detected, identifies the logical frame ID of a logical communication frame to be blocked, and causes the logical frame ID processing unit to discard the communication frame in which the identified logical frame ID is stored. The logical frame ID processing unit comprises a plurality of units (4A, 4B, 24(1) to 24(3), 43(1), 43(2)), The in-vehicle communication system according to claim 3, wherein the logical network ID processing unit (12, 25, 42) determines which of the plurality of logical frame ID processing units to route to according to the identified logical network ID and then routes the data. The in-vehicle communication system according to claim 10, wherein the plurality of logical frame ID processing units are mounted in one communication unit (11, 22, 32). Equipped with multiple communication modules (14A, 14B), The in-vehicle communication system according to claim 3, wherein the logical network ID processing unit (12) determines which of the plurality of communication modules to route to according to the identified logical network ID and then routes the traffic. The in-vehicle communication system according to claim 12, wherein the plurality of communication modules are mounted on a single communication unit (11). The vehicle is equipped with multiple communication buses (8v(1) to 8v(3)) that perform communication based on the aforementioned in-vehicle communication protocol, The system includes a network switch (22) that determines and routes to one of several communication buses, The in-vehicle communication system according to claim 1, wherein the logical network ID processing unit (25) is provided in the network switch and determines which of the plurality of communication buses to route to according to the logical network ID and performs routing. The in-vehicle communication system according to claim 14, wherein the network switch performs processing corresponding to the routing destination on the communication frame that is the target of the routing. When the destination of the routing is a predetermined communication bus among the plurality of communication buses, The in-vehicle communication system according to claim 15, wherein the processing step involves deleting the logical network ID. When a vehicle equipped with an in-vehicle communication system employs a zone architecture in which multiple communication modules are separated to belong to one of several zones that divide the vehicle, A backbone bus (8, 8v(1) to 8v(3)) relays the transfer of the communication frames between the aforementioned multiple zones, This backbone bus is equipped with multiple communication buses (28v(1) to 28v(3)) that are provided separately from it. The network switch is located at the boundary between the backbone bus and the plurality of communication buses. An in-vehicle communication system according to any one of claims 14 to 16, which determines which of the plurality of communication buses to route a communication frame received from the backbone bus to, according to the logical network ID, and then routes it. The aforementioned in-vehicle communication protocol is designated as the first protocol, and the communication bus that performs communication based on this first protocol is designated as the first communication bus (8V). If we define a second in-vehicle communication protocol as different from the first protocol, and the communication bus that performs communication based on this second protocol as the second communication bus (39v), then, The system includes a converter (32) that performs protocol conversion between the first protocol and the second protocol, and also performs routing. The in-vehicle communication system according to claim 1, wherein the logical network ID processing unit (42) is provided in the converter. The in-vehicle communication system according to claim 18, wherein the converter performs the protocol conversion and routing using a profile (45) that shows the correspondence between a logical network ID stored in a communication frame based on the first protocol and a logical network ID stored in a communication frame based on the second protocol. The in-vehicle communication system according to claim 18 or 19, wherein the first protocol is CAN and the second protocol is Ethernet®. The in-vehicle communication system according to claim 4, further comprising a receiver (52) that discards a communication frame upon receiving a communication frame in which the aforementioned logical identifier is stored. The system receives a communication frame in a format based on a predetermined in-vehicle communication protocol from the communication bus. The aforementioned communication frame contains a logical network ID, which is an identifier for the logical network implemented on the in-vehicle communication protocol, in a portion of its fields. An in-vehicle communication method that, upon receiving the aforementioned communication frame, identifies the logical network ID and performs either filtering or routing of the communication frame, or both, according to the identified logical network ID. This is executed by a computer that constitutes a receiver that receives communication frames in a format based on a predetermined in-vehicle communication protocol from the communication bus. The aforementioned communication frame contains a logical network ID, which is an identifier for the logical network implemented on the in-vehicle communication protocol, in a portion of its fields. A computer program that, upon receiving the aforementioned communication frame, identifies the logical network ID and performs either filtering or routing of the communication frame, or both, according to the identified logical network ID.
