In-vehicle network system, activation message transmission procedure, end nodes and relay nodes

Abstract

An in-vehicle network system comprises: relay nodes (22), each containing communication ports; and end nodes (23), each connected to a relay node. Each communication port is connected to a child node. The end nodes contain a state management unit (234: S110 to S170) configured to transmit an activation message containing activation request information, which identifies an activation cluster to which the end nodes belong, and permitted transmission information.The relay nodes contain: a memory (225) that stores an activation table listing information that links node identification information with necessary transmission information; and a rewrite transmission unit (224: S210 to S260) configured to decrement a value identified by the permitted transmission information, delete the activation message, rewrite the permitted transmission information, and transmit the activation message, linking the necessary transmission information to a destination end node belonging to the activation cluster (224: S210 to S260).

Description

Technical field

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

[0002] In the patent literature described below 1, a subnetwork technology is known and the technology selectively controls wake / sleep states or arousal / rest states of each ECU that is connected to a vehicle-internal network system.

[0003] Patent Literature 1: JP 2021-011228 A

[0004] AUTOSAR R22-11: Specification of UDP Network Management, a standard for in-vehicle Ethernet networks, defines end nodes as periodically transmitting NM (Network Management Messages) to control an activation state, and relay nodes transmitting NM messages via broadcast. Ethernet is a registered trademark.

[0005] In a case where the NM message is transmitted via broadcast, if a loop is formed in the network, the NM message circulates, causing an increase in the amount of NM message communication.

[0006] One aspect of the present disclosure provides a technology for reducing the amount of communication messages related to controlling an activation state of a subnetwork.

[0007] According to one aspect of the present disclosure, an in-vehicle network system comprises multiple relay nodes and multiple end nodes. Each relay node contains multiple communication ports. Each end node is connected to one of the multiple relay nodes. Each communication port of the multiple relay nodes is connected to a child node, which is an end node that is subordinate to at least one relay node among the multiple end nodes. The end node contains a state management unit. The state management unit is configured to transmit an activation message containing activation request information that identifies an activation cluster to which the multiple end nodes belong, and permitted transmission information in which the permitted number of transmissions is set to one. The relay node contains a memory and a rewrite transmission unit.The memory stores an activation table. For each end node, the activation table lists information that links node identification information for identifying the end node with necessary transmission information. This transmission count specifies the number of transmissions required to reach a destination node, which is an end node identified by the node identification information among the multiple end nodes. The rewrite transmission unit is configured to decrement a value specified by the allowed transmission information when the activation message is received via the communication port, and to transmit the activation message if the value of the allowed transmission information after decrementing is greater than zero.The rewrite delivery unit deletes the activation message if the value of the permitted transmission information is zero after decrementing, and also if a transmission source for the activation message is not the child node. The rewrite delivery unit rewrites the permitted transmission information of the activation message and transmits the activation message if the value of the permitted transmission information is zero after decrementing, and also if a transmission source for the activation message is not the child node. The permitted transmission information is rewritten using the necessary transmission information associated with the target end node, which is an end node belonging to the activation cluster identified by the activation request information, according to the activation table.

[0008] According to this configuration, the relay node controlling the end node (the transmission source of the activation message) sets the appropriate permitted transmission information in the activation message. Accordingly, it is possible to remove activation messages that fail to reach their destinations due to broadcast transmission at an appropriate time. This allows for a reduction in the volume of activation messages.

[0009] One aspect of the present disclosure is a method for transmitting an activation message in a vehicle-internal network system. The vehicle-internal network system contains several relay nodes, each containing several communication ports, and several end nodes, each connected to one of the several relay nodes. Each communication port of the several relay nodes is connected to a child node, which is an end node subordinate to at least one relay node among the several end nodes. The activation message transmission method includes causing the several end nodes to transmit an activation message containing activation request information identifying an activation cluster to which the several end nodes belong, and permitted transmission information in which the permitted number of transmissions is set to one.The activation message transmission procedure includes decrementing a value, identified by the permitted transmission information, when the activation message is received via the communication interface. The activation message transmission procedure includes transmitting the activation message if the value of the permitted transmission information after decrementing is greater than zero. The activation message transmission procedure includes deleting the activation message if the value of the permitted transmission information after decrementing is equal to zero, and also if the transmission source of the activation message is not the child node.The activation message transmission procedure involves rewriting, according to an activation table, the permitted transmission information of the activation message and transmits the activation message if the value of the permitted transmission information is zero after decrementing, and also if the transmission source of the activation message is not the child node. The permitted transmission information is rewritten using the necessary transmission information associated with the target end node, which is an end node belonging to the activation cluster identified by the activation request information.The activation table lists information for each end node that links node identification information to identify the end node with necessary transmission information, which indicates a transmission count required to reach a target node that is an end node identified by the node identification information among the multiple end nodes.

[0010] By implementing such a method, it may be possible to obtain effects similar to those achieved by the vehicle-internal network system described above. According to one aspect of the present disclosure, an end node is connected to any one of several relay nodes, and the end node, together with the several relay nodes, configures a vehicle-internal network system. The end node includes an activation unit and a state management unit. The activation unit is configured to transition the several end nodes from a sleep state to a wake-up state when a preset activation condition is met.The state management unit is configured to transmit an activation message containing activation request information that identifies an activation cluster to which the end node belongs, and permitted transmission information, where the permitted number of transmissions is set to one, while the end node is in the wake-up state. The wake-up state is a normal operating state in which the end node's function can be executed without restriction. The sleep state is a low-power operating state in which at least some of the functionality of the multiple end nodes is restricted.

[0011] According to such a configuration, it can be used as the end node in the vehicle-internal network system described above. One aspect of the present disclosure is a relay node containing multiple communication ports. Each of the relay node's multiple communication ports is connected to a child node, which is an end node subordinate to the relay node, among multiple end nodes configured to transmit an activation message containing activation request information identifying an activation cluster to which the relay node belongs, and permitted transmission information identifying a permitted number of transmissions, or a different relay node distinct from the relay node. The relay node, together with the end nodes and the different relay node, configures a vehicle-internal network system.The relay node contains a memory and a rewrite transmission unit. The memory and rewrite transmission unit are configured similarly to the memory and rewrite transmission unit described in the vehicle-internal network system described above.

[0012] According to such a configuration, it can be used as a relay node in the vehicle's internal network system described above.

[0013] According to another aspect of the present disclosure, a vehicle-internal network system comprises: several relay nodes, each containing several communication ports; and several end nodes, each connected to one of the several relay nodes. Each communication port of the several relay nodes is connected to a subordinate node, which is an end node subordinate to at least one of the several relay nodes among the several end nodes.The multiple end nodes contain: a memory that stores a transmission information table listing information for each activation cluster, linking an activation cluster to which the end node belongs with necessary transmission information, identifying a transmission count necessary to reach all end nodes belonging to the activation cluster; and a state management unit configured to transmit an activation message containing activation request information identifying the activation cluster and permitted transmission information set to the necessary transmission information linked to the activation cluster by the transmission information table.The multiple relay nodes contain a rewrite transmission unit configured to decrement a value identified by the permitted transmission information when the activation message is received via the communication port, to transmit the activation message if the value of the permitted transmission information after decrementing is greater than zero, and to delete the activation message if the value of the permitted transmission information after decrementing is equal to zero.

[0014] The above and other features of the present disclosure will become even clearer from the following detailed description, which is made with reference to the accompanying drawings in which identical parts are designated with the same reference symbols. Fig. Figure 1 is a block diagram showing a configuration of an in-vehicle network system according to a first embodiment. Fig. Figure 2 is an explanatory diagram showing the configuration of an IP packet. Fig. Figure 3 is an explanatory diagram of a function of TTL. Fig. Figure 4 is an explanatory diagram showing a configuration of an NM message. Fig. Figure 5 is an explanatory diagram showing an overview of an activation process performed by an activation unit of an end-ECU upon receipt of the NM message. Fig. Figure 6 is a flowchart showing a state management process performed by an end-effect ECU. Fig. Figure 7 is an explanatory diagram showing the setting of an NM table in each zone ECU. Fig. Figure 8 is a flowchart showing an IP packet process executed by a zone ECU. Fig. Figure 9 is an explanatory diagram showing a setting of an NM table that is updated by adding the final ECU and updating a program. Fig. Figure 10 is an explanatory diagram showing several NM tables that are prepared in advance and selected for use. Fig. Figure 11 is a block diagram showing a configuration of an end-ECU in a second embodiment. Fig. Figure 12 is an explanatory diagram showing the settings of a transmission information table.

[0015] In the following, embodiments of the present disclosure are described with reference to the drawings. 1. First embodiment1-1. Configuration

[0016] As it is in Fig. As shown in Figure 1, a vehicle-internal network system 1 according to a first embodiment is connected to several electronic control units (hereinafter referred to as ECUs) 2 mounted on a vehicle via several transmission paths 4, which communicate using an Ethernet protocol. Ethernet is a registered trademark.

[0017] The ECU 2 has a wake-up state, which is a normal operating state in which its own functions can be performed without restriction, and a sleep state, which is a low-power operating state in which at least some of its own functions are restricted. The operating state of the ECU 2 is individually controlled using the NM message. NM stands for Network Management. This means that the vehicle's internal network system 1 is configured as a partial network (hereinafter referred to as PN). Furthermore, in the sleep state, the ECU 2 has at least one function: to receive the NM message and to bring the ECU 2 in question into the wake-up state, in accordance with the content of the NM message.

[0018] The multiple ECUs 2 are classified into multiple zone ECUs 22 and multiple end ECUs 23. Each zone ECU 22 is responsible for a zone into which a section of the vehicle is divided. The multiple zone ECUs 22 are interconnected via transmission paths 4 to form a communication network that includes redundant paths. Each zone ECU 22 is connected to multiple end ECUs 23 located within the zone via individual transmission paths 4. The zone ECU 22 controls subordinate end ECUs 23 that are directly connected to the zone ECU to implement coordinated control within the zone. One of the zone ECUs 22 can function as a central ECU. The central ECU controls the other zone ECUs 22 and implements coordinated control of the entire vehicle.

[0019] In the present embodiment, the vehicle is divided into four zones A to D, and the zone ECUs 22 located in each zone A to D are designated as zone ECU A, zone ECU B, zone ECU C, and zone ECU D. Zones A to D can be located in front of the vehicle, behind the vehicle, on one side of the vehicle, and on the other side of the vehicle. The number of zones is not limited to four, and the area can be subdivided into two or more zones.

[0020] As it is in Fig. As can be seen in Figure 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 individual transmission paths 4. Zone ECU C is connected to Zone ECU A and Zone ECU D via individual transmission paths 4. Zone ECU D is connected to Zone ECU B and Zone ECU C via individual transmission paths 4. In other words, the multiple Zone ECUs 22 are connected in a loop. However, by setting some of the communication ports connected to transmission path 4 as blocking ports, the communication frame is prevented from circulating. Fig. 1. The communication port to which transmission path 4 between zone ECU C and zone ECU D is connected is set as a blocking port. Communication via the blocking port can be prevented under normal conditions and can be released, for example, in the event of a failure of ECU 2, transmission path 4, or the like. This means that the blocking port can be used to ensure redundancy of the communication path. The multiple zone ECUs 22 can be described as forming a ring topology.

[0021] Three end ECUs 23 are connected to zone ECU A in a star topology via individual transmission paths 4. Hereinafter, the end ECU 23 connected to zone ECU A will also be referred to as an end ECU A, an end ECU B, and an end ECU C. Zone ECU A and end ECUs A through C form a switched network (hereinafter referred to as the switched network). It should be noted that the number of end ECUs 23 connected as subordinates in each zone ECU 22 is not limited to the above example and is arbitrary.

[0022] Three end-ECUs 23 are connected to zone-ECU B in a star configuration via individual transmission paths 4. In the following, the end-ECU 23 connected to zone-ECU A will also be referred to as end-ECU D, end-ECU E, and end-ECU F. This means that zone-ECU B and end-ECUs D through F form the switched network.

[0023] Zone ECU C is connected to End ECU 23 via a transmission path 4. Hereinafter, End ECU 23, which is connected to Zone ECU C, will also be referred to as End ECU X. Zone ECU D is connected to a wireless device 3, which communicates with a server or the like in a wireless wide-area network. Furthermore, Zone ECU C can also be connected to one or more End ECUs 23; however, for the sake of simplicity, this will not be illustrated or described here. 1-2. IP packet / NM message

[0024] An overview of an IP (Internet Protocol) packet and the NM message is provided with reference to the Fig. 2 to Fig. 5. It should be noted that the NM messages must conform to the specifications defined in AUTOSAR R22-11: Specification of UDP Network Management. It should be noted that the applicable specifications are not limited to R22-11. For example, a subsequent version such as R23-11 may also be used.

[0025] NM messages are transmitted and received using Ethernet frames that carry IP packets. As described in Fig. As shown in Figure 2, an Ethernet frame contains a physical header, an Ethernet header, payload, and a trailer. The physical header is a preamble. The Ethernet header contains a destination address, a source address, and other information. The payload is data and is contained within an IP frame. The trailer is a frame check sequence.

[0026] The IP packet contains an IP header and IP data. The IP header contains fields such as version, header length, service type, packet length, identifier, flags, fragment offset, lifetime, protocol, header checksum, source IP address, destination IP address, options, and padding.

[0027] The "Time to Live" field in the IP header is referred to below as TTL (Time to Live). As stated in Fig. As shown in Figure 3, the TTL is set in the end ECU 23, which is the transmission source of the IP packet, and is decremented by one each time the packet is forwarded or routed within the network. An IP frame whose TTL reaches 0 is discarded without being forwarded or routed. In this case, the transmission source of the IP packet is notified with an ICMP message called a Time Exceed. In other words, using the TTL function, IP packets are deleted after a certain period of time, thus preventing further circulation of IP packets even if a forwarding or routing loop is formed within the network.

[0028] The "Protocol", which is one of the fields in the IP header, specifies the protocol applied to data transmitted and received as IP data. Here, the protocol field is set to use UDP, and the NM message is transmitted and received as IP data.

[0029] The IP packet is a well-known technology, and the description of fields other than "TTL" and "Protocol" is omitted. As it is in Fig. As shown in Figure 4, the NM message contains an NID, a CBV, user data, and a PNI. The NID and CBV each consist of one byte. The user data has a variable length and Fig. Figure 2 shows a case where the user data is 4 bytes. The PNIs are variable and in Fig. The number 2 indicates a PNI case of two bytes. The positions of the NID and CBV in the NM message can be reversed.

[0030] NID is an abbreviation for Node Identifier and is information that identifies the node (i.e., the end ECU 23) that is the transmission source of the NM message. User data is an area where any data can be set by the user.

[0031] PNI is an abbreviation for Partial Network Information. The PNI is configured in the user data area and is represented by several bits. Each bit that makes up the PNI is called a PNC bit. PNC is an abbreviation for Partial Network Cluster. The PNC identifies a group (hereinafter referred to as a PN cluster) of end ECUs 23 that must be activated at the same time as the node (i.e., ECU 2). Each PNC bit is assigned to a different PN cluster. A PNC bit set to 1 indicates that a factor for waking up the PN cluster associated with that PNC bit is present. A PNC bit set to 0 indicates that there is no factor causing the PN cluster associated with that PNC bit to wake up.In the following, the PNI contained in the NM message to wake up the ECU 2 are referred to as PN request information.

[0032] CBV stands for Control Bit Vector, which is information that identifies the content of instructions via NM messages. The CBV contains a PNI bit, a PNL bit, an AW bit, an NMCSR bit, a PNSR bit, and an RMR bit. AW stands for Active Weakup. NMCSR stands for NM Coordinator Sleep Ready. PNSR stands for PN Shutdown Request. RMR stands for Repeat Message Request.

[0033] The PNI bit is information that indicates whether subnetwork management (hereinafter referred to as sub-NM) is supported. In the present embodiment, the PNI bit is set to a value indicating that it supports NM. If it is NM-compatible, the user data of the NM message will contain PN request information.

[0034] The PNL bit is information that indicates whether the message is the NM message 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 relevant to the main part of this disclosure, so their description is omitted. 1-3. End-ECU

[0035] As it is in Fig. As can be seen in Figure 1, the final ECU 23 contains a transmission unit 231, a receiving unit 232, an activation unit 233 and a calculation unit 234.

[0036] The transmission unit 231 has the function of transmitting a message generated by its own end-ECU 23. The receiving unit 232 has the function of receiving messages from other ECUs 2. The activation unit 233 has the function of bringing its own end-ECU 23 into the wake-up state based on the NM message received by the receiving unit 232 when its own end-ECU 23 is in the sleep state.

[0037] The computing unit 234 has at least one function of monitoring the transmission and reception of NM messages while its own end-ECU 23 is in the wake-up state, and of putting its own end-ECU 23 into the sleep state as required.

[0038] The end-ECU 23 maintains a PNI (hereinafter referred to as PN filter information) in which all PNC bits corresponding to the PN cluster to which its own 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) containing the PN request information, as described in Fig. As shown in Figure 5, the activation unit 233 compares the PN request information, which is indicated in the wake-up request, bit by bit with the PN filter information of its own end-ECU 23. As a result of the comparison, if there is a matching bit, the activation unit 233 transitions its own end-ECU 23 from sleep to wake-up. The comparison between the PN request information and the PN filter information can be performed by obtaining a logical product of the two pieces of information. In this case, if the result of the logical product is not zero, the PN request information indicates the PNC to which the own end-ECU 23 belongs; in other words, it is determined that a factor for waking up the own end-ECU 23 has occurred.

[0039] The activation unit 233 can be configured by hardware. When the activation condition is met, the activation unit 233 transitions the relevant end ECU 23 from the sleep state to the wake-up state. The activation condition includes at least the extraction of a wake-up factor (hereinafter referred to as an external factor) based on the received NM message. Furthermore, the activation condition can include the occurrence of a wake-up factor (hereinafter referred to as an internal factor) in the end ECU 23. The activation unit 233 can have a function of notifying the computation unit 234 with information indicating whether the transition from the sleep state to the wake-up state is due to an external or an internal factor.

[0040] The computing unit 234 contains a computer equipped with a CPU and memory. When the end ECU 23 is brought into the wake-up state, the computing unit 234 executes at least the state management process. The state management process is a process of maintaining the wake-up state, bringing the end ECU 23 into the sleep state, or managing its operating state. 1-3-1. Condition Management Process

[0041] The condition management process, which is executed by the computation unit 234 of the end ECU 23, is described with reference to a flowchart of Fig. 6 described.

[0042] In S110, the computation unit 234 starts the sleep timer and the periodic transmission timer. The sleep timer is a timer related to a sleep state, used when the relevant end ECU 23 transitions from the wake-up state to the sleep state. The sleep timer is set to a duration of, for example, 1 second. The periodic transmission timer determines the transmission timing of the NM message. The periodic transmission timer is set to a duration of, for example, 10 milliseconds. The duration intervals of the sleep timer and the periodic transmission timer are not limited to the above settings and can be configured as desired.

[0043] In S120, the compute unit 234 transmits an NM message containing the PN filter information held by its own end-ECU 23 as PN request information. The NM is contained within an IP packet with a TTL value set to 1 in the IP header. Instead of using the PN filter information as the PN request information, a portion of the PN filter information can be used as the PN request information, depending on the state of its own end-ECU 23. For example, the PNC to be activated can differ depending on whether the wake-up is caused by an external or internal factor.

[0044] In S130, the compute unit 234 determines whether the sleep state is fulfilled. One of the sleep states includes at least the expiration of the sleep timer. If the compute unit 234 determines that the sleep state is fulfilled, the process terminates and the relevant end ECU 23 enters sleep mode. If the compute unit 234 determines that the sleep state is not fulfilled, the process transitions to S140.

[0045] In S140, the computation unit 234 determines whether an NM message (hereinafter referred to as a destination NM message) containing PN activation information has been received, in which the PNC bit corresponding to the PNC to which the relevant end ECU 23 belongs is set to 1. If the computation unit 234 determines that the destination NM message has been received, the process proceeds to S150. If the computation unit 234 determines that the destination NM message has not been received, the process proceeds to S160.

[0046] In S150, compute unit 234 restarts the sleep timer and returns the process to S130. In S160, compute unit 234 determines whether the periodic transfer timer has expired. If the periodic transfer timer has expired, the process transitions to S170. If the periodic transfer timer has not expired, the process returns to S130.

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

[0048] This means that in the wake-up state, the end ECU 23 transmits the NM message at regular intervals based on the set value of the periodic transmission timer. Furthermore, the end ECU 23 enters sleep mode if it does not receive the target NM message for a specified period of time, based on the set value of the sleep timer. Zones 1-4 ECU

[0049] The multiple zone ECUs 22 are all configured in the same way. As shown in Fig. As can be seen in Figure 1, the zone ECU 22 contains a transmission unit 221, a receiving unit 222, a transmitting unit 223, a computation unit 224, a memory 225 and an update unit 226.

[0050] The transmission unit 221 has the function of transmitting a message via any of the several communication ports of the relevant zone ECU 22. The receiving unit 222 has the function of receiving messages from other ECUs 2 via any of the several communication ports of the relevant zone ECU 22.

[0051] The transmission unit 223 has a function of forwarding messages other than the NM message received by the other ECUs 2, according to the destination indicated in the message. The processing unit 224 implements a function of deleting unnecessary IP packets using the TTL of the IP packets and a function of forwarding the received NM message to one or more other communication ports.

[0052] Similar to the Computing Unit 234 of the End-ECU 23, the Computing Unit 224 contains a computer with a CPU and memory. The Computing Unit 224 executes at least one IP packet process.

[0053] Memory 225 stores the NM table. As it is in Fig. As shown in Figure 7, the NM table is a collection of data linked to connection numbers, zone categories, hop numbers (or jump numbers), node identification data, and PN filter information. In the drawings, the number may be shown as "No."

[0054] The node identification data is information that uniquely identifies the end-ECU 23. The node identification data can be any of the following: node ID, MAC address, and IP address. The NM table lists node identification data for all end-ECUs 23 belonging to the vehicle's in-vehicle network system 1. Fig. The entry “End A”, which can be seen in the node identification data column, is labelled “End-ECU A”. The same applies to the following entries. Fig. 9 and Fig. 10.

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

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

[0057] The hop number indicates the number of routings (i.e., the number of transmissions) required to reach the destination end ECU 23 from its own zone ECU 22. For example, the hop number to a subordinate end ECU 23 connected to its own zone ECU 22 or to a neighboring zone ECU 22 is one, and the hop number to a subordinate end ECU 23 of the neighboring zone ECU 22 is two.

[0058] The PN filter information is a PNI that identifies which PNC the target end-ECU 23 belongs to. As it is in Fig. As can be seen in Figure 7, the NM table is individually set for each Zone ECU 22, and all Zone ECUs 22 have the same content in terms of points except for the port number and the hop number.

[0059] Since end-of-line ECUs A to C, identified by the node identification data, belong to zone A, the zone category is set to A. Since end-of-line ECUs D to E belong to zone B, the zone category is set to B. Since end-of-line ECU X belongs to zone C, the zone category is set to C.

[0060] If the connection numbers of the communication ports in each zone ECU 22 and the connection structure between the ECUs 2 as in Fig. As shown in section 1, the connection numbers and hop number are set as follows. Focusing on the NM table of zone ECU A, as shown in the upper part of Fig. As shown in Figure 7, the communication port number leading to the end ECU A belonging to Zone A is set to P1. Additionally, since end ECU A is directly connected to communication port P1 of Zone ECU A, the hop number is set to one. The communication port number leading to end ECU D belonging to Zone B is set to P4. Additionally, since end ECU D is connected to communication port P4 of Zone ECU A via Zone ECU B, the hop number is set to 2. The communication port number leading to end ECU X belonging to Zone C is set to P5. Additionally, since end ECU X is connected to communication port P5 of Zone ECU A via Zone ECU C, the hop number is set to 2.

[0061] Focusing on zone ECU B, as shown in the lower part of Fig. As shown in diagram 7, the communication port number leading to end ECU A belonging to Zone A is set to P5. Additionally, since end ECU A is connected to the intermediate Zone ECU A via communication port P5 of Zone ECU B, the hop number is set to 2. The communication port number leading to end ECU D belonging to Zone B is set to P1. Additionally, since end ECU D is directly connected to communication port P1 of Zone ECU B, the hop number is set to 1. The communication port number leading to end ECU X belonging to Zone C is set to P5. Additionally, since end ECU X is connected to communication port P5 of Zone ECU B via Zone ECU A and Zone ECU C, the hop number is set to 3. 1-4-1. IP packet processing

[0062] The IP packet process, which is executed by the compute unit 224 when the zone ECU 22 is in the wake-up state, is described with reference to the flowchart of Fig. 8 described. The IP packet process is executed every time an IP packet is received via one of the communication ports.

[0063] In S210, the computation unit 224 decrements the TTL value contained in the header of the IP packet by one. In S220, the computation unit 224 determines whether the TTL value is greater than 0. If the TTL value is greater than 0, the process proceeds to S250. If the TTL value is equal to or less than 0, the process proceeds to S230.

[0064] In S230, the compute unit 224 determines whether the received IP packet contains the NM message and whether the transmission source is the end ECU 23, which is subordinate to its own zone ECU 22. The determination of whether the NM message is present is made, for example, by checking the protocol section of the IP header. The transmission source of the NM message is determined, for example, by checking one of the following pieces of information: the NID contained in the NM message, the transmission source IP address contained in the IP header, and the transmission source MAC address contained in the header of the Ethernet frame. If the compute unit 224 determines that the received IP packet contains the NM message from the subordinate end ECU 23, the process proceeds to S240. Furthermore, if the compute unit 224 determines that the received IP packet does not contain the NM message from the subordinate end ECU 23, the process passes to S260.

[0065] In S240, the computation unit 224 resets the TTL value of the received IP packet using the hop number indicated in the NM table, and the process then proceeds to S250. Specifically, a logical AND operation is performed between the PN request information contained in the NM message and the PN filter information of each end ECU 23 indicated in the NM table. Those end ECUs 23 for which the computation result is not zero are then identified. The TTL value of the received IP packet is reset according to the maximum value among the extracted hop numbers of the end ECUs 23.

[0066] In S250, the compute unit 224 executes the forwarding or routing process of the IP packet and then terminates the process. During forwarding, if the IP packet carries the NM message, the IP packet is forwarded to all communication ports except the one that received the packet carrying the NM message. This type of forwarding is called port forwarding. If the IP packet does not carry the NM message, the compute unit 224 performs forwarding according to the destination IP address contained in the IP header.

[0067] In S260, the compute 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 hop number, and terminates the process. 1-4-2. Update unit

[0068] The update unit 226 updates the NM table stored in memory 225 when a preset update condition is met. The update condition may include adding a new end-ECU 23, updating a program installed in the end-ECU 23, obtaining update data for the NM table from an external source, and the like. In the present embodiment, the update unit 226 is located separately from the computation unit 224; however, the update unit 226 can be implemented as part of the processes executed by the computation unit 224.

[0069] A case is described in which a new end-ECU 23 (hereinafter referred to as the end-ECU G) is connected to the communication port P6 of zone-ECU B, as indicated by the reference sign E1 in Fig. is marked 1. If the end ECU G is activated for any reason, it transmits the NM message, which contains its own PN filter information, as PN request information.

[0070] The update unit 226 of zone ECU B refers to its own NM table and, if it detects that the information of the end ECU G, which is indicated in the received NM message, is not registered in the NM table, it adds a point for the end ECU G to the NM table, as shown in the upper part of Fig. 9 can be seen. In Fig. The hatched areas are those that are determined by the initial settings of the NM table of the zone ECU B, which are located in the lower part of Fig. The 7 shown have been changed. This added content is also transmitted to the other Zone ECUs 22, and a point for End ECU G is added to the NM table in each Zone ECU 22. When a point for End ECU G is added to the NM table, the Zone category in Zone ECU B, to which End ECU 23 has been added, is set to Zone B, to which End ECU 23 belongs. The port number is set to P6, which identifies the communication port where the NM message was received. The hop number is set to 1, as End ECU G was added according to the control of its own Zone ECU B. The Zone ECU can detect that an End ECU has been added to its control, for example, through a SOME / IP service discovery, which is one of the common service communications in an in-vehicle network.Alternatively, a technique for detecting new communications used in a consumer network can be implemented in the relay device to detect the new communications.

[0071] The different zone ECU 22, which has received the update information (i.e., the point of the end ECU G to be added), updates its NM table in accordance with the update information.

[0072] Specifically, link information is added to the NM table according to the zone category indicated in the update information. This link information connects the port number of the communication port to which the zone ECU B corresponding to the zone category is connected or which the zone ECU B reaches, and the point on the end ECU G that contains the update information. The hop number is set to the same value as the hop number set for the other end ECU 23 that has the same zone category.

[0073] As indicated by the reference symbol E2 in Fig. Figure 7 describes a case in which the PN filter information is changed by updating the program of the end ECU D according to the zone ECU B. In this case, the end ECU D transmits an NM message (hereinafter referred to as an update instruction) containing the changed PN filter information and requesting PNC learning (i.e., enabling the PNL bit). In the zone ECU 22, which has received the update instruction, the update unit 226 updates the PN filter information for the end ECU D, which has been registered in its NM table as shown in the lower part of Figure 7. Fig. As shown in Figure 9, this is in accordance with the content of the update instruction. Furthermore, the update unit 226 transmits the above update instruction to the different zone ECU 22. This updates the NM table in all zone ECUs 22.

[0074] Furthermore, if, for example, the update unit 226 receives update data of the NM table from outside via the wireless device 3, it can update the NM table according to the received update data. 1-5. Operational example

[0075] For example, a case is described in which the NM message transmitted by the end ECU D identifies PN request information containing the PNC to which the end ECU X belongs. In this case, the TTL value of the IP packet carrying the NM message transmitted by the end ECU D is set to 1. The zone ECU B, which receives the IP packet carrying this NM message, decrements the TTL value by 1, making it zero. However, because the IP packet contains an NM message received by the subordinate end ECU D, the zone ECU B does not discard the IP packet but resets the TTL value according to the NM table and outputs it to each communication port.

[0076] The End ECUs 23 extracted when the TTL value is reset contain one End ECU X. If the hop number of End ECU X is the highest among the extracted End ECUs, the TTL value of the IP packet to be transmitted is set to 3. When this IP packet is transmitted to the adjacent Zone ECU A or Zone ECU D, the TTL value at the transmission destination is decremented to 2. However, since the TTL value is not 0, another transmission is performed. As a result, the IP packet reaches the end ECUs A to C and the zone ECU C. In the end ECUs A to C, the end ECUs A to C execute a process to wake up or awaken the end ECU 23 itself if the PNC, which matches the PN filter information held by the end ECU 23 itself, is present in the PN request information marked in the NM packet.The TTL value of the IP packet that reaches zone ECU C is decremented to 1 and then forwarded to the final ECU X. Additionally, the IP packet received via zone ECU A is also forwarded to zone ECU D if the communication port Px is not configured as a blocking port. The received IP packet that reaches zone ECU C via the path of zone ECU D is also forwarded to zone ECU A if the communication port Px is not configured as a blocking port. The IP packet that reaches zone ECUs A and D via zone ECU C has a TTL value of 0 and is therefore discarded without being forwarded. 1-6. Correspondence of terms

[0077] In the present embodiment, the zone ECU 22 corresponds to a relay node in the present disclosure, and the end ECU 23 corresponds to an end node in the present disclosure. In the present embodiment, the PN request information corresponds to activation request information in the present disclosure, the PN filter information corresponds to activation filter information in the present disclosure, and the PNC corresponds to an activation cluster in the present disclosure. In the present embodiment, the NM message corresponds to an activation message in the present disclosure, and the NM table corresponds to an activation table in the present disclosure.In the present embodiment, the hop number corresponds to necessary transmission information of the present disclosure, the TTL value corresponds to permitted transmission information of the present disclosure, and the port number corresponds to path information of the present disclosure. In the present embodiment, processes S210 to S260, which are executed by the computation unit 224 of the zone ECU 22, correspond to the rewrite transmission unit of the present disclosure. In the present embodiment, processes S110 to S170, which are executed by the computation unit 234 of the end ECU 23, correspond to the state management unit of the present disclosure. 1-7. Effect

[0078] According to a first embodiment, which is described in detail above, the following effects are achieved.

[0079] (1a) In the vehicle's internal network system 1, the TTL function of the IP packet is used, and the end ECU 23, which is the transmission source of the NM message, transmits the NM message in the IP packet with a TTL value of 1. The zone ECU 22 decrements the TTL value of the received IP packet. If an NM message is carried in an IP packet whose TTL value has become 0, and the transmission source of the NM message is the end ECU 23 according to its own zone ECU 22, the TTL value of the IP packet is reset using the NM table, and a retransmission is performed. According to the vehicle's internal network system 1, it is possible to remove NM messages that do not reach their destinations due to broadcast transmission at an appropriate time. It is possible to reduce the amount of activation messages being communicated.

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

[0081] (1c) According to the vehicle's internal network system 1, the NM table held by the zone ECU 22 is updated in response to the addition of the end ECU 23 or an update of a program, so that the system can be flexibly adapted to changes. 2. Second embodiment 2-1. Difference from the first embodiment

[0082] The basic configuration of a second embodiment is similar to that of the first embodiment. Therefore, the difference between them is described below. The same reference numerals as in the first embodiment denote the same elements, and reference is made to the preceding description.

[0083] In the first embodiment described above, the end ECU 23 sets the TTL value of the IP packet carrying the NM message to 1. The zone ECU 23, which receives the NM message from the subordinate end ECU 23, rewrites the TTL value according to the hop number in the NM table and transmits the message. In contrast, the second embodiment differs from the first 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 performs the hop transmission. 2-2. Configuration

[0084] In the second embodiment, the in Fig. 1 End-ECU 23 shown by a in Fig. The end ECU shown in section 11 replaces 23a. As shown in Fig. As can be seen in Figure 11, the final ECU 23a contains the transmission unit 231, the receiving unit 232, the activation unit 233, the calculation unit 234 and a memory 235.

[0085] Memory 235 stores a transmission information table. As described in Fig. As can be seen in section 12, the transmission information table lists information that assigns the hop number to the PNC for at least all PNCs to which the end ECU 23a belongs.

[0086] If the connections of the vehicle's internal network system 1 are as described in Fig. As shown in Figure 1, the transmission information table of end-ECU D is configured as follows. For example, it is assumed that end-ECU D belongs to cluster A, which includes end-ECUs A, B, C, and D; to cluster B, which includes end-ECUs D, E, and F; and to cluster D, which includes end-ECUs X, C, and D. In cluster A, end-ECUs A and B require the maximum number of transmissions to reach the destination (hereinafter referred to as the required number of transmissions), and the hop number is set to three. In cluster B, end-ECUs E and F have the maximum required number of transmissions, and the hop number is set to two. In cluster C, end-ECU X has the maximum required number of transmissions, and the hop number is set to four.

[0087] In a case where the calculation unit 234 of the final ECU 23a is in Fig. When performing the state management process shown in Figure 6, the compute unit 234, when transmitting the NM message in S120 and S170, transmits the NM message using an IP packet in which the hop number associated with the PNC, which is labelled as the PN request information, is set as a TTL value in accordance with the forwarding information table.

[0088] In zone ECU 22, the NM table stored in memory 225 can omit the decimal point of the hop number. If the calculation unit 224 contains the information in Fig. The IP packet processing shown in step 8 executes the processes in which S230 and S240 are omitted. 2-3. Effects

[0089] The second embodiment described above provides the effects (1b) and (1c) according to the first embodiment described above and the following effect.

[0090] (2a) In the second embodiment, a suitable TTL value is set or fixed in the final ECU 23a, which is the transmission source of the NM message. Therefore, it is possible to remove NM messages that do not reach their destination due to broadcast transmission at an appropriate time. It is possible to achieve the same effect as in the first embodiment, namely to reduce the volume of start messages while reducing the processing load on the zone ECU 22. 2-4th modification

[0091] The End-ECU 23a may also contain an update unit that updates the transmission information table. In this case, when the update unit receives information indicating that a new End-ECU 23a has been added, it can update the transmission information table in accordance with the received information. The update unit can also update a hop table by receiving transmission information table update data externally via the wireless device 3 or the like. 3. Other embodiments

[0092] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the embodiments described above and various modifications may be made.

[0093] (3a) In the above embodiments, the wireless device 3 is provided separately from the zone ECU 22, however, the wireless device 3 can be incorporated into one or more zone ECUs 22.

[0094] (3b) In the above embodiments, the switched network is used as the network topology for connecting the zone ECU 22 and the subordinate end ECU 23. However, a bus network can also be used.

[0095] (3c) In the embodiments described above, the zone ECU 22 transmits the received NM message to all communication ports except the one through which the NM message was received. The zone ECU 22 can use an NM table to extract the end ECU 23 that corresponds to the PNC identified in the PN activation request of the NM message and transmit the NM message only to the communication port that leads to the extracted end ECU 23. In this case, it is possible to reduce the amount of NM message communication.

[0096] (3d) In the above embodiment, when the TTL value is reset, the maximum value among the hop numbers of the extracted end ECUs 23 is used to collectively reset the TTL values ​​of all IP packets carrying the NM message. The extracted end ECUs 23 can be classified by port number, and the maximum value among the hop counts of the classified end ECUs 23 can be used so that the TTL value of the IP packet carrying the NM message can be set to a different value for each communication port.

[0097] (3e) In the embodiment above, the TTL of the IP packet is used as the permitted transmission information. However, the NM message can be carried in something other than the IP packet. If a packet other than an IP packet is used, information implementing a function equivalent to TTL can be set in a data area or the like.

[0098] (3f) In the above embodiments, it is assumed that only one path leading to each end ECU 23 is registered in the NM table. However, multiple routes may be registered in the NM table. In this case, the communication port with the lowest hop count among the multiple paths related to the target end ECU 23 can be used to perform the processing.

[0099] (3g) In the above embodiments, each zone ECU 22 uses an NM table. On the other hand, as described in Fig. As shown in Figure 10, for example, several types of NM tables can be prepared in advance, depending on the vehicle's equipment status with the vehicle's internal network system 1, such as the destination and the vehicle's gradient. In this case, it is possible, for example, to select which NM table to use at the time of dispatch. The NM table can be selected by a dedicated physical switch or by an external instruction via the wireless device 3. Furthermore, the vehicle's equipment status can be identified from the information flowing through the vehicle's internal network system 1, and the NM table can be selected automatically.

[0100] (3h) The computing units 224 and 234 and methods thereof described in this disclosure can 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 computing units 224 and 234 and methods thereof described in this disclosure can be implemented by a dedicated computer provided by configuring the processor with one or more dedicated hardware logic circuits.Alternatively, the computing units 224 and 234 and methods thereof described in this disclosure can be implemented by one or more dedicated computers configured with a combination of a processor and memory programmed to perform one or more functions, and a processor configured with one or more hardware logic circuits. The computer program can be stored in a computer-readable, non-volatile, tangible storage medium as instructions to be executed by a computer. The methods for implementing the function of each part contained in the computing units 224 and 234 do not necessarily involve software, and all functions can be implemented using one or more hardware components.

[0101] (3i) Several functions of a component in the embodiment described above may be implemented by several components, or a single function of a component may be implemented by several components. Several functions of several configuration elements may be implemented by a single configuration element, or a function implemented by several configuration elements may be implemented by a single configuration element. Part of the configuration of the embodiment described above may be omitted. At least part of the configuration in one embodiment may be added to or replaced by the configuration of another embodiment.

[0102] (3j) In addition to the vehicle-internal network system 1 described above, the present disclosure may also be implemented in various forms, such as relay nodes and end nodes that are components of the vehicle-internal network system 1, a program to cause a computer to function as the relay node or the end node, a non-volatile tangible storage medium, such as a semiconductor memory, on which this program is stored, and a method for transmitting the activation message. QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] JP 2021-011228 A

[0003]

Claims

[1] In-vehicle network system which features: a plurality of relay nodes (22), each containing multiple communication ports; and a plurality of terminal nodes (23), each connected to one of the plurality of relay nodes, where Each communication port of the multitude of relay nodes is connected to a subordinate node, which is an end node subordinate to at least one of the multitude of relay nodes, among the multitude of end nodes, and The multitude of end nodes contain a state management unit (234: S110 to S170) configured to transmit an activation message containing: Activation request information that identifies an activation cluster, which includes the multitude of end nodes, and Permitted transmission information in which the permitted number of transmissions is set to one, including the multitude of relay nodes: a memory (225) that stores an activation table which lists for each end node information linking node identification information for identifying the end node with required transmission information which indicates a transmission count required to reach a destination node which is an end node identified by the node identification information among the multitude of end nodes; and a rewrite transmission unit (224: S210 to S260) configured to to decrement a value characterized by the permitted transmission information when the activation message is received via the communication link, and to transmit the activation message if the value of the permitted transmission information after decrementing is greater than zero, to delete the activation message if the value of the permitted transmission information is zero after decrementing, and also if a transmission source of the activation message is not the child node, and According to the activation table, rewrite the permitted transmission information of the activation message using the required transmission information and transmit the activation message if the value of the permitted transmission information is zero after decrementing, and also if the transmission source of the activation message is the child node. wherein the necessary transmission information is linked to a destination end node, which is an end node belonging to the activation cluster characterized by the activation request information, among the plurality of end nodes (224: S210 to S260). [2] In-vehicle network system according to claim 1, wherein the plurality of end nodes further include an activation unit (233) that is configured to transition the plurality of end nodes from a sleep state to a wake-up state when a preset activation condition is met, the state management unit is configured to transmit the activation message while the end node is in the wake-up state, the wake-up state is a normal operating state in which a function of the multitude of end nodes can be executed without restriction, and The sleep state is an operating state with low energy consumption in which at least part of the function of the multitude of terminal nodes is restricted. [3] In-vehicle network system according to claim 1 or claim 2, wherein if the destination end node is a plurality of destination end nodes, the rewrite transmission unit is configured to rewrite the permitted transmission information to a maximum value of the necessary transmission information associated with the plurality of destination end nodes. [4] In-vehicle network system according to one of claims 1 to 3, wherein the activation table further includes: Information that links to the node identification information, activation filter information that lists the activation cluster to which the target node belongs, and Path information that identifies a communication port leading to the target end node among the multitude of communication ports of the multitude of relay nodes that hold the activation table, and the rewrite transmission unit is configured to transmit the activation message only to the communication port leading to the target end node. [5] In-vehicle network system according to claim 4, wherein if the destination end node is a plurality of destination end nodes and the communication port is also a plurality of communication ports linked to the plurality of destination end nodes by the path information, the rewrite transmission unit transmits the activation message in which the permitted transmission information is rewritten to a maximum value of the necessary transmission information linked to the plurality of destination end nodes for each communication port. [6] In-vehicle network system according to any one of claims 1 to 5, which further comprises an update unit (226) configured to update the activation table when a predetermined update condition is met. [7] In-vehicle network system according to claim 6, wherein the update condition includes receiving the activation message from an end node among the plurality of end nodes that is not registered in the activation table. [8] In-vehicle network system according to claim 6 or claim 7, wherein the update condition includes receiving an update instruction, which identifies update data of the activation table, from an end node among the plurality of end nodes registered in the activation table. [9] In-vehicle network system according to one of claims 6 to 8, wherein the update condition includes obtaining update data of the activation table from outside the in-vehicle network system. [10] In-vehicle network system according to any one of claims 1 to 9, wherein the activation table is a plurality of types of activation tables, the plurality of relay nodes which contains a multitude of types of activation tables, and is configured to select and use one of the many types of activation tables according to a vehicle's equipment device status with the vehicle's in-vehicle network system. [11] In-vehicle network system according to any one of claims 1 to 10, wherein the activation message is carried in an Internet Protocol packet and the permitted transmission information is configured to use a lifetime field contained in an Internet Protocol header. [12] A method for transmitting an activation message in a vehicle-internal network system comprising: a plurality of relay nodes, each containing a plurality of communication ports; and a plurality of end nodes, each connected to one of the plurality of relay nodes, wherein each communication port of the plurality of relay nodes is connected to a subordinate node, which is an end node subordinate to at least one of the plurality of relay nodes among the plurality of end nodes, wherein the method comprises: a cause that the multitude of end nodes transmit an activation message containing: Activation request information that identifies an activation cluster, which includes the multitude of end nodes, and Permitted transmission information in which the permitted number of transmissions is set to one (S120, S170); a decrement of a value characterized by the permitted transmission information when the activation message is received via the communication link (S210); a transmission of the activation message if the value of the permitted transmission information after decrementing is greater than zero (S220, S250); a deletion of the activation message if the value of the permitted transmission information is zero after decrementing, and also if a transmission source of the activation message is not the child node (S220, S230, S260); and a rewrite, according to an activation table, of the permitted transmission information of the activation message using the required transmission information, and a transmission of the activation message if the value of the permitted transmission information is zero after decrementing, and also if the transmission source of the activation message is the child node, where the necessary transmission information is linked to a target end node, which is an end node belonging to the activation cluster characterized by the activation request information, among the multitude of end nodes (S220, S230 to S250), and The activation table lists information for each end node, linking node identification information to identify the end node with necessary transmission information, which indicates a transmission count required to reach a target node, which is an end node identified by the node identification information among the multitude of end nodes. [13] End node (23) which is connected to one of a plurality of relay nodes (22) and configures an in-vehicle network system together with the plurality of relay nodes, wherein the end node comprises: an activation unit (233) configured to transition the end node from a sleep state to a wake-up state when a preset activation condition is met; and a state management unit (234: S110 to S170) configured to transmit an activation message containing: Activation request information that identifies an activation cluster to which the end node belongs, and Permitted transmission information in which the permitted number of transmissions is set to one while the end node is in the wake-up state, where the wake-up state is a normal operating state in which a function of the end node can be executed without restriction, and The sleep state is an operating state with low energy consumption in which at least part of the function of the terminal node is restricted. [14] Relay node (22) which has a large number of communication connections, where Each of the relay node's numerous communication ports is connected to a subordinate node, which is an end node that is subordinate to the relay node, among a plurality of end nodes (23) configured to transmit an activation message containing: Activation request information that identifies an activation cluster to which the relay node belongs, and Permitted transmission information that indicates a permitted number of transmissions, or a different relay node that differs from the relay node, wherein the relay node configures an in-vehicle network system together with the multitude of end nodes and the different relay node, and wherein the relay node further comprises: a memory (225) that stores an activation table which lists for each end node information linking node identification information for identifying the end node with required transmission information which indicates a transmission count required to reach a destination node which is an end node identified by the node identification information among the multitude of end nodes; and a rewrite transmission unit (224: S210 to S260) configured to to decrement a value characterized by the permitted transmission information when the activation message is received via the communication link, and to transmit the activation message if the value of the permitted transmission information after decrementing is greater than zero, to delete the activation message if the value of the permitted transmission information is zero after decrementing, and also if a transmission source of the activation message is not the child node, and According to the activation table, rewrite the permitted transmission information of the activation message using the required transmission information and transmit the activation message if the value of the permitted transmission information is zero after decrementing, and also if the transmission source of the activation message is the child node. wherein the necessary transmission information is linked to a target end node, which is an end node belonging to the activation cluster characterized by the activation request information, among the multitude of end nodes.

Images