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

Abstract

An in-vehicle network system comprises: relay nodes (21, 22), each containing communication ports; and end nodes (23), each connected to a relay node. Each communication port is connected to a different relay node or to an end node that is subordinate to the relay nodes. The end nodes contain an activation unit (233) configured to transition from a sleep state to a wake state when an activation condition is met, and to transmit an activation message containing activation request information that identifies an activation cluster, and to transition from the sleep state to the wake state when the activation message is received.The relay nodes contain: a message integration unit (224: S230 to 260, S280 to S320) configured to generate integration activation request information and an integration activation message; and a port transmission unit (224: S330) configured to transmit the integration activation message.

Description

Technical field

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

[0002] In the patent literature 1 described below, a subnetwork technology is known, and the technology selectively controls wake / sleep states or arousal / rest states of each ECU that is connected to an in-vehicle 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 Network Management (NM) messages to control an activation state, and relay nodes forwarding NM messages via broadcast. Ethernet is a registered trademark. This means that each NM message transmitted by any end node is individually relayed to all end nodes. Therefore, a challenge arises from the fact that the volume of NM messages transmitted across the network becomes enormous.

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

[0006] According to one aspect of the present disclosure, a vehicle-internal 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 different relay node among the multiple relay nodes or to an end node that is subordinate to the multiple relay nodes among the multiple end nodes. The end node contains an activation unit. When an activation condition is met in the end node, the activation unit transitions from a sleep state to a wake-up state and transmits an activation message containing activation request information that identifies the activation cluster to which the end node belongs.Furthermore, when the end node receives the activation message containing the activation request information that identifies the activation cluster to which the end node belongs, the end node transitions from the sleep state to the wake-up state. The relay node contains a message integration unit and a connection transmission unit. The message integration unit is configured to merge the activation request information identified in an integration target message (which is the activation message received by a child end node among the multiple end nodes during a predetermined buffer time interval) to generate integration activation request information and to create an integration activation message that is the activation message containing the integration activation request information.The port transmission unit is configured to transmit the integration activation message generated by the message integration unit to one of the multiple communication ports, except for one communication port that has received the integration target message.

[0007] With this configuration, the activation message is not transmitted as is; instead, an integrated activation message is sent, which incorporates multiple activation messages. Therefore, it may be possible to reduce the amount of communication related to the activation message between relay nodes and between relay nodes and the end node. Consequently, it may be possible to reduce the processing load related to duplicate activation messages at the relay node and the end node, and to lower power consumption by reducing unnecessary node activations.

[0008] According to one aspect of the present disclosure, a relay node forms an in-vehicle network system with a different relay node and several end nodes. The relay node contains several communication ports that are connected to the different relay node or to an end node that is subordinate to the relay node among the several end nodes. The relay node contains a message integration unit and a port transmission unit. The message integration unit and the port transmission unit are similar to those described in the in-vehicle network system described above.

[0009] According to such a configuration, it can be used as a relay node that configures the vehicle's in-vehicle network system described above. According to one aspect of the present disclosure, a transmission method for an activation message is applied to a relay node that forms a vehicle's in-vehicle network system with a different relay node and several end nodes. The relay node contains several communication ports that are connected to the different relay node or the end node according to its control.The activation message transmission procedure includes: merging the activation request information identified in the integration target message, which is the activation message received by a subordinate end node among the multiple end nodes during a predetermined buffer time interval to generate the integration activation request information; and generating an integration activation message containing the activation request information. Furthermore, the activation message transmission procedure includes transmitting the generated integration activation message to a communication port other than the one that received the integration target message. The definitions of terms in the activation message transmission procedure are similar to those described in the vehicle-internal network system described above.

[0010] By implementing such a procedure, it may be possible to obtain similar effects to those obtained by the vehicle-internal network system described above.

[0011] 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 by the same reference numerals. 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 a configuration of a Network Management (NM) message. Fig. Figure 3 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 4 is a flowchart showing a state management process performed by an end-effect ECU. Fig. Figure 5 is a flowchart showing a message integration process performed by a zone ECU. Fig. Figure 6 is an explanatory diagram showing an overview of processes in a normal state case and a buffer overload case in a message integration process. Fig. Figure 7 is a block diagram showing a configuration of an in-vehicle network system according to a second embodiment. Fig. Figure 8 is an explanatory diagram showing an initial setting of an NM table in each zone ECU. Fig. Figure 9 is an explanatory diagram showing a setting of the NM table that is updated by adding the final ECU and updating a program. Fig. Figure 10 is a block diagram showing a configuration of an in-vehicle network system according to a third embodiment. Fig. Figure 11 is an explanatory diagram showing a setting of the NM table for each zone ECU. Fig. Figure 12 is an explanatory diagram showing a case in which several pre-prepared NM tables are selected and used.

[0012] The following describes embodiments of the present disclosure with reference to the drawings. 1. First embodiment1-1. Configuration

[0013] An in-vehicle network system 1, which is located in Fig. The device shown in Figure 1 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.

[0014] 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 controlled individually 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 transition itself to the wake-up state, in accordance with the content of the NM message.

[0015] The multiple ECUs 2 are classified into a central ECU 21, multiple zone ECUs 22, and multiple end ECUs 23. The central ECU 21 forms a communication network that includes multiple zone ECUs 22 and redundant routes. The central ECU 21 controls the multiple zone ECUs 22 and implements coordinated control of the entire vehicle.

[0016] The zone ECU 22 is provided for each zone into which an area in the vehicle is divided. Each zone ECU 22 is connected to several end ECUs 23 present in 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.

[0017] In the present embodiment, the vehicle is divided into three zones A to C, and the zone ECUs 22 located in each zone A to C are designated as zone ECU A, zone ECU B, and zone ECU C. It should be noted that the number of zones is not limited to three, and the vehicle can be divided into four zones: the front of the vehicle, the rear of the vehicle, one on each side of the vehicle, and the other on the other side of the vehicle. Furthermore, it can be divided into five or more zones.

[0018] As it is in Fig. As can be seen in Figure 1, the central ECU 21 is connected to zone ECU A and zone ECU C via individual transmission paths 4. Zone ECU A is connected to the central ECU 21 and zone ECU B via individual transmission paths 4. Zone ECU B is connected to zone ECU A and zone ECU C via individual transmission paths 4. Zone ECU C is connected to zone ECU B and the central ECU 21 via individual transmission paths 4. This means that although the central ECU 21 and the multiple zone ECUs 22 are connected in a loop, a portion of the communication interface connected to transmission path 4 is set to a blocking interface, thus preventing the propagation of the communication frame. Fig. Figure 1 shows a case in which the communication port connecting the central ECU 21 and the zone ECU C is set to a blocking port. Communication via the blocking port can be prevented or blocked under normal conditions, and this blocking can be enabled 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 central ECU 21 and the multiple zone ECUs 22 can be described as forming a ring topology.

[0019] Three end-ECUs 23 are connected to zone ECU A in a star configuration 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 to each zone ECU 22 is not limited to the above example and is arbitrary.

[0020] Three end ECUs 23 are connected to zone ECU B in a bus configuration via a transmission line 4. Hereinafter, 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 bus network.

[0021] Zone ECU C 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, the illustration and description of this are omitted here. 1-2. NM message

[0022] An overview of the NM message is provided with reference to Fig. 2. It should be noted that the NM messages must comply with 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.

[0023] The NM message is transmitted and received using an Ethernet frame. The Ethernet frame contains a physical header, an Ethernet header, payload, and a trailer. The physical header is an introduction. The Ethernet header contains a destination address, a source address, and other information. The payload is data, and an NM message is embedded. The trailer is a frame check sequence.

[0024] The NM message contains a NID, a CBV, user data, and a PNI. The NID and CBV are provided by a single byte. The user data consists of variable bytes. Fig. Figure 2 shows a case of 4 bytes. The PNI is a variable byte 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.

[0025] NID stands 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.

[0026] PNI is an abbreviation for Partial Network Information. The PNI is set within 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. 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.

[0027] CBV is an abbreviation 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.

[0028] 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 contains PN request information.

[0029] The PNL bit indicates whether the message is a partial network learning (PNL) message. The AW bit indicates whether the node wake-up is based on a request from within or outside the node. AW stands for active wake-up.

[0030] The NMCSR bit is information that indicates whether a synchronous shutdown (hereinafter referred to as synchronous shutdown) of the entire network is required. NMCSR is an abbreviation for NM Coordinator Sleep Ready.

[0031] The PNSR bit indicates whether the NM message contains a request for synchronous shutdown. PNSR stands for PN shutdown request. The RMR bit indicates whether a transition to the re-message state is required. It is used when various pieces of information are collected using NM messages. RMR stands for re-message request. 1-3. End-ECU

[0032] 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.

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

[0034] 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 transferring its own end-ECU 23 into the idle state or sleep state when required.

[0035] 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 or awakening request) containing the PN request information, the PNI is set to 1. Fig. As shown in Figure 3, 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 allows its own end-ECU 23 to transition from sleep to wake-up. The comparison between the PN request information and the PN filter information can be performed by a logical AND operation of the two pieces of information. In this case, if the logical AND result 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 has occurred that wakes up the own end-ECU 23.

[0036] 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 occurs due to an external or an internal factor.

[0037] 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 sleep mode, or managing its operating state.

[0038] 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. As described in section 4, in S110, the computation unit 234 starts the sleep timer and the timer for periodic transmissions. 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 expire, for example, 1 second. The timer for periodic transmissions is a timer that determines the transmission timing of the NM message. The timer for periodic transmissions is set to expire, for example, 10 milliseconds. The expiration intervals of the sleep timer and the timer for periodic transmissions are not limited to the settings above and can be set as desired.

[0039] In S120, the compute unit 234 transmits an NM message containing the PN filter information of the relevant end ECU 23 as the PN request information. 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 the end ECU 23 itself. For example, the PN cluster to be activated can differ depending on whether the wake-up is caused by an external or an internal factor.

[0040] In S130, the compute unit 234 determines whether the rest or sleep condition is met. One of the rest or sleep conditions includes at least the expiration of the sleep timer. If the compute unit 234 determines that the rest or sleep condition is met, the process ends and the relevant end ECU 23 enters sleep mode. If the compute unit 234 determines that the rest or sleep condition is not met, the process switches to S140.

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

[0042] 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 switches to S170. If the periodic transfer timer has not expired, the process returns to S130.

[0043] In S170, the compute unit 234 restarts the timer for periodic transmissions and transmits the NM message similar to the NM message transmitted in S120, and returns the process to S130.

[0044] This means that in the wake-up state, the end ECU 23 transmits the NM message at regular intervals based on the timer setting for periodic transmissions. Furthermore, if the end ECU 23 does not receive the target NM message for a certain period of time based on the sleep timer setting, the end ECU 23 enters the idle or sleep state. Zones 1-4 ECU

[0045] 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 and a computation unit 224.

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

[0047] The transmission unit 223 has a function for transmitting messages other than the NM message received by the other ECUs 2, according to the destination indicated in the message. The processing unit 224 combines and integrates the PN request information contained in the NM message received by the subordinate end ECU 23 and has a function for transmitting the NM message (hereinafter referred to as the integrated NM message) containing the integrated PN request information to the other ECU 2.

[0048] Similar to the computation unit 234 of the final ECU 23, the computation unit 224 contains a computer that includes a CPU and memory. The computation unit 224 performs at least the message integration process.

[0049] The message integration process, which is executed by the computation unit 224 when the zone ECU 22 is in the wake-up or awakening state, is described with reference to a flowchart by Fig. As described in section 5, in S210, the compute unit 224 starts the sleep timer and the buffer timer. The sleep timer is set in a similar way to the sleep timer used in the state management process of the end ECU 23. The buffer timer determines the buffer time interval of the NM message. For example, the buffer timer is set to expire at a time equal to or longer than the time at which the periodic transmission timer used in the state management process of the end ECU 23 expires.

[0050] In S220, the computation unit 224 determines whether the rest or sleep condition is met. One of the rest or sleep conditions includes at least the expiration time of the sleep or rest timer. If the computation unit 224 determines that the rest or sleep condition is met, it terminates the process and puts the relevant zone ECU 22 into sleep mode. If it determines that the rest or sleep condition is not met, the process switches to S230.

[0051] In S230, the computation unit 224 determines whether the NM message has been received at any of the communication ports of the relevant zone ECU 22. The NM message here contains either an NM message from the subordinate end ECU 23 or an integrated NM message transmitted by the adjacent zone ECU 22. If the computation unit 224 determines that the NM message has been received, the process transitions to S240. If the computation unit 224 determines that the NM message has not been received, the process transitions to S280.

[0052] In S240, the compute unit 224 restarts the sleep timer. In S250, the compute unit 224 determines whether the received NM message is the accumulation target message. The accumulation target message is an NM message received by the subordinate end ECU 23. If the compute unit 224 determines that the received NM message is the accumulation target message, the process transitions to S260. If the compute unit 224 determines that the received NM message is not the accumulation target message, the process transitions to S270. The reasons for excluding NM messages from the other zone ECUs 22 from the accumulation target are as follows. This means that if the integration target contains the NM message from the other zone ECU 22, the integration NM message will ultimately be generated, targeting all nodes for activation.This means that the integrated NM message can be sent back to all end ECUs 23, which are the transmission sources of the NM message, and the effect of preventing unnecessary node activation can be reduced.

[0053] In S260, compute unit 224 buffers the accumulation target message in the receive buffer and returns the process to S220. In S270, compute unit 224 transmits the non-accumulation target message (NM message other than the accumulation target message) to all communication ports of the relevant zone ECU 22 except the one where the non-accumulation target message was received, and returns the process to S220. The non-accumulation target message is the integrated NM message transmitted by another adjacent zone ECU 22.

[0054] In S280, compute unit 224 determines whether the buffer timer has expired, that is, whether the buffer period has ended. If compute unit 224 determines that the buffer timer has not expired, the process switches to S290. If compute unit 224 determines that the buffer timer has expired, the process switches to S300.

[0055] In S290, the compute unit 224 determines whether the receive buffer of the relevant zone ECU 22 is in an overload state. For example, a state in which the receive buffer has less than 10% free space can be defined as an overload state. If the compute unit 224 determines that the receive buffer is in an overload state, the process switches to S300. If the compute unit 224 determines that the receive buffer is not in an overload state, the process returns to S220.

[0056] In S300, compute unit 224 restarts the buffer timer. This means that the current buffer period ends and a new one begins. In S310, compute unit 224 determines whether the accumulated NM message is in the receive buffer. If the accumulated NM message is present, the process switches to S320. If there is no accumulated NM message, the process returns to S220.

[0057] In S320, compute unit 224 generates the integrated NM message based on the NM message that accumulated in the receive buffer during the buffer time interval that ended earlier. Specifically, PN request information is extracted from each NM message stored in the receive buffer. All the extracted PN request information is combined by performing a logical OR operation to generate integrated PN request information. The NM message used to generate the integrated PN request information is deleted from the receive buffer. Then, a new NM message (that is, an integrated NM message) containing the generated integrated PN request information is generated.

[0058] In S330, the computation unit 224 transmits the integrated NM message generated in S320 to all communication ports of the relevant zone ECU 22 except for the communication port through which the NM message, which is the source of the integrated NM message, was received, and returns this to the process in S220.

[0059] The integration of NM messages into the zone ECU 22 is described with reference to Fig. 6 described. Fig. Figure 6 shows a case where the zone ECU B is in Fig. 1. An NM message containing NM request information is received from each of its subordinate end ECUs D to F during the same buffer time interval. In normal cases where the receive buffer is not overloaded, after the buffer time interval expires, the integrated NM message containing integrated NM request information, obtained by performing the logical OR operation on the NM request information, is generated.

[0060] If the overload of the receive buffer is detected during the buffer period, the buffer period is forcibly terminated and the integrated NM message is generated according to the NM messages received at that time by the end ECU D and the end ECU E.

[0061] The generated integrated NM message is transmitted to all communication ports connected to other zone ECUs 22 adjacent to zone ECU B. In contrast, in the conventional technology, which does not use the integrated NM message, the three NM messages received by the end ECUs D to F are transmitted to all communication ports connected to the different zone ECUs 22 adjacent to zone ECU B. This means that in this case, the number of transmitted NM messages is 1 / 3 compared to the conventional technology.

[0062] In addition, Zone ECU B transmits the integrated NM message received from the neighboring Zone ECU 22 (for example, Zone ECU A) to all communication ports of Zone ECU B except for the communication port that received the integrated NM message.

[0063] Zone ECU 22 enters sleep mode if it does not receive either the NM message from the subordinate end ECU 23 or the integrated NM message from the adjacent Zone ECU 22 for a specified period of time based on the sleep timer setting. 1-5. Central ECU

[0064] The central ECU 21 has the same configuration as the zone ECU 22. However, if there is no end ECU 23, which is a direct subordinate part of the central ECU 21, the computation unit 224 can omit the execution of the message integration process. 1-6. Correspondence of concepts

[0065] In the present embodiment, the central ECU 21 and the zone ECU 22 correspond to relay nodes 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 PN cluster 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 processes in S230 to S260 and S280 to S320, which are executed by the computing unit 224, correspond to a message integration unit of the present disclosure, and the process in S330 corresponds to a connection transmission unit of the present disclosure. 1-7. Effects

[0066] According to the first embodiment described in detail above, the following effects are achieved.

[0067] (1a) In the vehicle's internal network system 1, the zone ECU 22 does not simply transmit the NM message received from the subordinate end ECU 23, but instead generates and transmits an integrated NM message that incorporates multiple NM messages received during the buffer period. Accordingly, the vehicle's internal network system 1 makes it possible to reduce the amount of NM message communication, and consequently, it makes it possible to reduce the processing load (for example, unnecessary wake-up) required for NM messages in each ECU 2, and the power consumption.

[0068] (1b) In the vehicle's internal network system 1, when an overload is detected in the receive buffer, the zone ECU 22 forcibly terminates the buffer time period and generates the integrated NM message using the NM message that was buffered at that time. Accordingly, the vehicle's internal network system 1 makes it possible to prevent the receive buffer of the zone ECU 2 from overflowing and also to prevent the NM message from being discarded without being transmitted due to the overflow.

[0069] (1c) In the vehicle-internal network system 1, the connection between the zone ECU 22 and the subordinate end ECU 23 can be either a switched network or a bus network, so that it is possible to implement cooperative network operations between different protocols.

[0070] (1d) In the vehicle's internal 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 internal network system 1 can not only support OTA software downloads and updates, but also wake-up instructions from outside the vehicle's internal network system 1. OTA stands for Over The Air. 2. Second embodiment 2.1. Difference to the first embodiment

[0071] 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.

[0072] The zone ECU 22 of the first embodiment described above outputs the integrated NM message to all communication ports except the receive port. The receive port is the communication port that received the integrated NM message, or the communication port that received the NM message used to generate the integrated NM message. In contrast, a zone ECU 22a of the second embodiment differs from the first embodiment in that it extracts the communication port that needs to be transmitted using the NM table and transmits the integrated NM message only to the extracted communication port. 2-2. Configuration

[0073] As it is in Fig. As can be seen in Figure 7, in a vehicle-internal network system 1a the ECUs 2 are divided into a central ECU 21a, the zone ECU 22a and an end ECU 23.

[0074] The zone ECU 22a contains a memory 225 and an update unit 226 in addition to the transmission unit 221, the receiving unit 222, the transmitting unit 223 and the calculation unit 224. The memory 225 stores the NM table.

[0075] As it is in Fig. As shown in Figure 8, the NM table is a collection of data that is associated with port numbers, zone categories, node identification data, and PN filter information. 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 that belong to the vehicle's in-vehicle network system 1. Fig. In section 8, the entry "End A", which can be seen in the node identification data column, indicates an "End ECU A". The same applies to the following: Fig. 9, Fig. 11 and Fig. 12.

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

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

[0078] The PN filter information is a PNI that identifies which PNC the focused end-ECU 23 belongs to. As it is in Fig. As shown in section 8, the NM table is set for each zone ECU 22. However, apart from the connection number, all zone ECUs 22 have the same content.

[0079] End-ECU A and End-ECU B, identified by the node identification data, belong to Zone A, so the zone category is set to A. Furthermore, since End-ECU D and End-ECU E belong to Zone B, the zone category is set to B.

[0080] Focusing on Zone ECU A, End ECU A, belonging to Zone A, is connected to communication port P1 of Zone ECU A, and End ECU B is connected to communication port P2 of Zone ECU A. End ECU D and End ECU E, belonging to Zone B, are connected to Zone ECU B, which is connected to communication port P4 of Zone ECU A. Accordingly, in Zone ECU A's NM table, the port number assigned to End ECU A is set to P1. The port number assigned to End ECU B is set to P2. The port numbers assigned to End ECU D and End ECU E are both set to P4.

[0081] Focusing on Zone ECU B, End ECU A and End ECU B, belonging to Zone A, are connected to Zone ECU A, and Zone ECU A is connected to the communication port P1 of Zone ECU B. Furthermore, both End ECU D and End ECU E, belonging to Zone B, are connected to the communication port P2 of Zone ECU B. Therefore, in the NM table of Zone ECU B, the port numbers assigned to End ECU A and End ECU B are both set to P1, and the port numbers assigned to End ECU D and End ECU E are both set to P2. 2-3. Connection transmission

[0082] In each zone ECU 22a, the connection forwarding processes in S270 and S330 differ in the message integration process executed by the computation unit 224, which is in Fig. Figure 5 shows a difference from the first embodiment. This means that, in the present embodiment, when the integrated NM message is transmitted to each communication port, the NM table is used to extract the communication port that needs to be transmitted, and the integrated NM message is transmitted to the extracted communication port. Specifically, the logical AND operation of the integrated PN request information identified in the integrated NM message and the PN filter information of all end ECUs 23 identified in the NM message is calculated individually. Then, the end ECU 23 whose calculation result is not zero is extracted, and the integrated NM message is transmitted only to the communication port identified by the port number assigned to the extracted end ECU 23. 2-4. Update unit

[0083] The update unit 226 updates the NM table when a preset update condition is met. The update condition can 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 process performed by the computation unit 224.

[0084] As can be seen through a reference E1 in Fig. Figure 7 describes a case in which the new end-ECU 23 (hereinafter referred to as end-ECU G) is connected to transmission path 4, which is connected to the communication port P2 of zone ECU B. When end-ECU G is connected to transmission path 4 and is activated for any reason, it transmits an NM message containing its own PN filter information as PN request information.

[0085] When the update unit 226 of zone ECU B refers to its NM table and detects that the information of end ECU G is not registered in the NM table, it adds the point of end ECU G to the NM table, as shown in the top row of Fig. 9 can be seen. This added content is also transmitted to the other zone ECUs 22, and each zone ECU adds a point from end ECU G to the NM table. When a point from end ECU G is added to the NM table, in zone ECU B, to which end ECU 23 is added according to its control, the zone category is set to zone B, to which it belongs, and the port number is set to P2, which identifies the communication port that received the NM message.

[0086] The different zone ECU 22a, which has received the update information (i.e., the end ECU G point to be added), updates its NM table in accordance with the update information. Specifically, information is added to the NM table according to the zone category indicated in the update information. This information includes details that link the connection number of the communication port to which zone ECU B is connected, or which zone ECU B can reach, according to the zone category, with the end ECU G point containing the update information.

[0087] As can be seen from reference 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 22a, 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 22a. This updates the NM table in all zone ECUs 22a.

[0088] 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. 2-5. Effects

[0089] The second embodiment, which is described in detail above, provides the effects (1a) to (1c) described in the first embodiment, and additionally the following effect.

[0090] (2a) The zone ECU 22a transmits the integrated NM message only to the communication port that reaches the final ECU 23, which is the activation target, using the NM table. Accordingly, according to the vehicle's internal network system 1a, it is possible to further reduce the amount of NM message communication.

[0091] (2b) According to the vehicle's internal network system 1a, the NM table held by the zone ECU 22a is updated in response to the addition of the end ECU 23 or a program update. Therefore, it is possible to handle system changes flexibly. 3. Third embodiment 3-1. Difference from the second embodiment

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

[0093] In the first embodiment described above, it has been described that there are two zone ECUs 22 that are to be forwarded between the end ECUs 23; however, there can be three or more zone ECUs 22 that are to be forwarded. For example, there can be several hierarchically connected zone ECUs 22 in one zone.

[0094] As it is in Fig. As shown in Figure 10, an in-vehicle network system 1b includes a zone ECU AA, which controls a zone AA that is part of a zone A under zone ECU A, and an end ECU AA under zone ECU AA. The zone ECU AA is connected to the communication port P5 of zone ECU A. Zone ECU A is connected to the communication port P4 of zone ECU AA, and the end ECU AA is connected to the communication port P1 of zone ECU AA. The in-vehicle network system 1b is similar to the in-vehicle network system 1a of the second embodiment, except that the end ECUs 23 are located under zone ECU AA and zone ECU AA (only the end ECU AA is shown in Figure 10). Fig. 10 to be seen) have been added. This means that in Fig. 10 a part of the central ECU 21, the zone ECU C and the end ECU 23 are omitted.

[0095] In the vehicle's internal network system 1b, which is in Fig. As can be seen in Figure 10, the NM tables of zone ECU AA, zone ECU A and zone ECU B are set, as shown in Fig. Figure 11 is shown. In the NM table of zone ECU AA, information about all end ECUs 23 connected to the different zone ECU 22 is assigned to terminal number P4. The zone category of end ECU AA is set to AA, and information about end ECU AA is assigned to terminal number P1.

[0096] In the NM tables of zone ECU A and zone ECU B, the information from end ECU AA has been added to the contents that are in Fig. 8 can be seen. However, the information of the end ECU AA is assigned to connection number P5 in the NM table of zone ECU A and to connection number P1 in the NM table of zone ECU B. 3-2. Operation example

[0097] For example, if the end ECU D transmits the NM message identifying the PN request information containing a PN cluster of the end ECU AA, then the PN request information of the integration message generated in the zone ECU B will naturally include the PN cluster of the end ECU AA. Accordingly, this integrated NM message will be transmitted to at least the communication port P1 in accordance with the information of the end ECU AA in the NM table and will be received by the zone ECU A.

[0098] The integrated NM message transmitted to the zone ECU A is retransmitted to at least the communication port P5 in accordance with the information of the end ECU AA in the NM table of the zone ECU A and received by the zone ECU AA.

[0099] The integrated NM message transmitted to the zone ECU AA is retransmitted to at least the communication port P1 in accordance with the information of the end ECU AA in the NM table of the zone ECU AA and is received by the end ECU AA. 3-3. Effects

[0100] According to the third embodiment, which is described in detail above, in addition to the effects (1a) to (1d) of the first embodiment and the effects (2a) and (2b) of the second embodiment, the following effect is also obtained.

[0101] (3a) In the vehicle-internal network system 1b, the zone ECUs 22 have a hierarchical multi-level connection structure. Therefore, it is possible, for example, to implement a network structure suitable for long vehicles, such as commercial vehicles. 4. Other embodiments

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

[0103] (4a) 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.

[0104] (4b) In the embodiments described above, the network aspect of connecting the zone ECU 22 and the subordinate end ECU 23 involves a combination of a switched network and a bus network. However, the network aspect can be unified into any one of these network aspects.

[0105] (4c) In the embodiments described above, when buffer overload is detected, the buffer time interval is forcibly terminated. This makes it possible to prevent the NM message from being discarded due to the receive buffer overflow. Instead of buffering the NM message, the integrated NM message can be generated as follows to prevent the NM message from being discarded. That is, the NM request information is extracted directly from the received NM message and stored in a working area of ​​memory. Each time a new NM message is received, the contents of the working area memory are updated based on a logical OR operation performed on the NM request information extracted from the received NM message and the NM request information stored in the working area.At the end of the buffer period, the integrated NM message can be generated using the NM request information stored in the workspace and transmitted to each communication port. In this case, a new workspace is required to update the NM request information. However, since it is not necessary to store the entire received NM message during the buffer period, it is possible to prevent the receive buffer from overflowing.

[0106] (4d) In the embodiment above, each zone ECU 22a uses an NM table. On the other hand, as described in Fig.As shown in Figure 12, for example, several types of NM tables can be prepared in advance, depending on the vehicle's equipment status with the in-vehicle network system 1a, 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 in-vehicle network system 1a, and the NM table can be selected automatically.

[0107] (4e) 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 of these described in the present 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.

[0108] (4f) 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 the 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. Furthermore, at least part of the configuration of the embodiments described above may be added to or replaced by the configuration of another embodiment described above.

[0109] (4g) In addition to the vehicle-internal network system described above, the present disclosure may also be implemented in various forms, such as the zone ECU 22 and the end ECU 23, which are components of the vehicle-internal network system, a program to cause a computer to function as the zone ECU 22 or the end ECU 23, a non-volatile tangible storage medium, such as a semiconductor memory, on which this program is stored, and a method for transmitting an 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 multitude of relay nodes (21, 22), each containing multiple communication ports (Pi); and a plurality of end nodes (23) each connected to one of the plurality of relay nodes, wherein Each communication port of the multitude of relay nodes is connected to a different relay node within the multitude of relay nodes or to an end node that is subordinate to the multitude of relay nodes within the multitude of end nodes, and the multitude of end nodes contains an activation unit (233) that is configured to to transition from a sleep state to a wake-up state when an activation condition is met within at least one of the plurality of end nodes, and to transmit an activation message containing activation request information that identifies an activation cluster to which the plurality of end nodes belongs, and to transition from the sleep state to the wake-up state when the activation message is received, which contains the activation request information that identifies the activation cluster to which the multitude of end nodes belongs, the multitude of relay nodes includes: a message integration unit (224: S230 to 260, S280 to S320) that is configured to to combine the activation request information, which is identified in an integration target message, that is the activation message received by a child end node among the multitude of end nodes during a predetermined buffer time period, in order to generate integration activation request information, and to generate an integration activation message, which is the activation message containing the integration activation request information; and a connection transmission unit (224: S330) that is configured to transmit the integration activation message generated by the message integration unit to a communication port among the multitude of communication ports other than a communication port that has received the integration target message. [2] In-vehicle network system according to claim 1, wherein each relay node contains an activation table, the activation table for all of the multitude of end nodes contains: Information for identifying each terminal node, Activation filter information for listing the activation cluster to which the multitude of end nodes belongs, Information for identifying the multitude of relay nodes connected to the multitude of end nodes, and Information that characterizes the multitude of communication connections, each individually reaching a multitude of end nodes, and the connection transmission unit is configured to to compare the activation request information identified in the integration activation message with the activation filter information identified in the activation table in order to identify, among the multitude of end nodes, an end node that is identified by the activation request information, and to transmit the integration activation message to all communication links that reach the identified end node. [3] In-vehicle network system according to claim 2, further comprising an update unit (226) configured to update the activation table when a predetermined update condition is met. [4] In-vehicle network system according to claim 3, 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. [5] In-vehicle network system according to claim 3 or claim 4, wherein the update condition includes receiving an update instruction, which characterizes update data of the activation table, from an end node among the plurality of end nodes that is registered in the activation table. [6] In-vehicle network system according to one of claims 3 to 5, wherein the update condition includes obtaining update data of the activation table from outside the in-vehicle network system. [7] In-vehicle network system according to any one of claims 2 to 6, wherein the activation table contains a plurality of types of activation tables, the plurality of relay nodes which contains a variety of activation table types and is configured to select and use one of the many types of activation tables according to a vehicle's equipment status with the vehicle's in-vehicle network system. [8] Relay node forming a vehicle-internal network system with a distinct relay node (22) and a plurality of end nodes (23), wherein the relay node comprises: a multitude of communication ports (Pi) connected to the different relay node or an end node subordinate to the relay node among the multitude of end nodes; a message integration unit (224: S230 to 260, S280 to S320) that is configured to To merge activation request information that is tagged in an integration target message, which is an activation message received by a child end node among the multitude of end nodes during a predetermined buffer time interval, in order to generate integration activation request information, and to generate an integration activation message containing the activation request information; and a connection transmission unit (224: S330) configured to transmit the integration activation message generated by the message integration unit to a communication port among the multitude of communication ports other than a communication port in which the integration target message is received, where The activation request information is information that identifies an activation cluster to which an end node, which is a transmission source of the activation message, belongs among the multitude of end nodes, and The activation message is transmitted from at least one end node among the plurality of end nodes when a predetermined activation condition is met in the at least one end node, and a receiving end node among the plurality of end nodes transitions from a sleep state to a wake-up state when the activation cluster to which the receiving end node that received the activation message belongs is identified in the activation request information contained in the activation message. [9] A method of transmitting an activation message in a relay node forming an in-vehicle network system with a distinct relay node (22) and a plurality of end nodes (23), wherein the relay node has a plurality of communication ports (Pi) connected to the distinct relay node or to an end node subordinate to the relay node among the plurality of end nodes, wherein the method comprises: a merging of activation request information that is tagged in an integration target message, which is the activation message received by a child end node among the multitude of end nodes during a predetermined buffer time interval to generate integration activation request information, and a generation of an integration activation message containing the activation request information (S230 to 260, S280 to S320); and a transmission of the generated integration activation message to a communication port among the multitude of communication ports other than a communication port that has received the integration target message (S330), where The activation request information is information that identifies an activation cluster to which an end node, which is a transmission source of the activation message, belongs among the multitude of end nodes, and the activation message is transmitted from at least one end node among the plurality of end nodes when a predetermined activation condition is met in the at least one end node, and the method further includes causing a receiving end node among the plurality of end nodes to transition from a sleep state to a wake-up state when the activation cluster to which the receiving end node that received the activation message belongs is identified in the activation request information contained in the activation message.

Images