In-vehicle network system, activation message transfer method, terminal node, and relay node

Abstract

A technology is provided for reducing the amount of communication of messages related to control of the activation state of a partial network. [Solution] A calculation unit 234 of an end ECU 23 transmits an NM message including PN request information indicating the PNC to which an end node 22 belongs, loaded on an IP packet with a TTL value set to 1. In S210, a calculation unit 224 of a zone ECU 22 decrements the TTL value of the received IP packet. If the calculation unit 224 determines in S220 to S230 that the TTL value after decrement is 0 and that the sender of the NM message is a subordinate end ECU 23, it rewrites the TTL value in S240 and transfers the IP packet carrying the NM message in S250.

Description

[Technical Field]

[0001] The present disclosure relates to an in-vehicle network system. [Background technology]

[0002] Patent Document 1 listed below discloses a partial network technology that selectively controls the wake-up / sleep state of each ECU connected to an in-vehicle network system. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-011228 Summary of the Invention [Problem to be solved by the invention]

[0004] AUTOSAR R22-11: Specification of UDP Network Management, a standard for in-vehicle Ethernet networks, specifies that end nodes periodically transmit NM messages that control their startup status, and that relay nodes forward the NM messages by broadcast. Ethernet is a registered trademark.

[0005] When NM messages are transmitted by broadcast, if a loop is formed in the network, the NM messages circulate, increasing the amount of NM message communication.

[0006] One aspect of the present disclosure provides a technique for reducing the amount of communication of messages related to control of the activation state of a partial network. [Means for solving the problem]

[0007] One aspect of the present disclosure is an in-vehicle network system comprising a plurality of relay nodes (22) and a plurality of terminal nodes (23). Each of the relay nodes has a plurality of communication ports. Each of the terminal nodes is connected to one of the plurality of relay nodes. Each of the plurality of communication ports of a relay node is connected to a subordinate node, which is a terminal node subordinate to the relay node, or to another relay node different from the relay node. The terminal node comprises a state management unit (234: S110 to S170). The state management unit is configured to transmit a startup message including startup request information indicating an activation cluster to which the terminal node belongs and permitted forwarding information in which the number of permitted forwardings is set to 1. The relay node comprises a memory unit (224) and a rewrite forwarding unit (223: S210 to S260). The memory unit stores a startup table. The activation table lists, for each of a plurality of terminal nodes, information linking node identification information that identifies the terminal node with required forwarding information that indicates the number of forwardings required to reach the terminal node of interest, which is identified by the node identification information. When the rewrite forwarder receives a startup message via a communication port, it decrements the value indicated by the permission forwarding information, and if the value of the permission forwarding information after the decrement is greater than 0, it forwards the startup message. If the value of the permission forwarding information after the decrement is 0 and the sender of the startup message is not a subordinate node, the rewrite forwarder deletes the startup message. If the value of the permission forwarding information after the decrement is 0 and the sender of the startup message is a subordinate node, the rewrite forwarder rewrites the permission forwarding information of the startup message and forwards the startup message. The permission forwarding information is rewritten using the required forwarding information linked to the target terminal node, which is the terminal node belonging to the activation cluster indicated by the activation request information, according to the activation table.

[0008] With this configuration, appropriate permission forwarding information is set in the start message at a relay node that is subordinate to the end node that is the sender of the start message. Therefore, start messages that do not reach their destination due to broadcast forwarding can be removed at an appropriate time, and the communication volume of start messages can be reduced.

[0009] One aspect of the present disclosure is a method for forwarding a startup message in an in-vehicle network system. The in-vehicle network system includes multiple relay nodes, each having multiple communication ports, and multiple end nodes, each connected to one of the multiple relay nodes. Each of the multiple communication ports of a relay node is connected to a subordinate node, which is an end node under the relay node, or a relay node different from the relay node. The startup message forwarding method includes transmitting a startup message from the end node (S120, S170) that includes startup request information indicating an activation cluster to which the end node belongs and permission forwarding information in which the number of permitted forwardings is set to 1. The startup message forwarding method also includes decrementing a value indicated by the permission forwarding information upon receiving the startup message via the communication port (S210). The startup message forwarding method also includes forwarding the startup message if the value of the permission forwarding information after the decrement is greater than 0 (S220, S250). The method of forwarding the startup message includes deleting the startup message if the value of the permission forwarding information after decrement is 0 and the sender of the startup message is not a subordinate node (S220, S230, S260). The method of forwarding the startup message includes rewriting the permission forwarding information of the startup message in accordance with the startup table and forwarding the startup message if the value of the permission forwarding information after decrement is 0 and the sender of the startup message is a subordinate node (S220, S230 to S250). The permission forwarding information is rewritten using required forwarding information associated with a target terminal node that is an terminal node belonging to the startup cluster indicated by the startup request information. The startup table lists, for each of a plurality of terminal nodes, information that associates node identification information that identifies the terminal node with required forwarding information that indicates the number of forwardings required to reach a target node that is an terminal node identified by the node identification information.

[0010] By implementing this method, it is possible to obtain the same effects as those obtained by the above-mentioned in-vehicle network system. One aspect of the present disclosure is a terminal node (23) connected to one of a plurality of relay nodes (22) and constituting an in-vehicle network system together with the plurality of relay nodes, the terminal node (23) including a startup unit (233) and a state management unit (234: S110 to S170). The startup unit is configured to transition the terminal node from a sleep state to a wake-up state when a preset startup condition is met. The state management unit is configured to transmit, while the terminal node is in the wake-up state, a startup message including startup request information indicating an activation cluster to which the terminal node belongs and permitted forwarding information in which the number of permitted forwardings is set to 1. The wake-up state is a normal operating state in which the functions of the terminal node can be executed without restriction. The sleep state is a low-power operating state in which at least some of the functions of the terminal node are restricted.

[0011] With this configuration, it can be used as a terminal node in the above-mentioned in-vehicle network system. One aspect of the present disclosure is a relay node (22) having a plurality of communication ports. Each of the plurality of communication ports of the relay node is connected to a subordinate node, which is a subordinate terminal node of the relay node, or another relay node different from the relay node, among a plurality of terminal nodes (23) configured to transmit an activation message including activation request information indicating an activation cluster to which the relay node belongs and permitted forwarding information indicating the number of permitted forwardings. The relay node, together with the terminal node and other relay nodes, constitutes an in-vehicle network system. The relay node includes a storage unit (225) and a rewrite forwarding unit (224: S210 to S260). The storage unit and the rewrite forwarding unit are configured similarly to the storage unit and the rewrite forwarding unit described in the in-vehicle network system.

[0012] With this configuration, it can be used as a relay node in the above-mentioned in-vehicle network system. [Brief explanation of the drawings]

[0013] [Figure 1]1 is a block diagram showing a configuration of an in-vehicle network system according to a first embodiment. [Figure 2] FIG. 2 is an explanatory diagram showing the configuration of an IP packet. [Figure 3] FIG. 1 is an explanatory diagram of the function of TTL. [Figure 4] FIG. 10 is an explanatory diagram showing the configuration of an NM message. [Figure 5] FIG. 2 is an explanatory diagram showing an outline of a startup process that is executed by a startup unit of a terminal ECU when an NM message is received. [Figure 6] 10 is a flowchart showing a state management process executed by a terminal ECU. [Figure 7] FIG. 10 is an explanatory diagram showing the setting of the NM table in each zone ECU. [Figure 8] 10 is a flowchart showing IP packet processing executed by a zone ECU. [Figure 9] FIG. 10 is an explanatory diagram showing the settings of the NM table updated by adding a terminal ECU and updating a program. [Figure 10] FIG. 10 is an explanatory diagram showing a plurality of NM tables that are prepared in advance and are selected for use. [Figure 11] FIG. 10 is a block diagram showing the configuration of a terminal ECU in a second embodiment. [Figure 12] FIG. 10 is an explanatory diagram showing settings of a forwarding information table. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. [1. First embodiment] [1-1.Configuration] In the in-vehicle network system 1 of the first embodiment shown in Fig. 1, a plurality of electronic control units (hereinafter referred to as ECUs) 2 mounted on a vehicle are interconnected via a plurality of transmission paths 4 that communicate using the Ethernet protocol. Ethernet is a registered trademark.

[0015] The ECU 2 has a wake-up state, which is a normal operating state in which it can execute its own functions without any restrictions, and a sleep state, which is a low-power operating state in which at least some of its functions are restricted. The operating states of the ECU 2 are individually controlled using NM messages. NM stands for Network Management. In other words, the in-vehicle network system 1 is configured as a partial network (hereinafter referred to as PN). In addition, the ECU 2 has at least the function of receiving an NM message in the sleep state and transitioning itself to the wake-up state according to the contents of the NM message.

[0016] The plurality of ECUs 2 are classified into a plurality of zone ECUs 22 and a plurality of end ECUs 23 . A zone ECU 22 is provided for each zone that divides the interior of the vehicle. The multiple zone ECUs 22 are connected to each other via transmission paths 4, forming a communication network that includes redundant paths. Each zone ECU 22 is connected to multiple end ECUs 23 present in the zone via individual transmission paths 4. A zone ECU 22 controls the subordinate end ECUs 23 that are directly connected to the zone ECU, thereby achieving coordinated control within the zone. One of the zone ECUs 22 may also function as a central ECU. The central ECU controls the other zone ECUs 22, thereby achieving coordinated control of the entire vehicle.

[0017] In this embodiment, the vehicle is divided into four zones A to D, and the zone ECUs 22 arranged in the respective zones A to D are denoted as zone ECU_A, zone ECU_B, zone ECU_C, and zone ECU_D. Zones A to D may be located in the front of the vehicle, behind the vehicle, one side of the vehicle, and the other side of the vehicle. The number of zones is not limited to four, and the vehicle may be divided into two or more zones.

[0018] As shown in FIG. 1 , zone ECU_A is connected to zone ECU_B and zone ECU_C via separate transmission paths 4. Zone ECU_B is connected to zone ECU_A and zone ECU_D via separate transmission paths 4. Zone ECU_C is connected to zone ECU_A and zone ECU_D via separate transmission paths 4. Zone ECU_D is connected to zone ECU_B and zone ECU_C via separate transmission paths 4. In other words, multiple zone ECUs 22 are connected in a loop. However, by setting some of the communication ports connected to the transmission paths 4 as blocking ports, communication frames are prevented from circulating. In FIG. 1 , the communication port connected to the transmission path 4 between zone ECU_C and zone ECU_D is set as a blocking port. Communication is normally prohibited through the blocking port, and the prohibition is lifted, for example, when a failure occurs in the ECU 2 or the transmission path 4. In other words, the blocking port may be used to ensure redundancy of the communication path. The plurality of zone ECUs 22 may be referred to as forming a ring topology.

[0019] Three end ECUs 23 are connected to the zone ECU_A in a star configuration via individual transmission paths 4. Hereinafter, the end ECUs 23 connected to the zone ECU_A will also be referred to as end ECU_A, end ECU_B, and end ECU_C. The zone ECU_A and the end ECUs_A to C form a switched network (hereinafter, switched NW). Note that the number of end ECUs 23 connected to each zone ECU 22 as subordinates is not limited to the above example, and is arbitrary.

[0020] Three end ECUs 23 are connected to zone ECU_B in a star configuration, each via a separate transmission path 4. Hereinafter, the end ECUs 23 connected to zone ECU_A will also be referred to as end ECU_D, end ECU_E, and end ECU_F. In other words, zone ECU_B and end ECUs_D to F form a switched NW.

[0021] The zone ECU_C is connected to an end ECU 23 via a transmission line 4. Hereinafter, the end ECU 23 connected to the zone ECU_C will also be referred to as an end ECU_X. A wireless device 3 that communicates with a server on the wide area wireless network is connected to the zone ECU_D. One or more end ECUs 23 may also be connected to the zone ECU_C, but for simplicity, illustration and description thereof are omitted here.

[0022] [1-2. IP packets / NM messages] An overview of IP packets and NM messages will be explained using Figures 2 to 5. NM messages comply with the AUTOSAR R22-11: Specification of UDP Network Management. The compliant specification is not limited to R22-11, but may also be its successor, R23-11, for example.

[0023] NM messages are sent and received using Ethernet frames carrying IP packets. As shown in Figure 2, an Ethernet frame is composed of a physical header, an Ethernet header, a payload, and a trailer. The physical header is a preamble. The Ethernet header includes a destination address, a source address, etc. The payload is data and carries an IP frame. The trailer is a frame check sequence.

[0024] An IP packet includes an IP header and IP data. The IP header includes fields such as a version, header length, service type, packet length, identifier, flags, fragment offset, time to live, protocol, header checksum, source IP address, destination IP address, options, and padding.

[0025] The "time to live" field in the IP header is referred to as TTL below. TTL stands for Time to Live. As shown in Figure 3, TTL is set by the end ECU 23, which is the source of the IP packet, and is decremented by one each time the packet is routed within the network. An IP frame with TTL=0 is discarded without being routed. In this case, an ICMP message called "Time Exceeded" is sent to the source of the IP packet. In other words, by using the TTL function, IP packets are automatically deleted after a certain period of time, preventing IP packets from circulating even if a routing loop is formed within the network.

[0026] The "protocol" field in the IP header specifies the protocol to be applied to data sent and received as IP data. In this example, the protocol field is set to use UDP, and the NM message is sent and received as IP data.

[0027] The IP packet is a known technology, and the description of fields other than "TTL" and "Protocol" will be omitted. As shown in Fig. 4, the NM message includes an NID, a CBV, user data, and a PNI. The NID and the CBV each consist of one byte. The user data has a variable length, and Fig. 2 shows a case where it is four bytes. The PNI has a variable length, and Fig. 2 shows a case where it is two bytes. The positions of the NID and the CBV in the NM message may be reversed.

[0028] NID is an abbreviation for Node Identifier, and is information for identifying the node (that is, the end ECU 23) that is the source of the NM message. The user data is an area in which the user can set any data.

[0029] PNI stands for Partial Network Information. PNI is set in the user data area and is represented by multiple bits. Each bit constituting PNI is called a PNC bit. PNC stands for Partial Network Cluster. PNC indicates a group of end ECUs 23 that need to be started simultaneously in a node (i.e., ECU2). A different PNC is assigned to each PNC bit. A PNC bit set to a value of 1 indicates that a factor has occurred that will wake up the PN cluster associated with the PNC bit. A PNC bit set to a value of 0 indicates that a factor has not occurred that will wake up the PN cluster associated with the PNC bit. Hereinafter, the PNI carried in the NM message to wake up ECU2 is called PN request information.

[0030] CBV is an abbreviation for Control Bit Vector, and is information indicating the content of instructions given by the NM message. The CBV includes the PNI bit, PNL bit, AW bit, NMCSR bit, PNSR bit, and RMR bit. AW stands for Active Weakness. NMCSR stands for NM Coordinator Sleep Ready. PNSR stands for PN Shutdown Request. RMR stands for Repeat Message Request.

[0031] The PNI bit is information indicating whether or not partial network management (hereinafter referred to as partial NM) is supported. In this embodiment, the PNI bit is fixed to a value indicating support for NM. If support for NM is supported, PN request information is included in the user data of the NM message.

[0032] The PNL bit is information indicating whether the NM message is for PNC learning. PNL stands for Partial Network Learning. The NM message is a standardized, well-known technology, and the AW bit, NMCSR bit, PNSR bit, and RMR bit are not closely related to the main part of this disclosure, so explanations thereof will be omitted.

[0033] [1-3. Terminal ECU] As shown in FIG. 1, the terminal ECU 23 includes a transmitter 231, a receiver 232, a starter 233, and a calculator 234.

[0034] The transmitting unit 231 has a function of transmitting a message generated by the local terminal ECU 23 . The receiving unit 232 has a function of receiving messages from other ECUs 2 . The activation unit 233 has a function of transitioning the own terminal ECU 23 to a wake-up state based on the NM message received by the receiving unit 232 when the own terminal ECU 23 is in a sleep state.

[0035] The calculation unit 234 has at least a function of monitoring the transmission and reception of NM messages while the own terminal ECU 23 is in a wake-up state, and transitioning the own terminal ECU 23 to a sleep state as necessary.

[0036] The end ECU 23 holds a PNI (hereinafter referred to as PN filter information) in which all PNC bits corresponding to the PN cluster to which the end ECU 23 belongs are set to 1. When the activation unit 233 receives an NM message (hereinafter referred to as a wake-up request) including PN request information, it compares the PN request information indicated in the wake-up request with the PN filter information held by the local terminal ECU 23, bit by bit, as shown in FIG. 5. If the comparison results in at least one matching bit, the activation unit 233 transitions the local terminal ECU 23 from a sleep state to a wake-up state. The comparison between the PN request information and the PN filter information may be performed by calculating the logical product of the two. In this case, if the result of the logical product is non-zero, it is determined that the PN request information indicates the PNC to which the local terminal ECU 23 belongs, or in other words, that a factor for waking up the local terminal ECU 23 has occurred.

[0037] The activation unit 233 may be configured by hardware. When an activation condition is met, the activation unit 233 transitions its own terminal ECU 23 from a sleep state to a wake-up state. The activation condition includes at least the extraction of a wake-up cause (hereinafter, external cause) based on the received NM message. The activation condition may also include the occurrence of a wake-up cause (hereinafter, internal cause) in the terminal ECU 23. The activation unit 233 may have a function of notifying the calculation unit 234 of information indicating whether the transition from the sleep state to the wake-up state is due to an external cause or an internal cause.

[0038] The calculation unit 234 includes a computer having a CPU and a memory. When the end ECU 23 transitions to the wakeup state, the calculation unit 234 executes at least a state management process. The state management process is a process for managing the operating state of the end ECU 23, determining whether to maintain the wakeup state or transition to a sleep state.

[0039] [1-3-1. State management processing] The state management process executed by the calculation unit 234 of the terminal ECU 23 will be described with reference to the flowchart of FIG.

[0040] In S110, the calculation unit 234 starts a sleep timer and a periodic transmission timer. The sleep timer is a timer related to the sleep conditions used when transitioning the local terminal ECU 23 from a wake-up state to a sleep state. The sleep timer is set to time out in, for example, 1 second. The periodic transmission timer is a timer that determines the timing of transmitting an NM message. The periodic transmission timer is set to time out in, for example, 10 ms. The timeout times of the sleep timer and the periodic transmission timer are not limited to the above settings and can be set arbitrarily.

[0041] In S120, the calculation unit 234 transmits an NM message including the PN filter information held by the local end ECU 23 as PN request information in an IP packet with the TTL value of the IP header set to 1. Instead of using the PN filter information as is as the PN request information, part of the PN filter information may be used as the PN request information depending on the state of the local end ECU 23. For example, the PNC to be activated may differ depending on whether the wake-up is due to an external factor or an internal factor.

[0042] In S130, the calculation unit 234 determines whether or not the sleep conditions are satisfied. One of the sleep conditions includes at least the time-out of the sleep timer. If the calculation unit 234 determines that the sleep conditions are satisfied, it ends the process and transitions its own terminal ECU 23 to the sleep state. If the calculation unit 234 determines that the sleep conditions are not satisfied, it proceeds to S140.

[0043] In S140, the calculation unit 234 determines whether or not it has received an NM message (hereinafter, a target NM message) having PN activation information in which the PNC bit corresponding to the PNC to which its own terminal ECU 23 belongs is set to 1. If the calculation unit 234 determines that it has received the target NM message, it proceeds to S150, and if it determines that it has not received the target NM message, it proceeds to S160.

[0044] In S150, the calculation unit 234 restarts the sleep timer and returns the process to S130. In S160, the calculation unit 234 determines whether the periodic transmission timer has expired, and if the periodic transmission timer has expired, the process proceeds to S170, and if the periodic transmission timer has not expired, the process returns to S130.

[0045] In S170, the calculation unit 234 restarts the periodic transmission timer and transmits the same NM message as in the previous S120, that is, the NM message carried on an IP packet with a TTL value set to 1, and then returns the process to S130.

[0046] That is, in the wake-up state, the end-user ECU 23 transmits an NM message at regular intervals determined by the setting value of the periodic transmission timer. Also, if the end-user ECU 23 does not receive a target NM message for a regular interval determined by the setting value of the sleep timer, the end-user ECU 23 transitions to the sleep state.

[0047] [1-4. Zone ECU] The plurality of zone ECUs 22 are all configured in the same manner. As shown in FIG. 1, the zone ECU 22 includes a transmitter 221, a receiver 222, a transfer unit 223, a calculator 224, a memory 225, and an update unit 226.

[0048] The transmitter 221 has a function of transmitting a message via one of a plurality of communication ports that the own zone ECU 22 has. The receiving unit 222 has a function of receiving a message from another ECU 2 via one of a plurality of communication ports that the own zone ECU 22 has.

[0049] The transfer unit 223 has a function of transferring messages other than NM messages received from other ECUs 2 according to the destination indicated in the message. The calculation unit 224 realizes a function of deleting unnecessary IP packets by using the TTL of the IP packets, and a function of transferring a received NM message to one or more other communication ports.

[0050] The calculation unit 224 includes a computer having a CPU and a memory, similar to the calculation unit 234 of the terminal ECU 23. The calculation unit 224 executes at least IP packet processing.

[0051] The storage unit 225 stores an NM table. As shown in FIG. 7, the NM table is a collection of data linking port numbers, zone categories, hop counts, node identification data, and PN filter information.

[0052] The node identification data is information that uniquely identifies the end ECU 23. The node identification data may be any of a node ID, a MAC address, and an IP address. The NM table lists the node identification data for all end ECUs 23 that belong to the in-vehicle network system 1. In FIG. 7, the entry "End A" shown in the node identification data column indicates "end ECU_A." The same applies to FIGS. 9 and 10 below.

[0053] The zone category is information indicating to which zone the end ECU 23 identified by the node identification data (hereinafter referred to as the target end ECU 23) belongs (that is, to which zone ECU 22 it is connected).

[0054] The port number is information that identifies the communication port to which the target end ECU 23 is connected or the communication port that leads to the zone ECU 22 to which the target end ECU 23 is connected. In other words, it is information that indicates which communication port can be used to reach the target end ECU 23.

[0055] The number of hops indicates the number of routings (i.e., the number of transfers) required to reach the target end ECU 23 from the own-zone ECU 22. For example, the number of hops to the subordinate end ECU 23 connected to the own-zone ECU 22 or to the adjacent zone ECU 22 is 1, and the number of hops to the subordinate end ECU 23 of the adjacent zone ECU 22 is 2.

[0056] The PN filter information is a PNI indicating to which PNC the target end ECU 23 belongs. As shown in FIG. 7, the NM table is set individually for each zone ECU 22, and all the zone ECUs 22 have the same contents for items other than the port number and the number of hops.

[0057] End ECUs A to C identified by the node identification data belong to zone A, so their zone category is set to A. End ECUs D to E belong to zone B, so their zone category is set to B. End ECU X belongs to zone C, so their zone category is set to C.

[0058] When the port numbers of the communication ports in each zone ECU 22 and the connection structure between the ECUs 2 are as shown in FIG. 1, the port numbers and the number of hops are set as follows. Focusing on the NM table of zone ECU_A, as shown in the upper part of FIG. 7, the port number of the communication port leading to end ECU_A belonging to zone A is set to P1. Furthermore, since end ECU_A is directly connected to communication port P1 of zone ECU_A, the number of hops is set to 1. The port number of the communication port leading to end ECU_D belonging to zone B is set to P4. Furthermore, since end ECU_D is connected to communication port P4 of zone ECU_A across zone ECU_B, the number of hops is set to 2. The port number of the communication port leading to end ECU_X belonging to zone C is set to P5. Furthermore, since end ECU_X is connected to communication port P5 of zone ECU_A across zone ECU_C, the number of hops is set to 2.

[0059] Focusing on zone ECU_B, as shown in the lower part of FIG. 7, the port number of the communication port leading to end ECU_A belonging to zone A is set to P5. Furthermore, end ECU_A is connected to communication port P5 of zone ECU_B with zone ECU_A in between, so the number of hops is set to 2. The port number of the communication port leading to end ECU_D belonging to zone B is set to P1. Furthermore, end ECU_D is directly connected to communication port P1 of zone ECU_B, so the number of hops is set to 1. The port number of the communication port leading to end ECU_X belonging to zone C is set to P5. Furthermore, end ECU_X is connected to communication port P5 of zone ECU_B with zone ECU_A and zone ECU_C in between, so the number of hops is set to 3.

[0060] [1-4-1.IP packet processing] The IP packet processing executed by the calculation unit 224 when the zone ECU 22 is in the wake-up state will be described with reference to the flowchart of Fig. 8. The IP packet processing is executed every time an IP packet is received via any of the communication ports.

[0061] In S210, the calculation unit 224 decrements the TTL value included in the header area of ​​the IP packet by one. In S220, the calculation unit 224 determines whether the TTL value is greater than 0, and if the TTL value is greater than 0, the process proceeds to S250, and if the TTL value is equal to or less than 0, the process proceeds to S230.

[0062] In S230, the calculation unit 224 determines whether the received IP packet contains an NM message and whether the source is an end-level ECU 23 subordinate to the own-zone ECU 22. The determination of whether the IP packet contains an NM message is performed, for example, by checking the protocol field of the IP header. The determination of the source of the NM message is performed, for example, by checking any one of the NID included in the NM message, the source IP address included in the IP header, and the source MAC address included in the header of the Ethernet frame. If the calculation unit 224 determines that the received IP packet contains an NM message from a end-level ECU 23 subordinate to the own-zone ECU 22, the calculation unit 224 proceeds to S240. If the calculation unit 224 determines that the received IP packet does not contain an NM message from a end-level ECU 23 subordinate to the own-zone ECU 22, the calculation unit 224 proceeds to S260.

[0063] In S240, the calculation unit 224 resets the TTL value of the received IP packet using the hop count indicated in the NM table, and proceeds to S250. Specifically, the calculation unit 224 calculates a logical product of the PN request information included in the NM message and the PN filter information of each end ECU 23 indicated in the NM table, and extracts end ECUs 23 for which the calculation result is non-zero. The calculation unit 224 resets the TTL value of the received IP packet according to the maximum value of the hop counts of the extracted end ECUs 23.

[0064] In S250, the calculation unit 224 executes a routing process for the IP packet and ends the process. In the routing process, if the IP packet carries an NM message, the IP packet is forwarded to all communication ports other than the communication port that received the IP packet carrying the NM message. This type of forwarding is called port forwarding. Note that if the IP packet does not carry an NM message, the calculation unit 224 executes routing according to the destination IP address included in the IP header.

[0065] In S260, the calculation unit 224 discards the received IP packet, that is, the IP packet whose TTL value has become 0 and whose TTL value has not been reset based on the number of hops, and ends the process.

[0066] [1-4-2. Update section] When a preset update condition is met, the update unit 226 updates the NM table stored in the storage unit 225. The update condition may include the addition of a new terminal ECU 23, the updating of a program installed in the terminal ECU 23, the acquisition of update data for the NM table from an external source, etc. In this embodiment, the update unit 226 is provided separately from the calculation unit 224, but the update unit 226 may also be realized as part of the processing executed by the calculation unit 224.

[0067] A case will be described in which a new end ECU 23 (hereinafter referred to as end ECU_G) is connected to the communication port P6 of the zone ECU_B, as indicated by the symbol E1 in Fig. 1. When the end ECU_G is started for some reason, it transmits an NM message including its own PN filter information as PN request information.

[0068] The update unit 226 of the zone ECU_B refers to its own NM table and, if it detects that the information on the end ECU_G indicated in the received NM message is not registered in the NM table, adds an item for the end ECU_G to the NM table as shown in the upper part of FIG. 9. Note that the shaded portions in FIG. 9 are changes from the initial setting of the NM table of the zone ECU_B shown in the lower part of FIG. 7. This addition is also transferred to the other zone ECUs 22, and an item for the end ECU_G is added to the NM table in each zone ECU 22. When adding the item for the end ECU_G to the NM table, the zone ECU_B to which the end ECU 23 has been added sets the zone category to zone B to which the zone ECU_B belongs. The port number is set to P6, which indicates the communication port through which the NM message was received. The hop count is set to 1 because the end ECU_G has been added to the zone ECU_B itself. The zone ECU may detect that the end ECU has been added to its own zone ECU_B, for example, by SOME / IP service discovery, which is one of the common service communications in in-vehicle networks. Alternatively, a technology for detecting new communications used in a consumer network may be implemented in the relay device to detect the new communications.

[0069] The other zone ECUs 22 that have received the update information (i.e., the item of the end ECU_G to be added) update their own NM tables in accordance with the update information. Specifically, in accordance with the zone category indicated in the update information, information linking the port number of the communication port to which the zone ECU_B corresponding to the zone category is connected or which leads to the zone ECU_B with the item of the end ECU_G that is the update information is added to the NM table. The hop count is set to the same value as the hop count set for the other end ECUs 23 that have the same zone category.

[0070] As shown by reference symbol E2 in FIG. 7, a case will be described in which the PN filter information is changed by updating the program of the end ECU_D subordinate to the zone ECU_B. In this case, the end ECU_D transmits an NM message (hereinafter referred to as an update instruction) that includes the changed PN filter information and requests PNC learning (i.e., the PNL bit is enabled). In the zone ECU 22 that receives the update instruction, the update unit 226 updates the PN filter information for the end ECU_D that has already been registered in its own NM table in accordance with the contents of the update instruction, as shown in the lower part of FIG. 9. The update unit 226 also transfers the update instruction to the other zone ECUs 22. As a result, the NM tables in all zone ECUs 22 are updated.

[0071] Furthermore, the update unit 226 may be configured to, for example, when receiving update data for the NM table from the outside via the wireless device 3, update the NM table in accordance with the received update data.

[0072] [1-5. Example of operation] For example, let us consider a case where the NM message transmitted from end ECU_D indicates PN request information including the PNC to which end ECU_X belongs. In this case, the TTL value of the IP packet carrying the NM message transmitted by end ECU_D is set to 1. When zone ECU_B receives this IP packet carrying the NM message, it decrements the TTL value by 1, making the TTL value zero. However, since the IP packet carries the NM message received from the subordinate end ECU_D, zone ECU_B does not discard the IP packet, but instead resets the TTL value according to the NM table and outputs it to each communication port.

[0073] The end ECUs 23 extracted when resetting the TTL value include end ECU_X. If end ECU_X has the largest number of hops among the extracted end ECUs, the TTL value of the IP packet to be transferred is set to 3. When this IP packet is transferred to the adjacent zone ECU_A or zone ECU_D, the TTL value is decremented at the transfer destination to 2, but since it is not 0, further transfer is performed. As a result, the IP packet reaches end ECUs A to C and zone ECU_C. If end ECUs A to C contain a PNC in the PN request information indicated in the NM packet that matches the PN filter information held by their own end ECU 23, they perform a process to wake up their own end ECU 23. The TTL value of the IP packet that arrives at zone ECU_C is decremented to 1, and the IP packet is transferred to end ECU_X. Furthermore, IP packets received via zone ECU_A are also transferred to zone ECU_D if the communication port Px is not set as a blocking port. A received IP packet that arrives at zone ECU_C via the route of zone ECU_D is also forwarded to zone ECU_A if the communication port Px is not set as a blocking port. An IP packet that arrives at zone ECU_A or D via zone ECU_C has a TTL value of 0, so it is discarded without being forwarded further.

[0074] [1-6. Terminology] In this embodiment, the zone ECU 22 corresponds to the relay node of the present disclosure, and the end ECU 23 corresponds to the end node of the present disclosure. In this embodiment, the PN request information corresponds to the startup request information of the present disclosure, the PN filter information corresponds to the startup filter information of the present disclosure, and the PNC corresponds to the startup cluster of the present disclosure. In this embodiment, the NM message corresponds to the startup message of the present disclosure, and the NM table corresponds to the startup table of the present disclosure. In this embodiment, the hop number corresponds to the required forwarding information of the present disclosure, the TTL value corresponds to the permitted forwarding information of the present disclosure, and the port number corresponds to the path information of the present disclosure. In this embodiment, the processes of S210 to S260 executed by the calculation unit 224 of the zone ECU 22 correspond to the rewrite transfer unit of the present disclosure. In this embodiment, the processes of S110 to S170 executed by the calculation unit 234 of the end ECU 23 correspond to the state management unit of the present disclosure.

[0075] [1-7.Effects] According to the first embodiment described above in detail, the following effects are achieved. (1a) In the in-vehicle network system 1, the TTL function of IP packets is used, and the end ECU 23 that is the sender of an NM message transmits the NM message by incorporating it into an IP packet with a TTL value of 1. The zone ECU 22 decrements the TTL value of the received IP packet. If the NM message is incorporated into an IP packet whose TTL value has become 0 and the sender of the NM message is an end ECU 23 subordinate to the own zone ECU 22, the TTL value of the IP packet is reset using the NM table and port forwarding is performed. According to the in-vehicle network system 1, NM messages that do not reach their destination due to broadcast forwarding can be removed at an appropriate time, thereby reducing the communication volume of startup messages.

[0076] (1b) In the in-vehicle network system 1, the wireless device 3 is connected to the network via the zone ECU 22 and configured as an SDV. SDV stands for Software-Defined Vehicle. Therefore, the in-vehicle network system 1 can not only support software downloads and updates via OTA, but also support wake-up instructions from outside the in-vehicle network system 1. OTA stands for Over The Air.

[0077] (1c) According to the in-vehicle network system 1, the NM table held by the zone ECU 22 is updated in response to the addition of an end ECU 23 or an update of a program, so that the system can be flexibly adapted to changes.

[0078] [2. Second Embodiment] [2-1. Differences from the first embodiment] The second embodiment has the same basic configuration as the first embodiment, so differences will be described below. Note that the same reference numerals as those in the first embodiment indicate the same configuration, and reference will be made to the preceding description.

[0079] In the first embodiment described above, the end ECU 23 sets the TTL value of the IP packet carrying the NM message to 1, and the zone ECU 23 that receives the NM message from the subordinate end ECU 23 rewrites the TTL value in accordance with the hop number in the NM table and forwards the message. In contrast, the second embodiment differs from the first embodiment in that the end ECU 23 sets the TTL value to the hop number, and the zone ECU 22 only decrements the TTL value and forwards the message to the port.

[0080] [2-2.Configuration] In the second embodiment, the terminal ECU 23 shown in Fig. 1 is replaced with a terminal ECU 23a shown in Fig. 11. As shown in Fig. 11, the terminal ECU 23a includes a receiving unit 231, a transmitting unit 232, a starting unit 233, a calculating unit 234, and a storage unit 235.

[0081] The storage unit 235 stores a forwarding information table. As shown in FIG. 12, the transfer information table lists information associating the number of hops with PNCs for at least all PNCs to which the local end ECU 23a belongs.

[0082] When the in-vehicle network system 1 is connected as shown in Fig. 1, the transfer information table of end ECU_D is set as follows. Assume that end ECU_D belongs to cluster A to which end ECUs A, B, C, and D belong, cluster B to which end ECUs D, E, and F belong, and cluster D to which end ECUs X, C, and D belong. In cluster A, end ECUs A and B require the greatest number of transfers to reach their destination (hereinafter referred to as required number of transfers), and the number of hops is set to 3. In cluster B, end ECUs E and F require the greatest number of transfers, and the number of hops is set to 2. In cluster C, end ECU_X requires the greatest number of transfers, and the number of hops is set to 4.

[0083] When executing the state management process shown in Figure 6, the calculation unit 234 of the terminal ECU 23a transmits the NM message at S120 and S170 using an IP packet in which the number of hops linked to the PNC indicated as PN request information is set as the TTL value in accordance with the forwarding information table.

[0084] In the zone ECU 22, the hop number item may be omitted from the NM table stored in the storage unit 224. When performing the IP packet processing shown in Fig. 8, the calculation unit 224 performs processing in which S230 and S240 are omitted.

[0085] [2-3. Effects] According to the second embodiment described above in detail, the effects (1b) and (1c) of the first embodiment described above are achieved, and further, the following effects are achieved.

[0086] (2a) In the second embodiment, an appropriate TTL value is set in the end ECU 23a, which is the source of the NM message. Therefore, an NM message that does not reach its destination due to broadcast transfer can be removed at an appropriate timing, and the same effect as in the first embodiment, that is, the amount of communication of the activation message can be reduced, can be achieved while reducing the processing load on the zone ECU 22.

[0087] [2-4. Modifications] The end ECU 23a may further include an update unit that updates the forwarding information table. In this case, when the update unit receives information indicating that a new end ECU 23a has been added, the update unit may update the forwarding information table in accordance with the received information. The update unit may also update the Hop table by receiving update data for the forwarding information table from an external device via the wireless device 3 or the like.

[0088] 3. Other Embodiments Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.

[0089] (3a) In the above embodiment, the radio 3 is provided separately from the zone ECU 22. However, the radio 3 may be built into one or more of the zone ECUs 22. (3b) In the above embodiment, a switched network is used as the network topology for connecting the zone ECU 22 and the subordinate terminal ECU 23, but a bus network may also be used.

[0090] (3c) In the above embodiment, the zone ECU 22 transfers the received NM message to all communication ports except the communication port through which the NM message was received. The zone ECU 22 may use the NM table to extract the end ECUs 23 that belong to the PNC indicated in the PN activation request of the NM message, and transfer the NM message only to the communication ports leading to the extracted end ECUs 23. In this case, the amount of communication of the NM message can be further reduced.

[0091] (3d) In the above embodiment, when resetting the TTL value, the maximum value among the hop counts of the extracted end-ECUs 23 is used to reset the TTL value of all IP packets carrying the NM message in common. The extracted end-ECUs 23 may be classified by port number, and the maximum value among the hop counts of the classified end-ECUs 23 may be used to set the TTL value of the IP packet carrying the NM message to a different value for each communication port.

[0092] (3e) In the above embodiment, the TTL of the IP packet is used as the permitted forwarding information, but the NM message may be carried in a packet other than the IP packet. When a packet other than the IP packet is used, information that realizes a function equivalent to the TTL may be set in the data area, etc.

[0093] (3f) In the above embodiment, it is assumed that only one path leading to each end ECU 23 is registered in the NM table, but multiple paths may be registered. In this case, the communication port with the smallest number of hops among the multiple paths related to the end ECU 23 of interest may be used for processing.

[0094] (3g) In the above embodiment, each zone ECU 22 uses one NM table. However, as shown in FIG. 10, multiple types of NM tables may be prepared in advance depending on the equipment status of the vehicle equipped with the in-vehicle network system 1, such as the destination and vehicle grade. In this case, the NM table to be used can be selected, for example, at the time of shipping. The NM table may be selected by a dedicated physical switch or by an external instruction via the wireless device 3. Alternatively, the equipment status of the vehicle may be identified from information flowing through the in-vehicle network system 1, and an NM table may be automatically selected.

[0095] (3h) The computing units 224, 234 and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the computing units 224, 234 and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the computing units 224, 234 and the methods described herein may be implemented by one or more special-purpose computers configured by combining a processor and memory programmed to perform one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible storage medium. The methods for implementing the functions of the computing units 224, 234 do not necessarily need to include software; all of the functions may be implemented using one or more hardware devices.

[0096] (3i) Multiple functions of one component in the above embodiments may be realized by multiple components, or one function of one component may be realized by multiple components. Also, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

[0097] (3j) In addition to the above-described in-vehicle network system 1, the present disclosure can also be realized in various forms, such as relay nodes and terminal nodes that are components of the in-vehicle network system 1, a program for causing a computer to function as a relay node or terminal node, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a method for transferring a startup message.

[0098] [9. Technical Ideas Disclosed in This Specification] [Item 1] a plurality of relay nodes (22) each having a plurality of communication ports; a plurality of terminal nodes (23) each connected to any one of the plurality of relay nodes; Equipped with a subordinate node that is the terminal node subordinate to the relay node, or another relay node different from the relay node, is connected to each of the plurality of communication ports of the relay node; The terminal node is a state management unit (234: S110 to S170) configured to transmit a startup message including startup request information indicating a startup cluster to which the terminal node belongs and permitted forwarding information in which the permitted number of forwardings is set to 1; Equipped with The relay node a storage unit (225) that stores a start table in which information linking node identification information that identifies the terminal node with required forwarding information that indicates the number of forwardings required to reach a target node that is the terminal node identified by the node identification information is listed for each of the plurality of terminal nodes; a rewrite transfer unit (224: S210 to S260) configured to decrement a value indicated by the permission forwarding information when the startup message is received via the communication port, and if the value of the permission forwarding information after the decrement is greater than 0, to transfer the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is other than the subordinate node, to delete the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is the subordinate node, to rewrite the permission forwarding information of the startup message in accordance with the startup table using the required forwarding information linked to a target terminal node that is the terminal node belonging to the startup cluster indicated by the startup request information, and to transfer the startup message; Equipped with In-vehicle network system.

[0099] [Item 2] The in-vehicle network system according to item 1, The terminal node is a wake-up unit (233) configured to transition the terminal node from a sleep state to a wake-up state when a preset wake-up condition is met; the state manager is configured to send the wake-up message while the end node is in the wake-up state; The wake-up state is a normal operating state in which the functions of the terminal node can be executed without any restrictions, The sleep state is a low-power operation state in which at least a part of the functions of the terminal node is limited. In-vehicle network system.

[0100] [Item 3] The in-vehicle network system according to item 1 or 2, The rewrite transfer unit is configured to rewrite the permitted forwarding information to a maximum value among the required forwarding information associated with the plurality of target terminal nodes when there are a plurality of target terminal nodes. In-vehicle network system.

[0101] [Item 4] The in-vehicle network system according to any one of items 1 to 3, The startup table further includes information linking startup filter information listing the startup cluster to which the target node belongs and route information indicating the communication port leading to the target terminal node among the communication ports provided in the relay node that holds the startup table, to the node identification information; The rewrite transfer unit is configured to transfer the start message only to the communication port leading to the target terminal node. In-vehicle network system.

[0102] [Item 5] Item 4. The in-vehicle network system according to item 4, the rewrite transfer unit is configured to, when there are a plurality of target terminal nodes and a plurality of communication ports linked to the target terminal nodes by the route information, transfer the boot message in which the permitted forwarding information has been rewritten to the maximum value of the required forwarding information linked to the plurality of target terminal nodes for each communication port; In-vehicle network system.

[0103] [Item 6] Item 5: An in-vehicle network system according to any one of items 1 to 5, an update unit (226) configured to update the activation table when a predetermined update condition is met; In-vehicle network system.

[0104] [Item 7] Item 6. The in-vehicle network system according to item 6, the update condition includes receiving the invocation message from the terminal node that is not registered in the invocation table; In-vehicle network system.

[0105] [Item 8] The in-vehicle network system according to item 6 or 7, the update condition includes receiving an update instruction indicating update data for the invocation table from the terminal node registered in the invocation table; In-vehicle network system.

[0106] [Item 9] The in-vehicle network system according to any one of items 6 to 8, the update condition includes obtaining update data for the startup table from outside the in-vehicle network system. In-vehicle network system.

[0107] [Item 10] An in-vehicle network system according to any one of items 1 to 9, the relay node is configured to have a plurality of types of the startup tables and to select and use one of the plurality of types of the startup tables according to the state of equipment of a vehicle equipped with the in-vehicle network system; In-vehicle network system.

[0108] [Item 11] An in-vehicle network system according to any one of items 1 to 10, The trigger message is carried in an IP packet; The permitted forwarding information is configured to use a TTL included in an IP header. In-vehicle network system.

[0109] [Item 12] A method for transferring a startup message in an in-vehicle network system, comprising: a plurality of relay nodes each having a plurality of communication ports; and a plurality of end nodes each connected to one of the plurality of relay nodes, wherein a subordinate node which is the end node subordinate to the relay node or another relay node different from the relay node is connected to each of the plurality of communication ports of the relay node, The end node transmits a start message including start request information indicating the start cluster to which the end node belongs and permitted forwarding information in which the permitted number of forwardings is set to 1 (S120, S170); When the start message is received via the communication port, the value indicated by the permitted transfer information is decremented (S210); If the value of the permission transfer information after decrement is greater than 0, transfer the Trigger message (S220, S250); If the value of the permission forwarding information after decrement is 0 and the sender of the start message is other than the subordinate node, delete the start message (S220, S230, S260); If the value of the permission forwarding information after decrement is 0 and the sender of the startup message is the subordinate node, the permission forwarding information of the startup message is rewritten using necessary forwarding information linked to the target terminal node, which is the terminal node belonging to the startup cluster indicated by the startup request information, according to the startup table, and the startup message is forwarded (S220, S230 to S250); Including, The start table lists, for each of the plurality of terminal nodes, information linking node identification information for identifying the terminal node with the required forwarding information indicating the number of forwardings required to reach the terminal node, which is the target node, identified by the node identification information. How the startup message is forwarded.

[0110] [Item 13] a terminal node (23) connected to any one of a plurality of relay nodes (22) and constituting an in-vehicle network system together with the plurality of relay nodes, a wake-up unit (233) configured to transition the terminal node from a sleep state to a wake-up state when a preset wake-up condition is met; a state management unit (234: S110 to S170) configured to transmit a wake-up message including wake-up request information indicating a wake-up cluster to which the terminal node belongs and permitted forwarding information in which the permitted number of forwardings is set to 1 while the terminal node is in the wake-up state; Equipped with The wake-up state is a normal operating state in which the functions of the terminal node can be executed without any restrictions, The sleep state is a low-power operation state in which at least a part of the functions of the terminal node is limited. Terminal node.

[0111] [Item 14] A relay node (22) having a plurality of communication ports, each of the plurality of communication ports of the relay node is connected to a subordinate node that is a subordinate of the relay node, or to another relay node different from the relay node, among a plurality of terminal nodes (23) configured to transmit a startup message including startup request information indicating a startup cluster to which the relay node belongs and permitted transfer information indicating the number of transfers permitted; and the relay node, together with the terminal node and the other relay node, constitutes an in-vehicle network system; a storage unit (225) that stores a start table in which information linking node identification information that identifies the terminal node with required forwarding information that indicates the number of forwardings required to reach the terminal node, which is a target node, identified by the node identification information is listed for each of the terminal nodes; a rewrite and forwarding unit (224: S210 to S260) configured to decrement a value indicated by the permission forwarding information when the startup message is received via the communication port, and if the value of the permission forwarding information after the decrement is greater than 0, to forward the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is other than the subordinate node, to delete the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is the subordinate node, to rewrite the permission forwarding information of the startup message in accordance with the startup table using the required forwarding information linked to a target terminal node that is the terminal node belonging to the startup cluster indicated by the startup request information, and to forward the startup message; A relay node comprising:

[0112] [Item 15] a plurality of relay nodes (22) each having a plurality of communication ports; a plurality of terminal nodes (23a) each connected to any one of the plurality of relay nodes; Equipped with a subordinate node that is the terminal node subordinate to the relay node, or another relay node different from the relay node, is connected to each of the plurality of communication ports of the relay node; The terminal node is a storage unit (235) for storing a forwarding information table in which information linking a start cluster to which the end node belongs with required forwarding information indicating the number of forwardings required to reach all of the end nodes belonging to the start cluster is listed for each start cluster; a state management unit (234: S110 to S170) configured to transmit a startup message including startup request information indicating the startup cluster and permitted forwarding information set to the required forwarding information linked to the startup cluster according to the forwarding information table; Equipped with The relay node a transfer unit (224: S210-220, S250-S260) configured to decrement a value indicated by the permission forwarding information when the startup message is received via the communication port, to transfer the startup message if the value of the permission forwarding information after the decrement is greater than 0, and to delete the startup message if the value of the permission forwarding information after the decrement is 0; Equipped with In-vehicle network system. [Explanation of symbols]

[0113] 1...In-vehicle network system, 2...ECU, 3...Radio, 4...Transmission path, 22...Zone ECU, 23...End ECU, 221, 231...Transmitter, 222, 232...Receiver, 223...Transfer unit, 224, 234...Calculation unit, 225...Memory unit, 226...Update unit, 233...Startup unit.

Claims

1. a plurality of relay nodes (22) each having a plurality of communication ports; a plurality of terminal nodes (23) each connected to any one of the plurality of relay nodes; Equipped with a subordinate node that is the terminal node subordinate to the relay node, or another relay node different from the relay node, is connected to each of the plurality of communication ports of the relay node; The terminal node is a state management unit (234: S110 to S170) configured to transmit a startup message including startup request information indicating a startup cluster to which the terminal node belongs and permitted forwarding information in which the permitted number of forwardings is set to 1; Equipped with The relay node a storage unit (225) for storing a start table in which information linking node identification information for identifying the terminal node with required forwarding information indicating the number of forwardings required to reach a target node, which is the terminal node identified by the node identification information, is listed for each of the plurality of terminal nodes; a rewrite and transfer unit (224: S210 to S260) configured to decrement a value indicated by the permission forwarding information when the startup message is received via the communication port, and if the value of the permission forwarding information after the decrement is greater than 0, to transfer the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is other than the subordinate node, to delete the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is the subordinate node, to rewrite the permission forwarding information of the startup message in accordance with the startup table using the necessary forwarding information linked to a target terminal node that is the terminal node belonging to the startup cluster indicated by the startup request information, and to transfer the startup message; Equipped with In-vehicle network system.

2. 2. The in-vehicle network system according to claim 1, The terminal node is The device further includes a wake-up unit (233) configured to transition the terminal node from a sleep state to a wake-up state when a preset wake-up condition is met, the state manager is configured to send the wake-up message while the end node is in the wake-up state; The wake-up state is a normal operating state in which the functions of the terminal node can be executed without any restrictions, The sleep state is a low-power operation state in which at least a part of the functions of the terminal node is limited. In-vehicle network system.

3. 2. The in-vehicle network system according to claim 1, The rewrite transfer unit is configured to rewrite the permitted forwarding information to a maximum value among the required forwarding information associated with the plurality of target terminal nodes when there are a plurality of target terminal nodes. In-vehicle network system.

4. 2. The in-vehicle network system according to claim 1, The startup table further includes information linking startup filter information listing the startup cluster to which the target node belongs and route information indicating the communication port leading to the target terminal node among the communication ports provided in the relay node that holds the startup table, to the node identification information; The rewrite transfer unit is configured to transfer the start message only to the communication port leading to the target terminal node. In-vehicle network system.

5. 5. The in-vehicle network system according to claim 4, the rewrite transfer unit is configured to, when there are a plurality of target terminal nodes and a plurality of communication ports linked to the target terminal nodes by the route information, transfer the boot message in which the permitted forwarding information has been rewritten to the maximum value of the required forwarding information linked to the plurality of target terminal nodes for each communication port; In-vehicle network system.

6. 2. The in-vehicle network system according to claim 1, an update unit (226) configured to update the startup table when a predetermined update condition is met; In-vehicle network system.

7. 7. The in-vehicle network system according to claim 6, the update condition includes receiving the invocation message from the terminal node that is not registered in the invocation table; In-vehicle network system.

8. 7. The in-vehicle network system according to claim 6, the update condition includes receiving an update instruction indicating update data for the invocation table from the terminal node registered in the invocation table; In-vehicle network system.

9. 7. The in-vehicle network system according to claim 6, the update condition includes obtaining update data for the startup table from outside the in-vehicle network system. In-vehicle network system.

10. 2. The in-vehicle network system according to claim 1, the relay node is configured to have a plurality of types of the startup tables and to select and use one of the plurality of types of the startup tables according to the state of equipment of a vehicle equipped with the in-vehicle network system; In-vehicle network system.

11. 2. The in-vehicle network system according to claim 1, The trigger message is carried in an IP packet, The permitted forwarding information is configured to use a TTL included in an IP header. In-vehicle network system.

12. A method for transferring a startup message in an in-vehicle network system, comprising: a plurality of relay nodes each having a plurality of communication ports; and a plurality of end nodes each connected to one of the plurality of relay nodes, wherein a subordinate node which is the end node subordinate to the relay node or another relay node different from the relay node is connected to each of the plurality of communication ports of the relay node, The end node transmits a startup message including startup request information indicating a startup cluster to which the end node belongs and permitted forwarding information in which the permitted number of forwardings is set to 1 (S120, S170); When the start message is received via the communication port, the value indicated by the permitted transfer information is decremented (S210); If the value of the permission transfer information after decrement is greater than 0, the start message is transferred (S220, S250); If the value of the permission forwarding information after decrement is 0 and the sender of the start message is other than the subordinate node, the start message is deleted (S220, S230, S260). If the value of the permission forwarding information after decrement is 0 and the sender of the startup message is the subordinate node, the permission forwarding information of the startup message is rewritten using necessary forwarding information linked to the target terminal node, which is the terminal node belonging to the startup cluster indicated by the startup request information, in accordance with the startup table, and the startup message is forwarded (S220, S230 to S250); Including, The start table lists, for each of the plurality of terminal nodes, information linking node identification information for identifying the terminal node with the required forwarding information indicating the number of forwardings required to reach the terminal node, which is the target node, identified by the node identification information. How the startup message is forwarded.

13. A terminal node (23) connected to any one of a plurality of relay nodes (22) and constituting an in-vehicle network system together with the plurality of relay nodes, a wake-up unit (233) configured to transition the terminal node from a sleep state to a wake-up state when a preset wake-up condition is met; a state management unit (234: S110 to S170) configured to transmit a wake-up message including wake-up request information indicating a wake-up cluster to which the terminal node belongs and permitted forwarding information in which the permitted number of forwarding times is set to 1 while the terminal node is in the wake-up state; Equipped with The wake-up state is a normal operating state in which the functions of the terminal node can be executed without any restrictions, The sleep state is a low-power operation state in which at least a part of the functions of the terminal node is limited. Terminal node.

14. A relay node (22) having a plurality of communication ports, each of the plurality of communication ports of the relay node is connected to a subordinate node that is a subordinate of the relay node, or to another relay node different from the relay node, among a plurality of terminal nodes (23) configured to transmit a startup message including startup request information indicating a startup cluster to which the relay node belongs and permitted transfer information indicating the number of transfers permitted; and the relay node, together with the terminal node and the other relay node, constitutes an in-vehicle network system; a storage unit (225) for storing a start table in which information linking node identification information for identifying the terminal node with required forwarding information indicating the number of forwardings required to reach a target node, which is the terminal node identified by the node identification information, is listed for each of the plurality of terminal nodes; a rewrite and transfer unit (224: S210 to S260) configured to decrement a value indicated by the permission forwarding information when the startup message is received via the communication port, and if the value of the permission forwarding information after the decrement is greater than 0, to transfer the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is other than the subordinate node, to delete the startup message, and if the value of the permission forwarding information after the decrement is 0 and the source of the startup message is the subordinate node, to rewrite the permission forwarding information of the startup message in accordance with the startup table using the necessary forwarding information linked to a target terminal node that is the terminal node belonging to the startup cluster indicated by the startup request information, and to transfer the startup message; A relay node comprising:

Images