In-vehicle network system and relay device

Abstract

Provided are an in-vehicle network system and a relay device that suppress power consumption of the in-vehicle network system and delay at the time of startup. When the wake-up signal is received via the communication lines (71, 81), the object extraction circuits (611, 612) acquire startup object data requesting the source node. A request generation circuit (63) generates startup request data by combining startup target data acquired during a predetermined acquisition period. The start-up determination circuits (612, 622) select a start-up target node in accordance with the generated start-up request data, and transmit a wake-up signal for selectively starting up the selected start-up target node in units of a group including one or more nodes.

Description

Technical Field

[0001] The present disclosure relates to in - vehicle network systems. Background Art

[0002] There is known a partial network technology for selectively controlling the wake - up / sleep states of each ECU. In Patent Document 1 described below, there is a technology described as follows: In a relay device that relays data transmission / reception between different networks, when a wake - up signal is received from a node on one network, based on the data included in the received wake - up signal, it is determined whether a wake - up signal can be sent to the other network.

[0003] Prior Art Documents

[0004] Patent Documents

[0005] Patent Document 1: Japanese Unexamined Patent Application Publication No. 2009 - 124480 Summary of the Invention

[0006] However, in the prior art, since it is assumed that the wake - up signal is sent in units of networks, there is a problem that all the nodes on the same network are started up, resulting in useless power consumption.

[0007] In addition, in the relay device, the relay function implemented by computer processing is used to transmit the wake - up signal between networks. Therefore, when the relay device is in the sleep state, waiting for the computer to start up to transmit the wake - up signal, there is a problem that the start - up time of the entire system increases.

[0008] One aspect of the present disclosure provides a technology for suppressing power consumption and start - up delay in an in - vehicle network system.

[0009] One embodiment of the present disclosure is an in - vehicle network system including a relay device and a plurality of nodes. The relay device connects a plurality of communication lines to each other.

[0010] The nodes are respectively connected to one of the plurality of communication lines and communicate with each other. The plurality of nodes have a normal operating state, i.e., a wake - up state, and a low - power consumption operating state in which some functions are restricted, i.e., a sleep state. A node in the sleep state changes to the wake - up state when a wake - up signal is received via the communication line. At least a part of the plurality of nodes is configured to send a wake - up signal when a preset start - up condition is satisfied.

[0011] The relay device is configured to, when a wake-up signal is received via a communication line, acquire the start-up target data of the request source node, and synthesize the start-up target data acquired during a specified acquisition period to generate start-up request data. The relay device is configured to, according to the generated start-up request data, select a start-up target node, and send a wake-up signal that designates and starts the selected start-up target node.

[0012] The request source node is the node that has become the transmission source of the wake-up signal. The start-up target data is set for each node and is data indicating the nodes that need to be started together when the node starts up. The start-up target node is the node that needs to transition from the sleep state to the wake-up state.

[0013] With such a configuration, it is possible to selectively start, in units of a group including one or more nodes, the nodes that need to be started together with the request source node. Therefore, it is possible to suppress the start-up of unnecessary nodes and suppress the power consumption of the in-vehicle network system. In addition, in the control related to the wake-up of the nodes, since there is no need to use the function of relaying communication frames, it is possible to suppress the delay at system startup.

[0014] One aspect of the present disclosure is a relay device that interconnects a plurality of communication lines to which one or more nodes are respectively connected, and includes a plurality of transceiver circuits, a signal transmission unit, and a wake-up control unit.

[0015] The transceiver circuits are provided for each of the plurality of communication lines and are configured to transmit and receive signals via the communication lines. The signal transmission unit is configured to transmit a communication frame received by one of the plurality of transceiver circuits to other transceiver circuits.

[0016] The wake-up control unit is configured to, when a wake-up signal is received via the transceiver circuit, acquire the start-up target data of the request source node, and synthesize the start-up target data acquired during a specified acquisition period to generate start-up request data. In addition, the wake-up control unit is configured to, according to the generated start-up request data, select a start-up target node, and send, via the transceiver circuit, a wake-up signal that designates and starts the selected start-up target node.

[0017] The request source node is the node that has become the transmission source of the wake-up signal. The start-up target data is set for each node and is data indicating the nodes that need to be started together when the node starts up. The start-up target node is the node that needs to transition from the sleep state to the wake-up state.

[0018] With such a configuration, it is possible to selectively start, in units of a group including one or more nodes, the nodes that need to be started together with the request source node. In addition, it is possible to suppress the situation of repeatedly sending wake-up signals to the same node. In addition, it is possible to execute the control related to the wake-up of the nodes without relying on the signal transmission unit. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a block diagram showing the overall configuration of the in-vehicle network system.

[0020] Figure 2 is a block diagram showing the configuration of the relay device.

[0021] Figure 3 is a block diagram showing the configuration of the wake-up control unit.

[0022] Figure 4 is an explanatory diagram showing the configuration of the start information table.

[0023] Figure 5 is an explanatory diagram illustrating the operation of the wake-up control unit.

[0024] Figure 6 is a flowchart of the wake-up transmission process executed by the on-demand operation unit of the node.

[0025] Figure 7 is a flowchart of the wake-up reception process executed by the on-demand operation unit of the node.

[0026] Figure 8 is a flowchart of the port process executed by the CAN port circuit and the Ethernet port circuit of the wake-up control unit.

[0027] Figure 9 is a flowchart of the table update process executed by the table update unit of the wake-up control unit.

[0028] Figure 10 is an explanatory diagram showing the configuration of the update frame.

[0029] Figure 11 is a flowchart of the table setting process executed by the table update unit of the wake-up control unit.

[0030] Figure 12 is a timing diagram showing the basic operation of the in-vehicle network system.

[0031] Figure 13 is a block diagram showing the configuration of the wake-up control unit in the relay device of the second embodiment.

[0032] Figure 14 is a flowchart of the port process executed by the CAN port circuit of the wake-up control unit constituting the relay device of the second embodiment.

[0033] Figure 15 is a block diagram showing another configuration example of the in-vehicle network system.

[0034] Figure 16 is a block diagram showing another configuration example of the in-vehicle network system.

[0035] Figure 17 It is a block diagram showing another configuration example of a vehicle-mounted network system. Detailed implementation manners

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

[0037] [1. First embodiment]

[0038] [1-1. Configuration]

[0039] Figure 1 The vehicle-mounted network system 100 shown includes a relay device 1. The relay device 1 connects the first network 7 and the second network 8 to each other.

[0040] The relay device 1 includes a CAN transceiver 2 and a switching hub 3. CAN is an abbreviation for Controller Area Network. CAN is a registered trademark. The CAN transceiver 2 is connected to the first network 7 and transceives communication frames conforming to the CAN protocol. The switching hub 3 is connected to the second network 8 and transceives communication frames conforming to the Ethernet protocol. Ethernet is a registered trademark.

[0041] The first network 7 forms a multi-drop type network in which a plurality of nodes (hereinafter referred to as CAN nodes) 72 are connected via one communication line (hereinafter referred to as a CAN bus) 71. The plurality of CAN nodes 72 perform communication conforming to the CAN protocol via the CAN bus 71. Hereinafter, the first network 7 will also be referred to as CAN-NW7. In addition, the number of CAN nodes 72 connected to one CAN bus 71 may also be one.

[0042] The second network 8 includes a plurality of communication lines (hereinafter referred to as Ethernet transmission paths) 81 each connected to one of the plurality of ports of the switching hub 3. The second network 8 forms a star-shaped network in which a plurality of nodes (hereinafter referred to as Ethernet nodes) 82 are connected via the plurality of Ethernet transmission paths 81. The Ethernet nodes 82 perform communication conforming to the Ethernet protocol via the Ethernet transmission paths 81 and the switching hub 3. Hereinafter, the second network 8 will also be referred to as Ethernet-NW8. In addition, the number of Ethernet transmission paths 81 may be one, and the number of Ethernet nodes 82 connected thereto may also be one.

[0043] Hereinafter, when it is not necessary to distinguish between the CAN nodes 72 and the Ethernet nodes 82, they will be simply referred to as nodes 72, 82. The nodes 72, 82 have two operation states: a wake-up state and a sleep state.

[0044] In addition, the wake-up state is, for example, a normal operating state in which all functions allocated to the present nodes 72 and 82 can be used. The sleep state is a low-power consumption operating state in which at least a part of the functions are restricted. Specifically, in the sleep state, for example, functions other than the function of the nodes 72 and 82 that execute processes related to wake-up can be stopped.

[0045] The nodes 72 and 82 include an ECU and a ready operating unit. The ECU is a part configured to include a computer having a CPU and a memory. Here, the state in which the ECU is stopped is the sleep state, and the state in which the ECU is started is the wake-up state. The ready operating unit is a part configured of hardware without including a computer, operates also in the sleep state, and implements at least functions related to the wake-up of the present node.

[0046] In the CAN-NW7, CAN frames are transmitted and received. The CAN frames include frames used as wake-up signals. In the header area of the CAN frame used as a wake-up signal, it is indicated that it is a wake-up signal. In addition, in the header area of the wake-up signal, a node ID inherently allocated to the node is indicated in order to identify the node that is the request source. In the data area of the wake-up signal, start request data indicating the node or group of nodes to be the start target is included.

[0047] The CAN node 72 in the wake-up state changes to the sleep state when the sleep condition is satisfied. The CAN node 72 in the sleep state changes to the wake-up state when a wake-up signal is received via the CAN bus 71 and the start request data indicating that the present node or the group to which the present node belongs is to be the start target is indicated in the received wake-up signal.

[0048] In addition, the CAN node 72 in the sleep state changes to the wake-up state when a predetermined start condition such as a start trigger occurs in the present node, and transmits a wake-up signal in which the node ID of the present node and the PNI data of the present node are set as start request data. The PNI data is data indicating the node or group of nodes that need to be started together with the present node, and details will be described later.

[0049] In the Ethernet-NW8, as a wake-up signal, a start request and a start indication signal including a wake-up pulse are used. The wake-up pulse is, for example, a pulse signal having a pulse width sufficiently wider than the pulse used for the transmission path code. The Ethernet node 82 in the wake-up state changes to the sleep state when the sleep condition is satisfied. The Ethernet node 82 in the sleep state changes to the wake-up state when a wake-up pulse is received via the Ethernet transmission path 81. In addition, the Ethernet node 82 in the sleep state changes to the wake-up state when a start trigger occurs in the present node, and transmits a wake-up pulse to the Ethernet transmission path 81.

[0050] In addition, the sleep conditions may include, for example, no communication in this node for a certain period of time or receiving a communication frame indicating a transition to the sleep state. The start trigger may include, for example, detecting a specific vehicle operation such as an operation of a door handle.

[0051] The CAN transceiver 2 is a transceiver circuit that implements the functions of the physical layer of CAN. The CAN transceiver 2 has a port P0 connected to the CAN bus 71 and performs the transmission and reception of CAN frames with the CAN node 72. The CAN transceiver 2 includes a function of decoding an encoded signal transmitted via the CAN bus 71 into a digital signal and a function of encoding a digital signal into a signal for transmission and sending it to the CAN bus 71.

[0052] The switching hub 3 has a plurality of ports P1 to PN connected to the Ethernet transmission path 81 and performs the transmission and reception of Ethernet frames with the Ethernet nodes 82 connected to each Ethernet transmission path 81. N is an integer of 2 or more. The switching hub 3 is also connected to the CAN transceiver 2.

[0053] As Figure 2 shown, the switching hub 3 includes a plurality of PHY transceivers 4, a signal transmission unit 5, and a wake-up control unit 6. The signal transmission unit 5 is constituted by a computer including a CPU and a memory. At least a part of the functions of the signal transmission unit 5 is realized by processing executed by the CPU.

[0054] Parts other than the signal transmission unit 5 of the switching hub 3 (i.e., the PHY transceivers 4 and the wake-up control unit 6) and the CAN transceiver 2 do not include a computer and are constituted by hardware. In particular, the CAN transceiver 2 and the PHY transceivers 4 can use commercially available semiconductor integrated circuits.

[0055] The relay device 1 has a sleep state and a wake-up state in the same manner as the nodes 72 and 82. Similar to the ECUs of the nodes 72 and 82, the state in which the signal transmission unit 5 stops is the sleep state, and the state in which the signal transmission unit 5 starts is the wake-up state. The CAN transceiver 2, the PHY transceivers 4, and the wake-up control unit 6 work even in the sleep state in the same manner as the always-on parts of the nodes 72 and 82.

[0056] The PHY transceiver 4 is a transceiver circuit that implements the functions of the physical layer of Ethernet. The PHY transceivers 4 are respectively provided at a plurality of ports P1 to PN to which the Ethernet transmission path 81 is connected. The PHY transceiver 4 includes a function of decoding an encoded signal transmitted via the Ethernet transmission path 81 into a digital signal and a function of encoding a digital signal into a signal for transmission and sending it to the Ethernet transmission path 81.

[0057] When the PHY transceiver 4 detects a wake-up pulse on the Ethernet transmission path 81, it outputs a detection notice indicating the detection of the wake-up pulse to the wake-up control unit 6. In addition, when a start instruction is input from the wake-up control unit 6, the PHY transceiver 4 sends a wake-up pulse to the Ethernet transmission path 81.

[0058] The signal transmission unit 5 has a protocol conversion function. That is, when the signal transmission unit 5 receives a communication frame via the PHY transceiver 4, it uses the MAC address table to determine the port connected to the node that is the destination based on the MAC address of the destination, and transmits the communication frame to the determined port. Among them, when the destination node is the CAN node 72, protocol conversion from Ethernet to CAN is performed, and the communication frame is transmitted to the CAN transceiver 2.

[0059] In addition, when the signal transmission unit 5 receives a CAN frame via the CAN transceiver 2, it determines the port connected to the node that is the destination based on the node ID of the destination indicated in the frame header area of the CAN frame. When the determined node is the Ethernet node 82, protocol conversion from CAN to Ethernet is performed, and the communication frame is sent to the determined port.

[0060] The signal transmission unit 5 may have the following functions: when receiving a communication frame in which table update data is set in the data area, taking out the table update data from the data area and outputting it to the wake-up control unit 6. In addition, the signal transmission unit 5 may have the following functions: when receiving a communication frame in which device determination data is set in the data area, taking out the device determination data from the data area and outputting it to the wake-up control unit 6. In addition, the table update data and the device determination data will be described later.

[0061] As Figure 3 shown, the wake-up control unit 6 includes a CAN port circuit 61, a plurality of Ethernet port circuits 62, a request generation circuit 63, a table storage unit 64, and a table update unit 65.

[0062] The table storage unit 64 stores a start information table. As Figure 4 shown, it is a set of data in which the port number, node identification data, and PNI data are associated.

[0063] The node identification data is information for uniquely identifying the nodes 72 and 82. Regarding the node identification data, the node ID can be used for the CAN node 72, and the MAC address can be used for the Ethernet node 82. The node identification data of all the nodes 72 and 82 is listed in the start information table.

[0064] The port number is information for identifying the ports to which nodes 72 and 82 are connected. In the present embodiment, since there is one CAN bus 71 connected to the CAN node 72, all the node identification information indicating the CAN node 72 is associated with the same port number (i.e., port P0). Since the Ethernet nodes 82 are respectively connected to different Ethernet transmission paths 81, different port numbers (i.e., ports P1 to PN) are assigned to all the node identification information indicating the Ethernet nodes 82. In addition, in the case where there are a plurality of CAN buses 71, the identification information indicating the CAN node 72 is associated with different port numbers according to the CAN bus 71 to which it is connected.

[0065] The PNI data is represented by data of a plurality of bits. PNI is an abbreviation of Pertial Network Information. Start groups are assigned to each bit of the PNI data. The start group refers to a group of nodes 72 and 82 that need to be started together when a certain node is started. That is, in the PNI data, the bit corresponding to the start group to which the node 72 and 82 corresponding to the PNI data belong is set to 1. Each of the nodes 72 and 82 belongs to at least one start group and may belong to a plurality of start groups.

[0066] Return to Figure 3 , the table update unit 65 executes table update processing, table setting processing, etc. according to the data input from the signal transmission unit 5. The table update processing is a process of updating the start information table stored in the table storage unit 64. The table setting processing is a process of selecting and setting the start information table to be used in the case where a plurality of types of start information tables are prepared.

[0067] The CAN port circuit 61 includes a frame header analysis circuit 610, an object extraction circuit 611, and a start determination circuit 612. The frame header analysis circuit 610 determines whether it is a wake-up start signal by analyzing the frame header area of the digitized CAN frame input from the CAN transceiver 2. When the frame header analysis circuit 610 determines that it is a wake-up start signal, it outputs a start instruction to the signal transmission unit 5, and extracts the node ID of the request source from the frame header area of the CAN frame and outputs it to the object extraction circuit 611. In addition, the frame header analysis circuit 610 can be configured to omit outputting a start instruction to the signal transmission unit 5 when it is known that the signal transmission unit 5 has completed starting.

[0068] The object extraction circuit 611 extracts the PNI data of the request source node by referring to the start information table according to the node ID extracted by the frame header analysis circuit 610. The object extraction circuit 611 outputs the extracted PNI data as start object data to the request generation circuit 63. The request source node here is the CAN node 72 that has become the transmission source of the wake-up signal.

[0069] The start determination circuit 612 individually performs a bitwise logical AND operation (i.e., AND operation) between the PNI data of all the CAN nodes 72 stored in the start information table and the start request data generated by the request generation circuit 63. The start determination circuit 612 notifies the node ID corresponding to the PNI data whose AND operation result is non-zero to the frame header analysis circuit 610.

[0070] The frame header analysis circuit 610 generates a wake-up signal showing the start request data corresponding to the node ID notified from the start determination circuit 612 in the data area, and transmits it to the CAN bus 71 via the CAN transceiver 2. Alternatively, the processing of the start determination circuit 612 can be omitted, and a wake-up signal showing the start request data generated by the request generation circuit 63 can be generated and transmitted.

[0071] The Ethernet port circuit 62 includes an object extraction circuit 621 and a start determination circuit 622. Here, the port corresponding to one Ethernet port circuit 62 of interest is referred to as this port. When the object extraction circuit 621 is notified of the input detection from the PHY transceiver 4 of this port, it extracts the PNI data of the request source node by referring to the start information table according to the port number of this port. The object extraction circuit 621 outputs the extracted PNI data as start object data to the request generation circuit 63. The request source node here is the Ethernet node 82 that has sent the wake-up pulse.

[0072] The start determination circuit 622 performs a bitwise logical AND operation (i.e., AND operation) between the PNI data of the Ethernet node 82 connected to this port stored in the start information table and the start request data generated by the request generation circuit 63. When the operation result of the start determination circuit 612 is non-zero, it outputs a start instruction to the PHY transceiver 4 of this port. The PHY transceiver 4 that has received the start instruction transmits a wake-up pulse.

[0073] The request generation circuit 63 performs a bitwise logical OR operation (i.e., OR operation) on all the start object data output from the CAN port circuit 61 and the plurality of Ethernet port circuits 62 to generate start request data. Among them, the request generation circuit 63 performs processing at each fixed acquisition cycle, and performs a logical OR operation on the start object data generated in the immediately preceding acquisition cycle.

[0074] [1-2. Operation example of the wake-up control unit]

[0075] A case where the relay device 1 receives wake-up signals from three nodes N1 to N3 approximately simultaneously (i.e., during the same acquisition cycle) is described. In addition, the PNI data is set to data representing nine start-up groups G1 to G9 in 9 bits.

[0076] As Figure 5 shown, node N1 belongs to start-up group G4, node N2 belongs to start-up group G7, and node N3 belongs to start-up groups G2 and G4. In this case, the three PNI data (i.e., start-up target data) extracted from the start-up information table become [000100000], [000000100], and [010100000]. The start-up request data obtained by the request generation circuit 63 performing a logical OR operation on these start-up target data becomes [010100100].

[0077] When node N4, which is the object of start-up determination, belongs to start-up groups G1 and G9, the PNI data is [100000001]. In this case, the operation result of the logical AND operation between the PNI data of node N4 and the start-up request data generated by the request generation circuit 63 becomes [000000000]. That is, since node N4 does not belong to any of the start-up groups indicated by the start-up request data, the operation result becomes zero, and it is determined that node N4 does not need to be woken up. That is, the sleep state of node N4 continues.

[0078] When node N5, which is the object of start-up determination, belongs to start-up group G4, the PNI data is [000100000]. In this case, the result of the logical AND operation between the PNI data of node N5 and the start-up request data generated by the request generation circuit 63 becomes [000100000]. That is, since node N5 belongs to one of the start-up groups indicated by the start-up request data, which is G4, the operation result becomes non-zero, and it is determined that node N5 needs to be woken up. That is, the transmission of a wake-up signal or a wake-up pulse for node N5 is executed, and node N5 changes to the wake-up state.

[0079] [1-3. Processing]

[0080] [1-2-1. Wake-up transmission processing]

[0081] Using Figure 6 the flowchart, the wake-up transmission processing executed in the on-demand operation units of nodes 72 and 82 is described.

[0082] Regardless of whether the operation state of this node is the wake-up state or the sleep state, the wake-up transmission processing is repeatedly executed. In addition, in the following description, the wake-up signal in Ethernet node 82 is set to a signal representing a wake-up pulse.

[0083] In S110, the on-demand working unit determines whether a start trigger has occurred at this node. If no start trigger has occurred, this step is repeated and the unit waits in standby. If a start trigger has occurred, the process moves to S120.

[0084] In S120, the on-demand working unit determines whether this node is in a sleep state (i.e., the state where the ECU is stopped). When the on-demand working unit determines that it is in a sleep state, the process moves to S130. When it determines that it is not in a sleep state but in a wake state, the process moves to S150.

[0085] In S130, the on-demand working unit starts the ECU of this node. The started ECU begins the initialization process to enable various processes to be executable. The initialization process includes turning on the power to each part of this node, starting the OS on the computer, starting the applications on the OS, etc.

[0086] In S140, the on-demand working unit determines whether the ECU has completed the initialization process. If the initialization process has not been completed, this step is repeated and the unit waits in standby. If the initialization process has been completed, the process moves to S150.

[0087] In S150, the on-demand working unit outputs an instruction to cause the ECU to send a wake-up signal and ends the process. According to this instruction, the ECU executes the process of sending a wake-up signal.

[0088] [1-3-2. Wake-up reception process]

[0089] Use Figure 7 the flowchart to explain the wake-up reception process executed in the on-demand working units of nodes 72 and 82. Similar to the wake-up transmission process, the wake-up reception process is repeatedly executed regardless of whether the operating state of this node is the wake state or the sleep state.

[0090] In S210, the on-demand working unit determines whether a wake-up signal has been received. If no wake-up signal has been received, this step is repeated and the unit waits in standby. If a wake-up signal has been received, the process moves to S220. In this case, the wake-up signal in CAN node 72 is such a CAN frame that indicates in the frame header area that it is a wake-up signal and indicates the start object data specifying this node in the data area.

[0091] In S220, the on-demand working unit determines whether this node is in a sleep state. If it is in a sleep state, the process moves to S130. If it is not in a sleep state, i.e., in a wake state, the process ends.

[0092] In S230, the on-demand operation unit activates the ECU of this node. The activated ECU starts the initialization process for enabling various processes to be in an executable state. In S240, the on-demand operation unit determines whether the initialization process has been completed. If the initialization process has not been completed, this step is repeated and the unit waits. If the initialization process has been completed, the process ends.

[0093] In addition, the processing of S220 to S240 is the same as the processing of S120 to S140 described previously.

[0094] [1-2-3. Port Processing]

[0095] Using Figure 8 the flowchart, the port processing performed by the CAN port circuit 61 and the Ethernet port circuit 62 in the wake-up control unit 6 of the relay device 1 will be described. Hereinafter, without distinguishing between the CAN port circuit 61 and the Ethernet port circuit 62, they will be simply referred to as port circuits. The port circuit repeatedly executes the port processing regardless of whether the relay device 1 is in the sleep state or the wake-up state.

[0096] In S310, the port circuit determines whether it is the processing timing. If it is the processing timing, the process moves to S340. If it is not the processing timing, the process moves to S320. The processing timing is, for example, the timing generated during the acquisition cycle described in the request generation circuit 63.

[0097] In S320, the port circuit determines whether a wake-up signal has been received. If a wake-up signal has been received, the process moves to S330. If a wake-up signal has not been received, the process returns to S310.

[0098] In the CAN port circuit 61, the determination of whether a wake-up signal has been received is made based on whether the CAN frame received by the CAN transceiver 2 is determined by the frame header analysis circuit 610 to be a wake-up signal. In addition, in the Ethernet port circuit 62, it is based on whether a detection notification has been received from the PHY transceiver 4.

[0099] In S330, the port circuit executes the processing of the object extraction circuits 611 and 621 that extract the start object data and output it to the request generation circuit 63. Specifically, the port circuit uses the node identification information of the request source node that requests wake-up, refers to the start information table, and thereby extracts the PNI data of the request source node as the start object data. Among them, in the CAN port circuit 61, the node ID indicated by the frame header of the wake-up signal is used as the node identification information, and in the Ethernet port circuit 62, the port number of this port that has received the detection notification is used as the node identification information.

[0100] In S340, the port circuit acquires the start request data generated by the request generation circuit 63. In S350, the port circuit acquires the PNI data of the node connected to this port from the start information table. Additionally, in the case of the CAN port circuit 61, since multiple nodes are connected to this port, the PNI data of all these nodes is acquired. In the case of the Ethernet port circuit 62, since one node is connected to this port, the PNI data of this one node is acquired.

[0101] In S360, the port circuit performs a logical AND operation between the start request data acquired in S340 and the PNI data acquired in S350. In the CAN port circuit 61, the logical AND operation between the acquired multiple PNI data and the start request data is performed respectively.

[0102] In S370, the port circuit determines whether the operation result in S360 is non-zero. If the operation result is non-zero, the process proceeds to S380. If the operation result is zero, the process ends. Additionally, in the CAN port circuit 61, as long as there is one PNI data among the multiple PNI data whose logical AND operation result is non-zero, the process proceeds to S380.

[0103] In S380, the port circuit selects the node with a non-zero operation result as the start target node, gives an instruction to cause the selected start target node to transition to the wake-up state, and ends the process. Specifically, in the CAN port circuit 61, the node IDs of all the start target nodes are output to the frame header analysis circuit 610. The frame header analysis circuit 610 generates a wake-up signal for each start target node, and sends the generated wake-up signal to the CAN bus 71 via the CAN transceiver 2. That is, sending a wake-up signal representing the start request data specifying each start target node is equivalent to specifying the start target node to send a wake-up signal. Additionally, instead of generating a wake-up signal for each start target node, it is also possible to send only one wake-up signal representing the start request data specifying all the start target nodes generated by the request generation circuit 63. In the Ethernet port circuit 62, a start instruction is output to the PHY transceiver 4 of this port. The PHY transceiver 4 that has received the start instruction sends a wake-up pulse to the Ethernet transmission path 81 of this port. That is, selectively sending a wake-up pulse only to the Ethernet transmission path 81 connected to the start target node is equivalent to specifying the start target node to send a wake-up signal.

[0104] [1-3-4. Table update process]

[0105] Use Figure 9Flowchart showing the table update process executed by the table update unit 65 of the wake-up control unit 6. The table update process is a process of updating the start information table stored in the table storage unit 64.

[0106] In addition, at least one of the nodes 72 and 82 sends a communication frame (hereinafter referred to as an update frame) that lists the PNI data of each node in the data area as shown Figure 10 The update frame can be sent from any one of the nodes 72 and 82. In this case, the PNI data of all the nodes 72 and 82 may be included in the data area. In addition, the update frame can also be sent from all the nodes 72 and 82. In this case, only the PNI data of the source node 72 or 82 may be shown in each update frame.

[0107] The PNI data carried in the update frame can be represented by an integer multiple of 1 byte. For example, when the PNI data is 9 bits, for the PNI data carried in the update frame, each node is represented by 2 bytes.

[0108] When the signal transmission unit 5 receives the update frame, it outputs the PNI data shown in the data area of the update frame as table update data to the table update unit 65 of the wake-up control unit 6. Among them, when all the nodes send the update frame individually, the signal transmission unit 5 outputs the data in which the PNI data extracted from the data area is associated with the node identification information of the source as the table update data. In addition, it may be that when one node sends the PNI data of all the nodes together, the node identification information can be determined according to the arrangement of the PNI data in the data area.

[0109] When the relay device 1 is in the wake-up state, that is, when the signal transmission unit 5 is in a state where it can execute the processing of the communication frame, the table update process is repeatedly executed. As Figure 9 shown, in S410, the table update unit 65 determines whether table update data is obtained from the signal transmission unit 5. If the table update data is obtained, the process proceeds to S420. If the table update data is not obtained, the process ends.

[0110] In S420, the table update unit 65 updates the start information table stored in the table storage unit 64 using the obtained table update data, and ends the process.

[0111] [1-3-5. Table setting process]

[0112] Using Figure 11 the flowchart, the table setting process executed by the table update unit 65 of the wake-up control unit 6 is described. When multiple types of start information tables corresponding to the status of vehicle equipment are prepared, the table setting process is a process of selecting which one to use for setting.

[0113] In addition, at least one of the nodes 72 and 82 transmits a communication frame that sets the device status data (hereinafter referred to as device status data) of the vehicle that can be recognized in the data area. The device status data can include, for example, data obtained via the CAN bus 71, that is, data indicating the type of vehicle, the grade of the vehicle, and the delivery location, etc.

[0114] The table setting process is repeatedly executed while the relay device 1 is in the wake-up state, similarly to the table update process. As Figure 11 shown, in S510, the table update unit 65 determines whether device status data is acquired from the signal transmission unit 5. If the device status data is acquired, the process proceeds to S520. If the device status data is not acquired, the process ends.

[0115] In S520, the table update unit 65 selects a startup information table corresponding to the device status data from among a plurality of types of prepared startup information tables. In addition, the table update unit 65 sets the selected startup information table in the table storage unit 64 so that it can be used by the CAN port circuit 61 and the Ethernet port circuit 62, and ends the process.

[0116] [1-4. System Operation]

[0117] Using Figure 12 the timing diagram shown, the representative operation of the in-vehicle network system 100 will be described. Hereinafter, the node in which a startup trigger has occurred will be referred to as a trigger node, the nodes belonging to the same startup group as the trigger node will be referred to as startup target nodes, and the nodes not belonging to the same startup group as the trigger node will be referred to as non-startup target nodes. The trigger node, the startup target nodes, and the non-startup target nodes can each be any one of the CAN nodes 72 and the Ethernet nodes 82.

[0118] As Figure 12 shown, it is assumed that in the initial state, the relay device 1, the CAN nodes 72, and the Ethernet nodes 82 are all in the sleep state. When the trigger node detects the occurrence of a startup trigger, it starts the ECU and changes the own node from the sleep state to the wake-up state. The trigger node that has changed to the wake-up state transmits a wake-up signal.

[0119] When the relay device 1 receives the wake-up signal, it starts the signal transmission unit 5 and changes the relay device 1 from the sleep state to the wake-up state. In parallel with the startup of the signal transmission unit 5, the relay device 1 uses the wake-up control unit 6 to execute a process of transmitting a wake-up signal for selectively starting the nodes to be startup targets in units of a group including one or more nodes. The wake-up signal is transmitted regardless of whether the initialization of the signal transmission unit 5 is completed, that is, regardless of whether the transition to the wake-up state is completed. That is, the wake-up signal is transmitted regardless of the operation of the signal transmission unit 5.

[0120] The starting object node that receives the wake-up signal causes this node to transition from the sleep state to the wake-up state by starting the ECU, thereby preparing for communication from other nodes belonging to the same starting group.

[0121] After that, when the initialization of the signal transmission unit 5 is completed and the relay device 1 transitions to the wake-up state, the data frames are transmitted and received between the triggered node that has been started and the starting object node. Among them, the communication between the started CAN nodes 72 is executed without passing through the relay device 1.

[0122] [1-5. Effects]

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

[0124] (1a) In the relay device 1, for each wake-up signal that is generated approximately simultaneously in multiple networks, the PNI data (i.e., starting object data) indicating the starting group to which each node that is the source of the wake-up signal belongs is extracted. By synthesizing the extracted starting object data, starting request data indicating all the starting groups that need to be started is generated. By comparing the generated starting request data with the PNI data of each node, the nodes that are the starting objects are determined, and the wake-up signal is selectively transmitted not in units of networks but in units of starting groups. Therefore, according to the relay device 1, it is possible to suppress the situation where nodes that do not need to be started are started in vain, and power saving of the system is achieved. In addition, it is possible to suppress the situation where the wake-up signal is repeatedly transmitted to the already started nodes.

[0125] (1b) In the relay device 1, the wake-up control unit 6 is composed of hardware and operates independently of the signal transmission unit 5, so it is possible to send a wake-up signal to the nodes that are the starting objects before the start of the signal transmission unit 5 is completed. Therefore, compared with the existing device that uses the signal transmission unit 5 of the relay device 1 to transmit the wake-up signal, the start-up time of the entire system can be shortened.

[0126] (1c) In the relay device 1, it is configured to be able to update the start information table listing the PNI data of each node. Therefore, according to the relay device 1, even when it is necessary to change the starting group due to changes in the system configuration, etc., it is possible to respond flexibly.

[0127] (1d) In the relay device 1, it is configured to be able to switch the start information table used according to the device status data. Therefore, according to the relay device 1, even when the starting group changes due to the vehicle grade, the installation status of optional equipment, etc., it is possible to respond flexibly.

[0128] [2. Second Embodiment]

[0129] [Differences from the First Embodiment]

[0130] Since the basic configuration of the second embodiment is the same as that of the first embodiment, the differences will be described below. In addition, the same reference numerals as those in the first embodiment denote the same components, and reference may be made to the previous description.

[0131] In the second embodiment, a part of the configuration of the wake-up control unit 6a is different from that of the first embodiment. Specifically, in the CAN port circuit 61 of the first embodiment, it is configured to perform processing by using the frame header analysis circuit 610 to refer to the frame header area of the CAN frame. In contrast, the CAN port circuit 61a of the second embodiment is different from the first embodiment in that it is configured by using a CAN decoding circuit that performs processing by referring not only to the frame header area of the CAN frame but also to the data area.

[0132] As Figure 13 shown, the CAN port circuit 61a constituted by the CAN decoding circuit includes a data extraction unit 613 and a wake-up signal generation unit 614. When the received CAN frame is a wake-up signal, the data extraction unit 613 extracts PNI data from the data area, uses the extracted PNI data as start target data, and outputs it to the request generation circuit 63.

[0133] When the wake-up signal generation unit 614 obtains non-zero start request data from the request generation circuit 63, it generates a wake-up signal in which the start request data is set in the data area, and transmits it to the CAN bus 71 via the CAN transceiver 2.

[0134] When the CAN node 72 receives the wake-up signal, it refers to the start request data shown in the data area and compares it with the PNI data of this node, thereby determining whether to change this node to the wake-up state.

[0135] [2-2. Processing]

[0136] Using Figure 14 the flowchart, the port processing performed by the CAN port circuit 61a will be described.

[0137] In S610, the CAN port circuit 61a determines whether it is the processing timing. If it is the processing timing, the process proceeds to S640; if it is not the processing timing, the process proceeds to S620.

[0138] In S620, the CAN port circuit 61a determines whether a wake-up signal has been received. If a wake-up signal has been received, the process proceeds to S630; if a wake-up signal has not been received, the process returns to S610.

[0139] In addition, the processing of S610 and S620 is the same as that of S310 and S320 in the CAN port circuit 61 described in the first embodiment. In S630, the CAN port circuit 61a obtains the PNI data from the data area of the wake-up signal and outputs it as start-up target data to the request generation circuit 63, and returns the processing to S610.

[0140] In S640, the CAN port circuit 61a obtains the start-up request data generated by the request generation circuit 63. In S650, the CAN port circuit 61a determines whether the start-up request data obtained in S640 is non-zero. If it is non-zero, the processing proceeds to S660; if it is zero instead of non-zero, the processing ends.

[0141] In S660, the CAN port circuit 61a generates a CAN frame indicating that it is a wake-up signal in the frame header area and setting the obtained start-up request data in the data area, and outputs it to the CAN transceiver 2, and ends the processing.

[0142] [2-3. Effects]

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

[0144] (2a) The start-up request data is sent to the CAN node 72 using the wake-up signal, and the CAN node 72 determines whether to start the present node using the start-up request data. Therefore, it is not necessary to send respective wake-up signals to each CAN node 72 on the CAN bus 71, and the communication volume of the CAN bus 71 during wake-up can be reduced.

[0145] [3. Other Embodiments]

[0146] The embodiments of the present disclosure have been described above, but the present disclosure is not limited to the above-described embodiments and can be implemented with various modifications.

[0147] (3a) In the above-described embodiment, different protocols are used in the first network 7 and the second network 8, but the same protocol can also be used. In addition, the protocols used in each of the networks 7 and 8 are not limited to the CAN protocol and the Ethernet protocol, and any communication protocol can be used.

[0148] (3b) In the above-described embodiment, the wake-up control unit 6 includes the table update unit 65, but the signal transmission unit 5 can also include the table update unit 65.

[0149] (3c) In the above-described embodiment, it is configured to send a wake-up signal and a wake-up pulse from the node 72 or 82 where the start trigger has occurred, but it is not limited thereto. For example, it can also be as Figure 15Like the in-vehicle network system 101 shown, a relay device 1 is connected to a wireless device 9, and the relay device 1 receives a wake-up signal from an external device via the wireless device 9. In addition, the relay device 1 may be configured to detect a start trigger that occurs due to communication with an external device, and output a wake-up signal or a detection notification to the switching hub 3. In this case, PNI data with the wireless device 9 or an external device that communicates with the wireless device 9 as a node may also be added to the start information table. The start trigger detected by the wireless device 9 may include, for example, a program rewrite request based on OTA from an external device, various requests from a digital key, a remote key, etc. In addition, the wireless device 9 may be used to update the start information table from outside the vehicle via OTA and a DDN controller. In addition, as in Figure 16 the in-vehicle network system 102 shown, the wireless device 9 may be built into the relay device 1.

[0150] (3d) In the above-described embodiment, the case where there is one relay device 1 has been described, but multiple relay devices 1 may be connected in multiple stages like the in-vehicle network system 103 shown in Figure 17 . In addition, in Figure 17 , CAN is used as the protocol between the relay devices 1, but it is not limited thereto.

[0151] (3e) Multiple functions of one component in the above-described embodiment may be implemented by multiple components, or one function of one component may be implemented by multiple components. In addition, multiple functions of multiple components may be implemented by one component, or one function implemented by multiple components may be implemented by one component. In addition, a part of the configuration of the above-described embodiment may be omitted. In addition, at least a part of the configuration of the above-described embodiment may be added to or replaced with the configuration of other above-described embodiments.

[0152] (3f) In addition to the above-described in-vehicle network system and relay device, the present disclosure can also be implemented in the form of a wake-up control method or the like.

Claims

1. A vehicle network system, characterized in that: have: a relay device that interconnects a plurality of communication lines; and A plurality of nodes are respectively connected to one of the plurality of communication lines to communicate with each other. The plurality of nodes are configured to have a normal operation state, namely, an awake state, and a low-power consumption operation state in which at least a portion of functions are restricted, namely, a sleep state, and the node in the sleep state changes to the awake state when receiving a wake-up signal via the communication line. At least a portion of the plurality of nodes is configured to send the wake-up signal when a preset activation condition is satisfied, The relay device is configured to, when receiving the wake-up signal via the communication line, obtain the startup object data of the request source node, synthesize the startup object data obtained during a specified acquisition period to generate startup request data, select a startup object node according to the generated startup request data, and send the wake-up signal to designate and start the selected startup object node. The request source node is the node that becomes the transmission source of the wake-up signal, The startup object data is set for each of the nodes and is data indicating the nodes that need to be started together when the node is started. The activation target node is the node that needs to transition from the sleep state to the awake state.

2. The vehicle network system according to claim 1, characterized in that: A plurality of the relay devices are provided, The relay devices are connected in multiple stages.

3. The vehicle network system according to claim 1, characterized in that: The plurality of communication lines include at least the communication line using either a CAN protocol or an Ethernet protocol.

4. The vehicle network system according to claim 1, characterized in that: It also has a wireless device for communicating with external devices. The relay device is configured to receive the wakeup signal from the external device via the wireless device.

5. A relay device that interconnects a plurality of communication lines each connected to one or more nodes, characterized in that: have: a plurality of transceiver circuits, provided in each of the plurality of communication lines, configured to transmit and receive signals via the communication lines; a signal transmission unit configured to transmit a communication frame received by one of the plurality of transceiver circuits to the other transceiver circuits; as well as The wake-up control unit is configured to, when receiving a wake-up signal via the transceiver circuit, obtain the startup object data of the request source node, synthesize the startup object data obtained during a specified acquisition period to generate startup request data, select the startup object node according to the generated startup request data, and send the wake-up signal for specifying and starting the selected startup object node via the transceiver circuit. The request source node is the node that becomes the transmission source of the wake-up signal, The startup object data is set for each of the nodes and is data indicating the nodes that need to be started together when the node is started. The startup object node is the node that needs to be changed from a dormant state to an awakened state. The awake state is a normal operating state, and the sleep state is a low-power-consumption operating state in which at least a part of functions is restricted.

6. The relay device according to claim 5, characterized in that: The signal transmission unit is configured to have the awake state and the sleep state, and when the awake signal is received via the transceiver circuit in the sleep state, the signal transmission unit changes from the sleep state to the awake state. The wakeup control unit is configured to transmit the wakeup signal independently of the operation of the signal transmission unit.

7. The relay device according to claim 5, characterized in that: The wake-up control unit comprises: a table storage unit storing, for each of the plurality of nodes, a startup information table in which node identification information for identifying the node is associated with the startup target data for the node; an object extraction circuit, which extracts the startup object data corresponding to the request source node from the startup information table when the wake-up signal is received by the transceiver circuit; a request generation circuit that synthesizes the startup object data extracted by the object extraction circuit during the acquisition period to generate the startup request data; as well as The startup determination circuit compares the startup target data of the node with the startup request data to determine whether to set the node as the startup target node.

8. The relay device according to claim 7, characterized in that: The wake-up control unit is configured by hardware.

9. The relay device according to claim 7, characterized in that: The startup object data is composed of a plurality of bits of data, each of which is assigned a startup group and is set to logic 1 when the node corresponding to the startup object data belongs to the startup group. The request generation circuit generates the activation request data by solving a logical OR of all the activation object data extracted during the acquisition period. The activation determination circuit is configured to select the node associated with the activation target data for which a result of performing a logical AND operation with the activation request data is non-zero as the activation target node.

10. The relay device according to claim 7, characterized in that: The signal transmission unit is configured to extract the activation target data from a data area of ​​a communication frame transmitted in the communication line, and output the extracted activation target data to the wake-up control unit as table update data. The wakeup control unit further includes a table updating unit that updates the activation information table using the table update data.

11. The relay device according to claim 7, characterized in that: The startup information table has multiple types. The signal transmission unit is configured to extract device status data indicating the status of a device of a vehicle equipped with the relay device from a data area of ​​a communication frame transmitted in the communication line, and output the extracted device status data to the wake-up control unit. The wakeup control unit is configured to switch the startup information table to be used according to the device status data.

12. The relay device according to claim 11, characterized in that: The equipment status data includes at least one of data indicating a type of vehicle, a grade of vehicle, and a delivery location.

13. The relay device according to claim 5, characterized in that: The plurality of communication lines include a mixture of communication lines using different communication protocols. The signal transmission unit has a protocol conversion function.

14. The relay device according to claim 5, characterized in that: The present invention further includes a wireless device configured to receive the wakeup signal from the external device by communicating with the external device.

15. The relay device according to claim 7, characterized in that: The plurality of communication lines at least include the communication line using the CAN protocol, The wake-up control unit comprises: a data extraction unit that extracts the activation object data of the request source node set in the data area of ​​the CAN frame indicating that the wake-up signal is the wake-up signal in the frame header area, and outputs the data to the request generation circuit; as well as The wake-up signal generating unit is configured to generate the CAN frame in which the wake-up signal is indicated in the frame header area and the start request data acquired from the request generating circuit is set in the data area, and transmit the frame to the communication line using the CAN protocol.

Images