In-vehicle network system, relay node, and start-up message transmission method

Abstract

The invention provides an in-vehicle network system, a relay node, and a method for transmitting an activation message, which suppress the traffic of a message related to the control of the activation state of a local network. During the determined buffer period, a calculation unit (224) of the area ECU (22) combines startup request information indicated by a message to be integrated, which is a startup message received from a subordinate end node, to generate integrated startup request information, and generates an integrated startup message, which is a startup message including the integrated startup request information. The calculation unit (224) transmits the generated integration start message to a communication port other than the communication port that has received the integration target message.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to an in-vehicle network system, a relay node, and a transmission method of a start-up message. BACKGROUND

[0002] In the following Patent Literature 1, a local network technology of selectively controlling wake / sleep states of each ECU connected to an in-vehicle network system is known.

[0003] PRIOR ART DOCUMENTS

[0004] PATENT LITERATURE

[0005] Patent Literature 1: Japanese Patent Application Publication No. 2021-011228 SUMMARY

[0006] In the in-vehicle Ethernet network standard AUTOSAR R22-11: Specification of UDP Network Management, it is prescribed that an end node periodically transmits an NM message that controls a start-up state, and a relay node transmits the NM message by broadcasting. Ethernet is a registered trademark. That is, the NM messages transmitted from each end node are individually transmitted to all end nodes. Thus, there is a problem that the communication volume of the NM messages transmitted within the network becomes large.

[0007] One aspect of the present disclosure provides a technology of suppressing the communication volume of messages related to control of a start-up state of a local network.

[0008] The vehicle-mounted network system of one embodiment of the present disclosure includes a plurality of relay nodes and a plurality of end nodes. The relay nodes each include a plurality of communication ports. The end nodes are each connected to one of the plurality of relay nodes. The plurality of communication ports of the relay nodes are each connected to another relay node or an end node subordinate to the relay node. The end nodes include an activation unit. The activation unit is configured to transition from a sleep state to a wake-up state and transmit an activation message including activation request information indicating an activation cluster to which the end node belongs, when an activation condition inside the end node is satisfied. In addition, the end nodes are configured to transition from the sleep state to the wake-up state when an activation message including activation request information indicating the activation cluster to which the end node belongs is received. The relay nodes include a message integration unit and a port transmission unit. The message integration unit is configured to generate integrated activation request information by integrating activation request information indicated by activation messages received from subordinate end nodes, i.e., integration target messages, in a determined buffer period, and generate an integrated activation message including the integrated activation request information. The port transmission unit is configured to transmit the integrated activation message generated by the message integration unit to a communication port other than the communication port that received the integration target message.

[0009] According to such a configuration, instead of transmitting activation messages as they are, an integrated activation message obtained by integrating a plurality of activation messages is transmitted, so that the amount of communication related to activation messages between relay nodes and between relay nodes and end nodes can be reduced. As a result, at the relay nodes and the end nodes, the processing load related to repeated activation messages can be reduced, and energy saving can be achieved by suppressing unnecessary node activation.

[0010] The relay node of one embodiment of the present disclosure forms a vehicle-mounted network system with other relay nodes and a plurality of end nodes, and includes a plurality of communication ports connected to other relay nodes or end nodes subordinate to the relay node. The relay node includes a message integration unit and a port transmission unit. The message integration unit and the port transmission unit are the same as described in the vehicle-mounted network system described above.

[0011] According to such a configuration, the relay node can be used as a relay node that constitutes the vehicle-mounted network system described above.

[0012] The transmission method of the start message of one embodiment of the present disclosure is applied to a relay node that forms a vehicle-mounted network system together with other relay nodes and a plurality of end nodes. The relay node has a plurality of communication ports that are connected to other relay nodes or end nodes subordinate to itself. The transmission method of the start message includes: generating integrated start request information by merging start request information indicated by a start message, which is an integration object message, received from a subordinate end node, during a decided buffer period, and generating an integrated start message that includes the integrated start request information. In addition, the transmission method of the start message includes: transmitting the generated integrated start message to a communication port other than the communication port that received the integration object message. The definitions of the terms in the transmission method of the start message are the same as the descriptions in the aforementioned vehicle-mounted network system.

[0013] By implementing such a method, the same effects as those of the aforementioned vehicle-mounted network system can be obtained. BRIEF DESCRIPTION OF DRAWINGS

[0014] Figure 1 is a block diagram that shows the configuration of the vehicle-mounted network system of the first embodiment.

[0015] Figure 2 is an explanatory diagram that shows the configuration of the NM message.

[0016] Figure 3 is an explanatory diagram that shows the outline of the start processing performed by the start unit of the end ECU at the time of NM message reception.

[0017] Figure 4 is a flowchart of the state management processing performed by the end ECU.

[0018] Figure 5 is a flowchart that shows the message integration processing performed by the region ECU.

[0019] Figure 6 is an explanatory diagram that shows the outline of the processing in the message integration processing at normal times and at the time of buffer congestion.

[0020] Figure 7 is a block diagram that shows the configuration of the vehicle-mounted network system of the second embodiment.

[0021] Figure 8 is an explanatory diagram that shows the initial setting of the NM table in each region ECU.

[0022] Figure 9 is an explanatory diagram that shows the setting of the NM table that is updated due to the addition of an end ECU and the update of a program.

[0023] Figure 10 is a block diagram that shows the configuration of the vehicle-mounted network system of the third embodiment.

[0024] Figure 11 This is an explanatory diagram showing the NM table settings for each region's ECU.

[0025] Figure 12 This is an illustration of the scenario where multiple pre-prepared NM tables are used. Detailed Implementation

[0026] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0027] [1. First Implementation Method]

[0028] [1-1. Composition]

[0029] exist Figure 1 In the in-vehicle network system 1 shown, multiple electronic control units (hereinafter referred to as ECUs) 2 mounted on the vehicle are interconnected via multiple transmission paths 4 that communicate using the Ethernet protocol. Ethernet is a registered trademark.

[0030] ECU2 has a normal operating state, namely the wake-up state, in which it can perform its functions without restriction, and a low-power operating state, namely the sleep state, in which at least some of its functions are restricted. The operating state of ECU2 is controlled individually using NM messages. NM is an abbreviation for Network Management. That is, the vehicle network system 1 is configured as a local area network (hereinafter referred to as PN). In addition, ECU2 has at least the function of receiving NM messages in the sleep state and waking up the ECU2 according to the content of the NM messages.

[0031] The multiple ECUs 2 are classified as central ECU 21, multiple regional ECUs 22, and multiple terminal ECUs 23.

[0032] The central ECU 21 and multiple regional ECUs 22 form a communication network with redundant paths. The central ECU 21 coordinates the multiple regional ECUs 22 to achieve overall vehicle coordinated control.

[0033] Each regional ECU 22 is positioned within a region defined by dividing the vehicle into zones. Each regional ECU 22 is connected to multiple terminal ECUs 23 located within that region via a separate transmission path 4. The regional ECU 22 coordinates the subordinate terminal ECUs 23 directly connected to it to achieve coordinated control within the region.

[0034] In this embodiment, the vehicle is divided into three regions A to C, and the region ECUs 22 configured in each region A to C are referred to as region ECU_A, region ECU_B, and region ECU_C. Furthermore, the number of regions is not limited to three; it can also be divided into four regions: the front of the vehicle, the rear of the vehicle, one side of the vehicle, and the other side of the vehicle. Alternatively, it can be divided into five or more regions.

[0035] like Figure 1 As shown, the central ECU 21 is connected to area ECU_A and area ECU_C via separate transmission paths 4. Area ECU_A is connected to the central ECU 21 and area ECU_B via separate transmission paths 4. Area ECU_B is connected to area ECU_A and area ECU_C via separate transmission paths 4. Area ECU_C is connected to area ECU_B and the central ECU 21 via separate transmission paths 4. In other words, the central ECU 21 and multiple area ECUs 22 are connected in a ring, and the circular forwarding of communication frames is suppressed by setting a portion of the communication ports connected to transmission path 4 as blocking ports. Figure 1 The diagram illustrates the case where the communication port connecting the central ECU 21 and the regional ECU_C is configured as a blocking port. The blocking port can normally disable communication and can be unblocked in case of ECU 2 or transmission path 4 failures. In other words, the blocking port can be used to ensure the redundancy of the communication path. Furthermore, the central ECU 21 and the multiple regional ECUs 22 can be considered to form a ring topology.

[0036] Three terminal ECUs 23 are connected to region ECU_A in a star configuration via separate transmission paths 4. Hereinafter, the terminal ECUs 23 connected to region ECU_A will also be referred to as terminal ECU_A, terminal ECU_B, and terminal ECU_C. Region ECU_A and terminal ECUs_A through C form a switched network (hereinafter referred to as a switched NW). Furthermore, the number of terminal ECUs 23 connected as subordinates to each region ECU 22 is not limited to the aforementioned example and is arbitrary.

[0037] Three terminal ECUs 23 are connected to the region ECU_B in a bus configuration via a transmission path 4. Hereinafter, the terminal ECUs 23 connected to the region ECU_B will also be referred to as terminal ECU_D, terminal ECU_E, and terminal ECU_F. That is, the region ECU_B and the terminal ECUs_D to F form bus NW.

[0038] A wireless device 3 is connected to the area ECU_C to communicate with servers or other devices on a wide area wireless network. Additionally, more than one end ECU 23 can be connected to the area ECU_C, but for simplicity, illustrations and explanations are omitted here.

[0039] [1-2. NM News]

[0040] use Figure 2 A summary of the NM message is provided. Furthermore, the NM message is based on AUTOSAR R22-11: Specification of UDP Network Management. However, the specification is not limited to R22-11; it could also be a subsequent specification such as R23-11.

[0041] Use Ethernet frames to send and receive NM messages.

[0042] An Ethernet frame consists of a physical layer header, an Ethernet header, a payload, and a trailer. The physical layer header is the preamble. The Ethernet header contains the destination address, source address, etc. The payload is the data, carrying an NM (Notification Messaging) message. The trailer is the frame check sequence number.

[0043] The NM message contains NID, CBV, user data, and PNI. NID and CBV each consist of 1 byte. User data is a variable-length byte. Figure 2 The example shown is a 4-byte case. PNI is a variable-byte number. Figure 2 This illustrates the 2-byte case. The positions of NID and CBV in the NM message can also be reversed.

[0044] NID is an abbreviation for Node Identifier, which is information used to identify the node (i.e., the end ECU23) that becomes the source of the NM message. User data is a region where users can set arbitrary data.

[0045] PNI is an abbreviation for Partial Network Information. The PNI is set in the user data area and is represented by multiple bits. Each bit constituting the PNI is called a PNC bit. PNC is an abbreviation for Partial Network Cluster. A PNC represents the group (hereinafter referred to as the PN cluster) of the end ECU23 that requires simultaneous startup by the node (i.e., ECU2). Different PN clusters are assigned to each PNC bit. A PNC bit set to 1 indicates that a factor has been generated that will wake up the PN cluster corresponding to that PNC bit. A PNC bit set to 0 indicates that no factor has been generated that will wake up the PN cluster corresponding to that PNC bit. Hereinafter, the PNI carried in the NM message to wake up ECU2 will be referred to as the PN request information.

[0046] CBV is an abbreviation for Control Bit Vector, which represents the information indicated by the NM message. CBV contains PNI, PNL, AW, NMCSR, PNSR, and RMR bits.

[0047] The PNI bit indicates whether or not it corresponds to the local network management (hereinafter referred to as the local NM). In this embodiment, the PNI bit is fixed at a value indicating correspondence with the NM. In the case of correspondence with the NM, the PN request information is included in the user data of the NM message.

[0048] The PNL bit indicates whether the NM message is for PNC learning. PNL is an abbreviation for Partial Network Learning. The AW bit indicates whether the node wake-up is based on a request from within the node or a request from outside the node. AW is an abbreviation for Active Wakeup.

[0049] The NMCSR bit indicates whether a synchronization shutdown (hereinafter referred to as synchronization shutdown) has been requested for the entire network. NMCSR is an abbreviation for NM Coordinator Sleep Ready.

[0050] The PNSR bit indicates whether the NM message contains a synchronous shutdown request. PNSR is an abbreviation for PN ShutdownRequest (Local Network Shutdown Request).

[0051] The RMR bit indicates whether a request has been made to transition to a repeat message state. It is used to gather various information using NM messages, etc. RMR is an abbreviation for Repeat Message Request.

[0052] [1-3. Terminal ECU]

[0053] like Figure 1 As shown, the terminal ECU 23 includes a transmitting unit 231, a receiving unit 232, a starting unit 233, and a computing unit 234.

[0054] The transmitting unit 231 has the function of transmitting messages generated by the terminal ECU 23.

[0055] The receiving unit 232 has the function of receiving messages from other ECUs 2.

[0056] The start-up unit 233 has the function of turning the terminal ECU 23 into a wake-up state based on the NM message received by the receiving unit 232 when the terminal ECU 23 is in a sleep state.

[0057] The arithmetic unit 234 has at least the function of monitoring the transmission and reception of NM messages during the period when the terminal ECU 23 is in the awake state, and causing the terminal ECU 23 to switch to a sleep state as needed.

[0058] The terminal ECU23 maintains all PNC bits corresponding to the PN cluster to which this terminal ECU23 belongs set to 1 in the PNI (hereinafter referred to as PN filtering information).

[0059] Upon receiving an NM message (hereinafter referred to as a wake-up request) containing PN request information, the startup unit 233, if... Figure 3 As shown, the PN request information represented by each bit of the wake-up request is compared with the PN filtering information possessed by this terminal ECU 23. Even if only one bit matches, the start-up unit 233 causes this terminal ECU 23 to transition from a sleep state to a wake-up state. The comparison between the PN request information and the PN filtering information can also be performed by performing a logical AND operation on both. In this case, if the result of the logical AND is not zero, it is determined that the PN request information indicates the PNC to which this terminal ECU 23 belongs; in other words, a factor has been generated that would wake up this terminal ECU 23.

[0060] The startup unit 233 can be configured in hardware. When a startup condition is met, the startup unit 233 transitions the terminal ECU 23 from a sleep state to a wake-up state. The startup condition includes at least a wake-up factor (hereinafter referred to as an external factor) extracted based on a received NM message. Alternatively, the startup condition may also include a wake-up factor generated at the terminal ECU 23 (hereinafter referred to as an internal factor). The startup unit 233 may also have the function of notifying the arithmetic unit 234 of information indicating whether the transition from the sleep state to the wake-up state was caused by an external factor or an internal factor.

[0061] The arithmetic unit 234 is configured as a computer including a CPU and memory. When the terminal ECU 23 enters the wake-up state, the arithmetic unit 234 performs at least state management processing. State management processing is the process of managing whether the terminal ECU 23 maintains the wake-up state or enters the sleep state.

[0062] use Figure 4 The flowchart illustrates the state management processing performed by the arithmetic unit 234 of the terminal ECU 23.

[0063] In S110, the arithmetic unit 234 starts the sleep timer and the periodic transmission timer. The sleep timer is a timer related to the sleep conditions used when the terminal ECU 23 transitions from a wake-up state to a sleep state. The sleep timer is, for example, set to a timeout of 1 second. The periodic transmission timer is a timer that determines the timing of sending NM messages. The periodic transmission timer is, for example, set to a timeout of 10 ms. The timeout periods of the sleep timer and the periodic transmission timer are not limited to the above settings and can be arbitrarily set.

[0064] In S120, the arithmetic unit 234 sends an NM message containing PN filtering information possessed by the local ECU 23 as PN request information. Alternatively, instead of sending the PN filtering information as is, a portion of the PN filtering information can be used as the PN request information depending on the state of the local ECU 23. For example, the PN cluster targeted for startup can vary depending on whether the wake-up is caused by external or internal factors.

[0065] In S130, the arithmetic unit 234 determines whether the sleep conditions are met. One of the sleep conditions includes at least a sleep timer timeout. If the arithmetic unit 234 determines that the sleep conditions are met, it terminates the process and puts the terminal ECU 23 into a sleep state; if the arithmetic unit determines that the sleep conditions are not met, it proceeds to S140.

[0066] In S140, the arithmetic unit 234 determines whether it has received an NM message (hereinafter referred to as an object NM message) containing PN startup information with the PNC bit set to 1 corresponding to the PN cluster to which this terminal ECU 23 belongs. If the arithmetic unit 234 determines that an object NM message has been received, it proceeds to S150; if it determines that no object NM message has been received, it proceeds to S160.

[0067] In S150, the arithmetic unit 234 restarts the sleep timer and returns the processing to S130.

[0068] In S160, the arithmetic unit 234 determines whether the periodic transmission timer has expired. If the periodic transmission timer has expired, the process proceeds to S170. If the periodic transmission timer has not expired, the process returns to S130.

[0069] In S170, the arithmetic unit 234 restarts the periodic transmission timer and sends the same NM message as the NM message sent in the previous S120, and returns the processing to S130.

[0070] In other words, in the wake-up state, the terminal ECU 23 sends an NM message at regular intervals based on a set value of a periodic transmission timer. Furthermore, if the terminal ECU 23 does not receive an NM message within a certain period based on a set value of a sleep timer, it transitions to a sleep state.

[0071] [1-4. Regional ECU]

[0072] The ECU22 in multiple regions is constructed in the same way.

[0073] like Figure 1 As shown, the regional ECU22 includes a transmitting unit 221, a receiving unit 222, a transmission unit 223, and a processing unit 224.

[0074] The transmitting unit 221 has the function of transmitting messages via any one of the multiple communication ports of the ECU 22 in this region.

[0075] The receiving unit 222 has the function of receiving messages from other ECUs 2 via any one of the multiple communication ports of the ECU 22 in this region.

[0076] The transmission unit 223 has the function of transmitting messages other than NM messages received from other ECU2 according to the destination indicated by the message.

[0077] The arithmetic unit 224 has the function of merging the PN request information contained in the NM message received from the subordinate terminal ECU 23, and transmitting the NM message containing the merged PN request information (hereinafter referred to as the merged NM message) to other ECUs 2.

[0078] Similar to the arithmetic unit 234 of the terminal ECU 23, the arithmetic unit 224 is configured as a computer including a CPU and memory. The arithmetic unit 224 performs at least message integration processing.

[0079] use Figure 5 The flowchart illustrates the message integration processing performed by the arithmetic unit 224 when the region ECU22 is in the wake-up state.

[0080] In S210, the arithmetic unit 224 starts the sleep timer and the buffer timer. The sleep timer is set in the same way as the sleep timer used in the status management process of the terminal ECU 23. The buffer timer is a timer that determines the buffering period of the NM message. The buffer timer is set, for example, to a timeout period that is longer than the timeout period of the periodic transmission timer used in the status management process of the terminal ECU 23.

[0081] In S220, the arithmetic unit 224 determines whether the sleep conditions are met. One of the sleep conditions includes at least a sleep timer timeout. If the arithmetic unit 224 determines that the sleep conditions are met, it terminates the process and puts the ECU 22 in this region into a sleep state; if the arithmetic unit determines that the sleep conditions are not met, it proceeds to S230.

[0082] In S230, the arithmetic unit 224 determines whether an NM message has been received through a communication port of the local ECU 22. This NM message may include an NM message from a subordinate terminal ECU 23 or a consolidated NM message transmitted from an adjacent local ECU 22. If the arithmetic unit 224 determines that an NM message has been received, it proceeds to S240; otherwise, it proceeds to S280.

[0083] In S240, the arithmetic unit 224 restarts the sleep timer.

[0084] In S250, the arithmetic unit 224 determines whether the received NM message is an accumulation target message. An accumulation target message is an NM message received from a subordinate end ECU 23. If the arithmetic unit 224 determines that the received NM message is an accumulation target message, it proceeds to S260; otherwise, it proceeds to S270. The reason for excluding NM messages from other region ECUs 22 from the accumulation target is as follows: If NM messages from other region ECUs 22 are included in the integration target, an integrated NM message will ultimately be generated that targets all nodes. In other words, this is because all end ECUs 23 that are the sources of the NM message will also receive the integrated NM message, potentially reducing the effectiveness of suppressing unnecessary node startups.

[0085] In S260, the arithmetic unit 224 buffers the accumulated object message in the receiving buffer and processes it before returning to S220.

[0086] In S270, the arithmetic unit 224 transmits NM messages that are not accumulation target messages (i.e., non-accumulation target messages) to all communication ports of the local ECU 22 except for the communication port that received the non-accumulation target message, and returns the processing to S220. Furthermore, non-accumulation target messages are integrated NM messages transmitted from adjacent ECU 22s in other regions.

[0087] In S280, the arithmetic unit 224 determines whether the buffer timer has timed out, that is, whether the buffer period has ended. If the arithmetic unit 224 determines that the buffer timer has not timed out, the process proceeds to S290; if the arithmetic unit 224 determines that the buffer timer has timed out, the process proceeds to S300.

[0088] In S290, the arithmetic unit 224 determines whether the receive buffer of the ECU 22 in this region is in a congested state. For example, a state where the idle time of the receive buffer is less than 10% can be defined as a congested state. If the arithmetic unit 224 determines that the receive buffer is in a congested state, the processing proceeds to S300; if the arithmetic unit 224 determines that the receive buffer is not in a congested state, the processing returns to S220.

[0089] In S300, the arithmetic unit 224 restarts the buffer timer. That is, it ends the current buffer period and begins a new buffer period.

[0090] In S310, the arithmetic unit 224 determines whether there is an accumulated NM message in the receive buffer. If there is an accumulated NM message, the process proceeds to S320. If there is no accumulated NM message, the process returns to S220.

[0091] In S320, the arithmetic unit 224 generates an integrated NM message based on the NM messages accumulated in the receive buffer during the previously ended buffering period. Specifically, PN request information is extracted from each NM message stored in the receive buffer, and all extracted PN request information is combined by performing a logical OR operation to generate integrated PN request information. Furthermore, the NM messages used in generating the integrated PN request information are deleted from the receive buffer. Then, a new NM message (i.e., the integrated NM message) containing the generated integrated PN request information is generated.

[0092] In S330, the arithmetic unit 224 transmits the integrated NM message generated in S320 to all communication ports of the ECU22 in this region except for the communication port that received the NM message that became the source of the integrated NM message, and returns the processing to S220.

[0093] use Figure 6 The integration of NM messages in region ECU22 is explained. Figure 6 In, it is shown Figure 1 In the case where region ECU_B receives NM messages containing NM request information from its subordinate end ECUs_D to F respectively during the same buffer period, under normal circumstances when the receive buffer is not congested, after the buffer period expires, a combined NM message containing combined NM request information obtained by performing a logical OR operation on the NM request information is generated.

[0094] If congestion of the receive buffer is detected during the buffering period, the buffering period is forcibly terminated, and an integrated NM message is generated according to the NM messages received from the end ECU_D and end ECU_E at that time.

[0095] The generated integrated NM message is transmitted to all communication ports connected to other area ECUs 22 adjacent to area ECU_B. In contrast, in the prior art without using integrated NM messages, the three NM messages received from end ECUs_D to F are transmitted to all communication ports connected to other area ECUs 22 adjacent to area ECU_B. That is, in this case, the number of NM messages transmitted is 1 / 3 compared to the prior art.

[0096] In addition, the integrated NM message received from the adjacent region ECU22 (e.g., region ECU_A) will be transmitted to all communication ports of region ECU_B other than the communication port that received the integrated NM message.

[0097] If a regional ECU 22 does not receive either an NM message from its subordinate end ECU 23 or an integrated NM message from its neighboring regional ECU 22 for a certain period based on a sleep timer setting, it will enter a sleep state.

[0098] [1-5. Central ECU]

[0099] The central ECU 21 is configured similarly to the regional ECU 22. In the absence of a terminal ECU 23 that is a direct subordinate of the central ECU 21, the execution of message integration processing in the arithmetic unit 224 can be omitted.

[0100] [1-6. Correspondence of Terms]

[0101] In this embodiment, the central ECU 21 and regional ECU 22 are equivalent to the relay nodes of this disclosure, and the terminal ECU 23 is equivalent to the terminal nodes of this disclosure. In this embodiment, the PN request information is equivalent to the startup request information of this disclosure, the PN filtering information is equivalent to the startup filtering information of this disclosure, and the PN cluster is equivalent to the startup cluster of this disclosure. In this embodiment, the NM message is equivalent to the startup message of this disclosure, and the NM table is equivalent to the startup table of this disclosure. In this embodiment, the processing of S230-S260 and S280-S320 executed by the arithmetic unit 224 is equivalent to the message integration unit of this disclosure, and the processing of S330 is equivalent to the port transmission unit of this disclosure.

[0102] [1-7. Effects]

[0103] According to the first embodiment described above, the following effects are achieved.

[0104] (1a) In the vehicle network system 1, the regional ECU 22 does not transmit the NM messages received from its subordinate end ECU 23 as is, but instead generates and transmits an integrated NM message that combines multiple NM messages received during the buffering period. Therefore, according to the vehicle network system 1, the amount of NM message communication can be reduced, which in turn reduces the processing load (e.g., unnecessary wake-ups) and power consumption required for NM messages in each ECU 2.

[0105] (1b) In the vehicle network system 1, when the region ECU 22 detects congestion in the receive buffer, it forcibly terminates the buffering period and uses the NM message buffered at that time to generate an integrated NM message. Therefore, according to the vehicle network system 1, it is possible to suppress the overflow of the receive buffer of the region ECU 2, and thus it is possible to prevent the NM message from being discarded due to overflow.

[0106] (1c) In the vehicle network system 1, the connection between the regional ECU 22 and the subordinate terminal ECU 23 can be achieved through either the switched NW or the bus NW, thus enabling NM operations that are coordinated between different protocols.

[0107] (1d) In the vehicle network system 1, the wireless device 3 is connected to the network via the area ECU 22, forming an SDV. SDV is an abbreviation for Software Defined Vehicle. Therefore, according to the vehicle network system 1, it can not only handle OTA-based software downloads and upgrades, but also handle wake-up instructions from outside the vehicle network system 1. OTA is an abbreviation for Over The Air.

[0108] [2. Second Implementation]

[0109] [2-1. Differences from the first embodiment]

[0110] Regarding the second embodiment, since its basic structure is the same as that of the first embodiment, the differences will be described below. Furthermore, the same reference numerals as in the first embodiment denote the same structures; please refer to the previous description.

[0111] In the first embodiment, the region ECU 22 outputs the integrated NM message to all communication ports except the receiving port. The receiving port refers to the communication port that receives the integrated NM message or the communication port that receives the NM message used in the generation of the integrated NM message. In contrast, the region ECU 22a in the second embodiment uses an NM table to extract the communication ports that need to be transmitted, and limits the transmission of the integrated NM message to the extracted communication ports, which differs from the first embodiment.

[0112] [2-2. Composition]

[0113] like Figure 7 As shown, in the vehicle network system 1a, ECU2 is divided into central ECU21a, regional ECU22a, and terminal ECU23.

[0114] In addition to the transmitting unit 221, receiving unit 222, transmission unit 223, and computing unit 224, the area ECU 22a also has a storage unit 225 and an update unit 226.

[0115] The NM table is stored in storage unit 225.

[0116] like Figure 8 As shown, the NM table is a collection of data obtained by establishing associations between port numbers, region categories, node identification data, and PN filtering information.

[0117] Node identification data uniquely identifies the terminal ECU 23. Node identification data can use any one of the following: node ID, MAC address, or IP address. The NM table lists the node identification data for all terminal ECUs 23 belonging to the vehicle network system 1. Figure 8 In the node identification data section, the entry "End A" indicates "End ECU_A". Below, in... Figure 9 , Figure 11 and Figure 12 The same applies to China.

[0118] The region category indicates which region (i.e. which region ECU22a) the terminal ECU23 identified through node identification data belongs to (i.e., which region ECU22a it is connected to).

[0119] The port number is information used to identify the communication port connected to the terminal ECU 23 of interest or to the communication port of the area ECU 22a connected to the terminal ECU 23. In other words, it indicates which communication port can be used to reach the terminal ECU 23 of interest.

[0120] PN filtering information indicates which PNC the terminal ECU23 of interest belongs to.

[0121] like Figure 8 As shown, the NM table is set for each region ECU22, and items other than the port number are the same in all regions of ECU22.

[0122] Terminal ECU_A and terminal ECU_B, identified using node identification data, belong to region A, therefore their region category is set to A. Additionally, terminal ECU_D and terminal ECU_E belong to region B, therefore their region category is set to B.

[0123] When focusing on region ECU_A, terminal ECU_A belonging to region A is connected to communication port P1 of region ECU_A, and terminal ECU_B is connected to communication port P2 of region ECU_A. Terminal ECU_D and terminal ECU_E belonging to region B are connected to region ECU_B, and region ECU_B is connected to communication port P4 of region ECU_A. Therefore, in the NM table of region ECU_A, the port number associated with terminal ECU_A is set to P1. The port number associated with terminal ECU_B is set to P2. The port numbers associated with terminal ECU_D and terminal ECU_E are both set to P4.

[0124] When focusing on region ECU_B, terminal ECU_A and terminal ECU_B, belonging to region A, are connected to region ECU_A, and region ECU_A is connected to communication port P1 of region ECU_B. Additionally, terminal ECU_D and terminal ECU_E, belonging to region B, are both connected to communication port P2 of region ECU_B. Therefore, in the NM table of region ECU_B, the port numbers associated with terminal ECU_A and terminal ECU_B are all set to P1, and the port numbers associated with terminal ECU_D and terminal ECU_E are all set to P2.

[0125] [2-3. Port Transmission]

[0126] In each region of ECU22a, Figure 5 The port transmission processing in S270 and S330 of the message integration process performed by the arithmetic unit 224 shown differs from that in the first embodiment. Specifically, in this embodiment, when transmitting the integrated NM message to each communication port, the communication port to which transmission is required is extracted using the NM table, and the integrated NM message is transmitted to the extracted communication port. Specifically, a logical AND operation is independently calculated between the integrated PN request information represented by the integrated NM message and the PN filtering information of all end ECUs 23 represented by the NM message. Then, end ECUs 23 whose calculation result is not zero are extracted, and the integrated NM message is transmitted only to the communication port represented by the port number associated with the extracted end ECU 23.

[0127] [2-4. Update Section]

[0128] The update unit 226 updates the NM table when preset update conditions are met. Update conditions may include the addition of a new terminal ECU 23, an update of the program installed on the terminal ECU 23, or the acquisition of updated NM table data from an external source. In this embodiment, the update unit 226 is separate from the calculation unit 224, but the update unit 226 may also be implemented as part of the processing performed by the calculation unit 224.

[0129] For example Figure 7 The attached diagram, labeled E1, describes the case where a new terminal ECU 23 (hereinafter referred to as terminal ECU_G) is connected to transmission path 4, which is connected to communication port P2 of region ECU_B. Terminal ECU_G, connected to transmission path 4, sends an NM message containing its own PN filtering information as a PN request message when it is started due to certain events.

[0130] When the updating unit 226 of region ECU_B detects, by referring to its own NM table, that the information of the terminal ECU_G is not registered in the NM table, if... Figure 9 As shown in the previous section, an entry for the terminal ECU_G is appended to the NM table. This appended content is also transmitted to other region ECUs 22, where the terminal ECU_G entry is appended to the NM table in each region ECU. When the terminal ECU_G entry is appended to the NM table, in region ECU_B, where the terminal ECU 23 has been appended, the region category is set to its own region B, and the port number is set to P2, which represents the communication port that receives the NM message.

[0131] Other regional ECUs 22a that receive the update information (i.e., the added item of the terminal ECU_G) update their own NM tables according to the update information. Specifically, according to the regional category indicated by the update information, they add information to the NM table that associates the port number connected to the regional ECU_B corresponding to the regional category or the communication port reaching the regional ECU_B with the item of the terminal ECU_G that is the update information.

[0132] For example Figure 7 The following description illustrates the case where the PN filter information is changed via the procedure of the subordinate terminal ECU_D of the update area ECU_B, as shown by reference numeral E2 in the attached figure. In this case, the terminal ECU_D sends 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). Upon receiving the update instruction, the update unit 226, according to the content of the update instruction, as shown in the attached figure, performs the following steps: Figure 9 As shown in the next section, the PN filtering information for the terminal ECU_D, which is already registered in its own NM table, is updated. Furthermore, the update unit 226 transmits the aforementioned update instruction to other regional ECUs 22a. Thus, the NM table is updated in all regional ECUs 22a.

[0133] Alternatively, the update unit 226 may be configured to update the NM table according to the received update data when it receives update data of the NM table from the outside via the wireless device 3.

[0134] [2-5. Effects]

[0135] According to the second embodiment described above, the effects of the first embodiment (1a) to (1d) mentioned above are achieved, and the following effects are also achieved.

[0136] (2a) The regional ECU 22a is limited to transmitting integrated NM messages to the communication port of the terminal ECU 23 that reaches the target of the start-up by using an NM table. Therefore, according to the vehicle network system 1a, the amount of NM message communication can be further reduced.

[0137] (2b) Based on the vehicle network system 1a, the NM table maintained by the regional ECU 22a is updated according to the addition of the terminal ECU 23 and the program update, so as to flexibly respond to system changes.

[0138] [3. Third Implementation Method]

[0139] [3-1. Differences from the second embodiment]

[0140] Regarding the third embodiment, since its basic structure is the same as that of the second embodiment, the differences will be described below. Furthermore, the same reference numerals as in the first and second embodiments denote the same structures; please refer to the previous description.

[0141] In the first embodiment described above, the case where there are two transit area ECUs 22 between the terminal ECUs 23 was explained, but there may also be three or more transit area ECUs 22. For example, multiple area ECUs 22 connected hierarchically may exist within a single area.

[0142] like Figure 10 As shown, the vehicle network system 1b includes a regional ECU_AA under the regional ECU_A, which coordinates the regional ECU_AA as part of regional A. The regional ECU_AA also includes a terminal ECU_AA. The regional ECU_AA is connected to the communication port P5 of the regional ECU_A. The regional ECU_A is connected to the communication port P4 of the regional ECU_AA, and the terminal ECU_AA is connected to the communication port P1 of the regional ECU_AA. The vehicle network system 1b adds the regional ECU_AA and the terminal ECU 23 under the regional ECU_AA (in... Figure 10 Only the terminal ECU_AA is shown in the diagram; otherwise, it is the same as the vehicle network system 1a of the second embodiment. That is to say, in Figure 10 The description of the central ECU21, regional ECU_C, and part of the terminal ECU23 is omitted.

[0143] exist Figure 10 In the vehicle network system 1b shown, such as Figure 11Configure the NM tables for regions ECU_AA, ECU_A, and ECU_B in that way.

[0144] In the NM table of region ECU_AA, information for all end ECUs 23 connected to other region ECUs 22 is associated with port number P4. The region category of end ECU_AA is set to AA, and the information for end ECU_AA is associated with port number P1.

[0145] In the NM tables for regions ECU_A and ECU_B, Figure 8 The information for the terminal ECU_AA is appended to the content shown. Specifically, the information for the terminal ECU_AA is associated with port number P5 in the NM table of region ECU_A, and with port number P1 in the NM table of ECU_B.

[0146] [3-2. Example of an action]

[0147] For example, if an NM message representing a PN request information for a PN cluster including the terminal ECU_AA is sent from the terminal ECU_D, the PN request information of the integrated message generated by the region ECU_B will naturally include the PN cluster of the terminal ECU_AA. Therefore, this integrated NM message is transmitted to at least the communication port P1 according to the information of the terminal ECU_AA in the NM table and is received by the region ECU_A.

[0148] The integrated NM message transmitted to region ECU_A is transmitted at least again to communication port P5 according to the information of the end ECU_AA in the NM table of region ECU_A, and is received by region ECU_AA.

[0149] The integrated NM message transmitted to the region ECU_AA is transmitted at least again to the communication port P1 according to the information of the end ECU_AA in the NM table of the region ECU_AA, and is received by the end ECU_AA.

[0150] [3-3. Effect]

[0151] According to the third embodiment detailed above, the effects of the first embodiment (1a) to (1d) and the second embodiment (2a) and (2b) are achieved, and the following effects are also achieved.

[0152] (3a) In the vehicle network system 1b, the regional ECU 22 has a hierarchical multi-level connection structure, so it can also realize a network structure suitable for vehicles with a long overall length, such as commercial trucks.

[0153] [4. Other Implementation Methods]

[0154] The embodiments of this disclosure have been described above, but this disclosure is not limited to the aforementioned embodiments and can be implemented in various modifications.

[0155] (4a) In the above embodiment, a wireless device 3 is provided separately from the regional ECU 22, but the wireless device 3 may also be built into any one or more regional ECUs 22.

[0156] (4b) In the above embodiment, as an NW form that connects the regional ECU22 to the subordinate terminal ECU23, a combination of switching NW and bus NW is used, but it can also be unified into any NW form.

[0157] (4c) In the above embodiment, when buffer congestion is detected, the NM message is prevented from being discarded due to receive buffer overflow by forcibly ending the buffering period. Alternatively, the discarding of NM messages can be prevented by generating a consolidated NM message instead of buffering the NM messages. That is, the NM request information is directly extracted from the received NM message and stored in the working area of ​​the memory. Whenever a new NM message is received, the storage content of the working area is updated using the result of a logical OR operation between the NM request information extracted from the received NM message and the NM request information stored in the working area. Alternatively, a consolidated NM message can be generated using the NM request information stored in the working area at the end of the buffering period and transmitted to each communication port. In this case, although a new working area is needed for updating the NM request information, since it is not necessary to store all received NM messages during the buffering period, the overflow of the receive buffer can be suppressed.

[0158] (4d) In the above embodiment, each region ECU22a uses a separate NM table. In contrast, as... Figure 12 As shown, for example, multiple types of NM meters can be prepared in advance based on the equipment status of the vehicle equipped with the in-vehicle network system 1a, such as the destination and vehicle class. In this case, for example, it can be configured so that which NM meter to use can be selected at the factory. The selection of the NM meter can be made by a dedicated physical switch or by an external instruction via the wireless device 3. Alternatively, the equipment status of the vehicle can be determined based on the information flowing in the in-vehicle network system 1a and the NM meter can be automatically selected.

[0159] (4e) The arithmetic units 224 and 234 and their methods described in this disclosure can also be implemented using a special-purpose computer provided by comprising a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the arithmetic units 224 and 234 and their methods described in this disclosure can also be implemented using a special-purpose computer provided by comprising a processor configured with one or more special-purpose hardware logic circuits. Alternatively, the arithmetic units 224 and 234 and their methods described in this disclosure can also be implemented using one or more special-purpose computers configured by combining a processor and memory programmed to perform one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program can also be stored as instructions to be executed by a computer on a computer-readable non-transitional tangible recording medium. In the method of implementing the functions of each unit included in the arithmetic units 224 and 234, software is not necessarily required; one or more hardware components can be used to implement all of their functions.

[0160] (4f) Multiple components may be used to achieve the multiple functions of one component in the above embodiments, or multiple components may be used to achieve the single function of one component. Alternatively, one component may be used to achieve the multiple functions of multiple components, or one component may be used to achieve the single function achieved by multiple components. Furthermore, a portion of the configuration of the above embodiments may be omitted. Additionally, at least a portion of the configuration of the above embodiments may be added to or replaced with other configurations of the above embodiments.

[0161] (4g) In addition to the aforementioned vehicle network system, this disclosure can also be implemented in various ways, such as for enabling a computer to function as a component of the vehicle network system, namely the regional ECU 22 and the terminal ECU 23, the program for the regional ECU 22 or the terminal ECU 23 to perform its functions, a non-transitional physical recording medium such as a semiconductor memory containing the program, and a method for transmitting startup messages.

Claims

1. An in-vehicle network system characterized by comprising: Possessing: a plurality of relay nodes each having a plurality of communication ports; and a plurality of end nodes each connected to one of the plurality of relay nodes; each of the plurality of communication ports of the relay nodes is connected to the end nodes subordinate to the relay node or other relay nodes, the end nodes possess a startup section configured to transition from a sleep state to a wake-up state, transmit a startup message containing startup request information indicating a startup cluster to which the end node belongs, in the case where a startup condition inside the end node is satisfied, and transition from the sleep state to the wake-up state in the case where the startup message containing the startup request information indicating the startup cluster to which the end node belongs is received, the relay nodes possess: a message integration section configured to generate integrated startup request information by merging the startup request information indicated by the startup message, i.e., an integration target message, received from subordinate end nodes, and generate the startup message, i.e., an integration startup message, containing the integrated startup request information, in a decided buffer period; and a port transmission section configured to transmit the integration startup message generated by the message integration section to the communication ports other than the communication port that received the integration target message.

2. The in-vehicle network system according to claim 1, wherein the plurality of relay nodes each possess a startup table, the startup table lists, for all of the plurality of end nodes, information identifying the end node, startup filter information listing the startup cluster to which the end node belongs, information identifying the relay node connected to the end node, and information indicating the communication port to which the end node belongs, the port transmission section is configured to determine the startup cluster indicated by the startup request information from the integration startup message by comparing the startup request information with the startup filter information indicated by the startup table, and transmit the integration startup message to all of the communication ports to the determined end node.

3. The in-vehicle network system according to claim 2, wherein the in-vehicle network system further possesses an update section configured to update the startup table in the case where a predetermined update condition is satisfied.

4. The in-vehicle network system according to claim 3, wherein the update condition includes reception of the startup message from an end node that is not registered in the startup table.

5. The in-vehicle network system according to claim 3, wherein the update condition includes reception of an update instruction indicating update data of the startup table from an end node that is registered in the startup table.

6. The in-vehicle network system according to claim 3, wherein ​ The update condition includes: acquiring update data of the start table from outside of the in-vehicle network system.

7. The in-vehicle network system according to any one of claims 2 to 6, characterized in that The relay node is configured to have a plurality of types of the start table, and to select one of the plurality of types of the start table to use in accordance with a situation of equipment possessed by a vehicle on which the in-vehicle network system is mounted.

8. A relay node that forms a vehicular network system with other relay nodes and a plurality of end nodes, and that has a plurality of communication ports that connect with the other relay nodes or the end nodes subordinate to itself, characterized by, provided with: a message integration section configured to merge start request information indicated by a start message received from a subordinate end node, which is an integration target message, to generate integrated start request information, and to generate an integrated start message including the start request information, in a decided buffer period; and a port transmission section configured to transmit the integrated start message generated by the message integration section to the communication port other than the communication port that received the integration target message; the start request information is information indicating a start cluster to which the end node that is a transmission source of the start message belongs, in the end node, the start message is transmitted from the end node in a case where a predetermined start condition is satisfied, and in a case where the start request information included in the start message indicates the start cluster to which the end node that received the start message, which is a reception end node, belongs, the start message causes the reception end node to transition from a sleep state to a wake-up state.

9. A start message transmission method in a relay node that forms a vehicular network system together with other relay nodes and a plurality of end nodes and has a plurality of communication ports connected to the other relay nodes or the end nodes subordinate to itself, characterized by, including the steps of: merging start request information indicated by a start message received from a subordinate end node, which is an integration target message, to generate integrated start request information, and to generate an integrated start message including the start request information, in a decided buffer period; and transmitting the integrated start message generated to the communication port other than the communication port that received the integration target message; the start request information is information indicating a start cluster to which the end node that is a transmission source of the start message belongs, in the end node, the start message is transmitted from the end node in a case where a predetermined start condition is satisfied, and in a case where the start request information included in the start message indicates the start cluster to which the end node that received the start message, which is a reception end node, belongs, the start message causes the reception end node to transition from a sleep state to a wake-up state.

Images