JP2019009678A - On-vehicle communication network system - Google Patents

Abstract

To provide an on-vehicle communication network system which can simultaneously manage the wake-up or the sleep of a plurality of electronic control units having different communication specifications, without an increase of a bus load.SOLUTION: Each of first ECUs 101-103, which conform to all NM management specifications of a plurality of communication specifications, includes a CPU 114 which transmits, to a communication bus 5, NM frames which respectively store data representing a switchover instruction from either of a wake-up state and a sleep state in the plurality of NM management specifications, to a plurality of NM management specification data areas which are divided from a data area. Each of second to fourth ECUs 201-203, 301-303, 401-403 not conforming to a part of the plurality of NM management specifications, includes a CPU 214 which receives the NM frames from the communication bus 5, and reads data in the NM management specification data area corresponding to the conforming NM management specification to switch over from either of the wake-up and sleep states.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an in-vehicle communication network system.

  Conventionally, as an in-vehicle communication network system, for example, the one described in Patent Document 1 is known. In this in-vehicle communication network system, wake-up / sleep management using an NM (Network Management) frame is realized without providing a gateway device between electronic control units having different communication specifications. That is, an electronic control unit conforming to all of the first communication specification and the second communication specification different from each other is provided, and the NM frame and the second communication conforming to the first communication specification are provided from the electronic control unit to the communication bus. NM frames conforming to the specification are sequentially transmitted. Thereby, the electronic control unit of the first communication specification and the electronic control unit of the second communication specification respectively receive the NM frame conforming to the corresponding communication specification and wake up / sleep.

Japanese Patent Laid-Open No. 2006-134855

  By the way, in Patent Document 1, it is necessary to generate NM frames for different communication specifications and sequentially transmit them to the communication bus, which necessitates an increase in bus load (communication bus usage rate).

  An object of the present invention is to provide an in-vehicle communication network system capable of simultaneously managing wake-up or sleep of a plurality of electronic control units having different communication specifications without increasing a bus load.

  An in-vehicle communication network system that solves the above problems includes a plurality of electronic control units and a communication bus to which the plurality of electronic control units are connected, and conforms to all of the NM (Network Management) management specifications of a plurality of communication specifications The first electronic control unit, which is each of the part of the electronic control units that perform, is in a state of either wake-up or sleep in the plurality of NM management specifications in a plurality of NM management specification data areas divided into data areas A first control unit that transmits NM frames each storing data indicating an instruction to switch to one of the other states to the communication bus, and that does not comply with a part of the plurality of NM management specifications. A second electronic control unit, each of all the electronic control units, is connected to the N from the communication bus. A second control unit that receives a frame, reads the data in the NM management specification data area corresponding to the NM management specification that conforms to the frame, and switches from one of the wake-up and sleep states to the other state Have

  According to this configuration, when the first control unit transmits the NM frame to the communication bus, the second control unit receives the NM frame from the communication bus and receives the second electronic control unit. Is switched from one of the wake-up state and the sleep state to the other state. Thus, even if the second electronic control unit does not conform to a part of the plurality of NM management specifications, that is, does not conform to the same NM management specification, the first electronic control unit When one NM frame is transmitted by the unit, the state is switched from one of the wake-up state and the sleep state to the other state. Therefore, the wake-up or sleep of the plurality of electronic control units having different communication specifications can be managed simultaneously without increasing the bus load.

  Note that one of the plurality of NM management specifications may not conform to all the NM management specifications that are already included in the in-vehicle communication network system. In other words, if it is a specification that can manage wake-up / sleep by receiving specific data, a specification that does not comply with all the NM management specifications that are already included in the in-vehicle communication network system is also one NM management specification. Is considered.

  With respect to the in-vehicle communication network system, the second control unit switches from one of the wake-up state and the sleep state to the other state with respect to the first electronic control unit in the NM management specification to which it conforms. It is preferable that the request frame representing the instruction is transmitted to the communication bus, and the first control unit receives the request frame from the communication bus and transmits the NM frame.

  According to this configuration, when the second control unit of one second electronic control unit transmits the request frame to the communication bus, the first control unit transmits the request frame from the communication bus. Receive and transmit the NM frame. As a result, all of the other second electronic control units are switched from one of the wake-up state and the sleep state to the other state. In this way, one second electronic control unit wakes up and sleeps all the other second electronic control units together with the first electronic control unit through the first electronic control unit. It is possible to switch from any one state to any other state.

  The present invention has an effect of simultaneously managing wake-up or sleep of a plurality of electronic control units having different communication specifications without increasing the bus load.

The block diagram which shows the electrical constitution about one Embodiment of a vehicle-mounted communication network system. The list figure which shows the relationship between 1st-4th ECU and NM management specification. Explanatory drawing which shows the structure of NM frame. The flowchart which shows the control aspect at the time of the wake-up about the vehicle-mounted communication network system of the embodiment. The flowchart which shows the control aspect at the time of the wake-up about the vehicle-mounted communication network system of the embodiment. The flowchart which shows the control aspect at the time of the sleep about the vehicle-mounted communication network system of the embodiment. The flowchart which shows the control aspect at the time of the sleep about the vehicle-mounted communication network system of the embodiment. The flowchart which shows the control aspect at the time of the wake-up about the vehicle-mounted communication network system of the embodiment.

Hereinafter, an embodiment of the in-vehicle communication network system will be described.
As shown in FIG. 1, the in-vehicle communication network system 1 is mounted on a vehicle such as an automobile, for example, and a CAN (Controller Area Network) is applied. The in-vehicle communication network system 1 can be used, for example, for data transfer between information devices, between power train devices, and between body devices.

  The in-vehicle communication network system 1 includes a first ECU 101, 102, 103 as a first electronic control unit, a second ECU 201, 202, 203 as a second electronic control unit, and a third ECU 301, 302, 303. And the fourth ECUs 401, 402, and 403, and the communication bus 5 that connects the first to fourth ECUs 101 to 103, 201 to 203, 301 to 303, and 401 to 403 by wire.

  1st ECU101-103 comprises the 1st network 10 based on all the 1st-3rd communication specifications. On the other hand, the second ECUs 201 to 203 constitute the second network 20 that conforms only to the first communication specification, and the third ECUs 301 to 303 correspond to the third communication specification that conforms only to the second communication specification. The network 30 is configured, and the fourth ECUs 401 to 403 configure the fourth network 40 that conforms only to the third communication specification.

  The first ECU 101 includes a communication transceiver 111 and a microcontroller 112. The microcontroller 112 includes a communication circuit 113, a CPU 114 as a first control unit that performs overall control of various processes, a ROM 115 in which various programs and data executed by the CPU 114 are written, and a work area of the CPU 114 when the programs are executed. Hardware such as the RAM 116 is mounted. The program written in the ROM 115 is created so as to comply with all of the first to third communication specifications.

  The communication transceiver 111 is connected to the communication bus 5 and transmits data from the communication circuit 113 to the communication bus 5 and receives data from the communication bus 5 and inputs it to the communication circuit 113 under the control of the communication driver. . As a result, the communication transceiver 111 transmits and receives data between the first to fourth ECUs 102, 103, 201 to 203, 301 to 303, and 401 to 403. When transmitting data, the communication transceiver 111 sends an inverted signal to the two communication lines (CANH, CANL) of the communication bus 5. When receiving data, the communication transceiver 111 determines whether the data on the communication bus 5 is “1” or “0” from the voltage difference between the two communication lines of the communication bus 5. .

  The communication circuit 113 is connected to the communication transceiver 111 and performs communication between the first to fourth ECUs 102, 103, 201 to 203, 301 to 303, and 401 to 403 via the communication bus 5. The communication circuit 113 transmits data from the CPU 114 from the communication transceiver 111, receives data input from the communication transceiver 111, and inputs the data to the CPU 114.

  The CPU 114 executes processing for controlling the entire first ECU 101 such as communication processing executed by the communication circuit 113. The CPU 114 operates according to the first to third communication specifications by executing the program written in the ROM 115. For example, the CPU 114 controls the operation of the first ECU 101, such as switching from one of the wake-up and sleep states to the other. When the CPU 114 switches from one of the wake-up state and the sleep state to the other state, the CPU 114 generates an NM frame indicating a corresponding switching instruction and inputs the NM frame to the communication circuit 113. The communication circuit 113 transmits the NM frame input to the CPU 114 from the communication transceiver 111.

Since the configuration and operation of the first ECUs 102 and 103 are the same, the description thereof is omitted.
The second ECU 201 also includes a communication transceiver 211 and a microcontroller 212 according to the first ECU 101. The microcontroller 212 is equipped with hardware such as a communication circuit 213, a CPU 214 as a second control unit, a ROM 215, and a RAM 216. However, the program written in the ROM 215 is created so as to comply only with the first communication specification.

  The CPU 214 executes processing for controlling the entire second ECU 201 such as communication processing executed by the communication circuit 213. The CPU 214 operates according to the first communication specification by executing the program written in the ROM 215. For example, the CPU 214 controls the operation of the second ECU 201 such as switching from one of the wake-up and sleep states to the other. This control is activated by inputting the NM frame transmitted from the first ECU 101. In addition, the CPU 214 generates a request frame indicating an instruction to switch the first ECU 101 from one of the wake-up state and the sleep state to the other state, and inputs the request frame to the communication circuit 213. The communication circuit 213 transmits the request frame input to the CPU 214 from the communication transceiver 211.

Note that the CPU 114 of the first ECU 101 is configured to generate an NM frame by receiving a request frame transmitted from the second ECU 201.
Since the configuration and operation of the second ECUs 202 and 203 are the same, the description thereof is omitted.

  Since the configurations and operations of the third ECUs 301 to 303 and the fourth ECUs 401 to 403 are the same, the same reference numerals as those of the second ECU 201 are assigned to the internal circuits (communication transceivers and the like). However, the program written in the ROM 215 of the third ECUs 301 to 303 is created so as to comply only with the second communication specification, and the program written in the ROM 215 of the fourth ECU 401 to 403 is the third communication. It is created to comply only with the specification.

  Here, the first communication specification conforms to the first NM management specification, and the second communication specification conforms to the second NM management specification. The third communication specification does not conform to all of the first to second NM management specifications and does not support the NM function. However, the third communication specification is a specification that can manage wake-up / sleep by receiving specific data (hereinafter referred to as “management source correspondence”). It can be said that the third communication specification that does not support the NM function conforms to one NM management specification that is different from the first and second NM management specifications because it corresponds to the management source. That is, in the present embodiment, a specification that does not comply with all the NM management specifications (first to second NM management specifications) that are included in the in-vehicle communication network system 1 is also regarded as one NM management specification.

  Therefore, as shown in FIG. 2, the first ECUs 101 to 103 comply with all of the first to second NM management specifications and the management source correspondence. On the other hand, the second ECUs 201 to 203 comply only with the first NM management specification, the third ECUs 301 to 303 conform only to the second NM management specification, and the fourth ECUs 401 to 403. Is compliant with managed sources only.

  In the following, when any one of the first ECUs 101 to 103 is described as a representative, it is referred to as “first ECU 100”, and when any one of the second ECUs 201 to 203 is described as a representative. This is described as “second ECU 200”. Similarly, when any one of the third ECUs 301 to 303 is described as a representative, “third ECU 300” is described, and when any one of the fourth ECUs 401 to 403 is described as a representative This is referred to as “fourth ECU 400”.

  As shown in FIG. 3, the CPU 114 of the first ECU 100 generates and transmits an NM frame 50 when a predetermined condition is satisfied. The NM frame 50 includes a CAN ID 51 indicating that the frame is related to wakeup / sleep management and a data area 52 of, for example, 8 bytes. The data area 52 is divided into a plurality of NM management specification data areas 52a, 52b, 52c, and 52d in order from the top.

  The first NM management specification data area 52a occupies 2 bytes, and in the first NM management specification, data (indication of switching from one of the wake-up and sleep states to the other state) For example, a communication management flag) is stored. The next NM management specification data area 52b occupies 2 bytes, and in the second NM management specification, data (indication of switching from one of the wake-up and sleep states to the other state) For example, a communication management flag) is stored. The last NM management specification data area 52d occupies 1 byte, and in the third communication specification (corresponding to the management source), an instruction to switch from one of the wake-up and sleep states to the other state Is stored.

  The CPU 214 of the second ECU 200 that has input the NM frame 50 reads the data in the NM management specification data area 52a corresponding to the first NM management specification to which the NM frame 50 is compliant, and either wakes up or sleeps the second ECU 200. Switch from one state to the other. Similarly, the CPU 214 of the third ECU 300 that has input the NM frame 50 reads the data of the NM management specification data area 52b corresponding to the second NM management specification to which it conforms, and wakes up and sleeps the third ECU 300. Switch from one state to the other. The CPU 214 of the fourth ECU 400 that has input the NM frame 50 reads data in the NM management specification data area 52d corresponding to the third communication specification (corresponding to the management source), and causes the fourth ECU 400 to either wake up or sleep. Switch from one state to the other.

  As described above, even if the second to fourth ECUs 200 to 400 do not comply with a part of the plurality of NM management specifications, that is, do not comply with the same NM management specification, the first ECU 100 performs one operation. The transmission of one NM frame 50 switches from one of the wake-up and sleep states to the other.

  On the other hand, each CPU 214 of the second to fourth ECUs 200 to 400 generates and transmits a request frame (not shown) according to the NM management specification when a predetermined condition is satisfied. This request frame represents an instruction to switch the first ECU 100 from one of the wake-up and sleep states to the other state.

  The CPU 114 of the first ECU 100 generates and transmits the NM frame 50 by inputting the request frame transmitted from any one of the second to fourth ECUs 200 to 400. As described above, as described above, all of the other second to fourth ECUs 200 to 400 are switched from one of the wake-up state and the sleep state to the other state.

Next, a control mode of switching from the sleep state to the wake-up state by the CPUs 114 and 214 of the first to fourth ECUs 100 to 400 will be described.
As shown in FIG. 4, the CPU 114 of the first ECU 100 generates and transmits an NM frame 50 in step S11 when the process is started, for example, when the ignition switch of the vehicle is switched from OFF to ON, and ends the process. To do. This NM frame 50 represents an instruction to switch from the sleep state to the wake-up state.

  As shown in FIG. 5, the CPU 214 of each of the second to fourth ECUs 200 to 400 performs processing by inputting an NM frame 50 (for example, an edge generated when the voltage applied to the communication bus 5 changes). Is activated, the NM frame 50 is received in step S21. In step S22, the CPU 214 reads data in the NM management specification data areas 52a to 52d corresponding to the NM management specification to which the CPU 214 complies, and in step S23, switches to the wake-up state based on the data and ends the process.

Next, a control mode of switching from the wake-up state to the sleep state by the CPUs 114 and 214 of the first to fourth ECUs 100 to 400 will be described.
As shown in FIG. 6, the CPU 114 of the first ECU 100 generates and transmits the NM frame 50 in step S31 when the process is started, for example, when the ignition switch of the vehicle is switched from on to off, and ends the process. To do. This NM frame 50 represents an instruction to switch from the wake-up state to the sleep state.

  As shown in FIG. 7, the CPU 214 of each of the second to fourth ECUs 200 to 400 performs processing by inputting an NM frame 50 (for example, an edge generated when the voltage applied to the communication bus 5 changes). Is activated, the NM frame 50 is received in step S41. In step S42, the CPU 214 reads data in the NM management specification data areas 52a to 52d corresponding to the NM management specification to which the CPU 214 complies. In step S43, the CPU 214 switches to the sleep state based on the data and ends the process.

  Next, another control mode of switching from any one of the wake-up and sleep states to the other state by the CPUs 114 and 214 of the first to fourth ECUs 100 to 400 will be described.

  As shown in FIG. 8, when one of the CPUs 214 of the second to fourth ECUs 200 to 400 is activated when a predetermined condition is satisfied, a request frame is generated and transmitted in step S51 and processed. Exit. This request frame represents an instruction to switch from one of the wake-up and sleep states to the other state.

  Along with this, the CPU 114 of the first ECU 100 generates and transmits the NM frame 50 by inputting a request frame (for example, an edge generated when the voltage applied to the communication bus 5 changes). This NM frame 50 represents an instruction for switching from one of the wake-up and sleep states to the other state. That is, the CPU 114 of the first ECU 100 performs the same process as that in FIG. 4 or FIG. 6 except that the process start condition is replaced with the input of the request frame.

Next, the effect of this embodiment will be described.
(1) In this embodiment, when the CPU 114 of the first ECU 100 transmits the NM frame 50 to the communication bus 5, each CPU 214 of the second to fourth ECUs 200 to 400 receives the NM frame 50 from the communication bus 5. Then, the second to fourth ECUs 200 to 400 are switched from one of the wake-up state and the sleep state to the other state. As described above, even if the second to fourth ECUs 200 to 400 do not conform to a part of the plurality of NM management specifications, that is, do not conform to the same NM management specification, the first ECU 100 does not. By the transmission of one NM frame 50, one of the wake-up state and the sleep state is switched to the other state. Therefore, the wake-up or sleep of the first to fourth ECUs 100 to 400 having a plurality of communication specifications can be managed simultaneously without increasing the bus load.

  Alternatively, the first to fourth ECUs 100 to 400 are eliminated by eliminating the time difference that occurs between a plurality of NM frames as in the case of generating NM frames for different communication specifications and sequentially transmitting them to the communication bus 5. It is possible to prevent the wake-up or sleep synchronization from being lost.

  (2) In the present embodiment, when the CPU 214 of one of the second to fourth ECUs 200 to 400 transmits a request frame to the communication bus 5, the CPU 114 of the first ECU 100 receives the request frame from the communication bus 5. The NM frame 50 is transmitted. As a result, all of the other second to fourth ECUs 200 to 400 are switched from one of the wake-up state and the sleep state to the other state. As described above, one second to fourth ECUs 200 to 400 are configured to wake up and sleep all of the other second to fourth ECUs 200 to 400 together with the first ECU 100 through the first ECU 100. It is possible to switch from any one state to any other state.

  (3) In the present embodiment, the fourth ECU 400 that does not support the NM function can also manage wake-up or sleep by reading the data in the NM management specification data area 52d of the NM frame 50.

  (4) In the present embodiment, a plurality of communication specifications can be obtained by an extremely simple method of merely setting the NM management specification data areas 52a to 52d of the NM frame 50 read by the CPUs 214 of the second to fourth ECUs 200 to 400. Since the wake-up or sleep of the first to fourth ECUs 100 to 400 can be managed at the same time, development man-hours and costs can be reduced. For example, it is possible to reduce the development man-hours and costs compared to the case where a program for making the fourth ECU 400 conform to the first NM management specification or the second NM management specification is created.

(5) In this embodiment, the battery consumption can be further reduced by simultaneously managing the wake-up or sleep of the first to fourth ECUs 100 to 400 having a plurality of communication specifications.
In addition, you may change the said embodiment as follows.

In the embodiment, the division of the NM management specification data areas 52a to 52d in the data area 52 is arbitrary, and is not limited to this description.
-In the said embodiment, transmission of the NM frame 50 between 1st ECU101-103 may determine a priority according to CSMA / CD (Carrier Sense Multiple Access / Collision Detection), for example.

  -In the said embodiment, the 1st ECU100 which conforms to all the 1st-2nd NM management specifications and management source correspondence may be one. That is, the first network 10 may be configured with only one first ECU 100.

  In the embodiment, the NM frame 50 that switches only a part of the second to fourth ECUs 200 to 400 from either one of the wake-up state and the sleep state to the other state may be used.

  In the above embodiment, the first ECUs 101 to 103 comply with the entire second to third communication specifications as long as they comply with all of the first to second NM management specifications and the management source correspondence. It does not have to be. That is, the program written in the ROM 115 of the first ECUs 101 to 103 may be created so as to comply only with the second NM management specification and management source support in addition to the first communication specification.

  In the above-described embodiment, each of the first to third ECUs 100 to 300 performs finer NM management (for example, control after wakeup or after sleep such as re-sleep or sleep standby) according to the NM management specification to which the first to third ECUs 100 to 300 comply. You may go.

In the embodiment, at least one of the second ECU 200 and the third ECU 300 may be compliant with management source correspondence.
In the above embodiment, the number of the first ECUs 100 constituting the first network 10 is arbitrary. Similarly, the number of second ECUs 200 constituting the second network 20, the number of third ECUs 300 constituting the third network 30, and the number of fourth ECUs 400 constituting the fourth network 40 are arbitrary. is there.

  -In above-mentioned embodiment, there is no need of ECU which conforms to management source correspondence. That is, it may be an in-vehicle communication network system that conforms to some NM management specification that all ECUs have already established.

-In the said embodiment, if the number of types of different NM management specifications is plural, it is arbitrary.
-In the said embodiment, the vehicle-mounted communication network system to which CAN FD (CAN with Flexible Data rate), FlexRay (trademark), LIN (Local Interconnect Network), etc. were applied may be sufficient. For example, when CAN FD is applied, it is possible to simultaneously manage wake-up or sleep of more types of ECUs having different communication specifications by dividing the data area expanded to 64 bytes into more NM management specification data areas. .

  5 ... communication bus, 50 ... NM frame, 52 ... data area, 52a to 52d ... NM management specification data area, 101 to 103 ... first ECU (electronic control unit, first electronic control unit), 114 ... CPU ( 1st control part), 201-203 ... 2nd ECU (electronic control unit, 2nd electronic control unit), 214 ... CPU (2nd control part), 301-303 ... 3rd ECU (electronic control) Unit, second electronic control unit), 401 to 403... Fourth ECU (electronic control unit, second electronic control unit).

Claims (2)

A plurality of electronic control units;
A communication bus to which the plurality of electronic control units are connected,
A first electronic control unit, which is each of a part of the electronic control units conforming to all of the NM (Network Management) management specifications of a plurality of communication specifications,
NM frames each storing data indicating an instruction to switch from one of the wake-up and sleep states to the other state in the plurality of NM management specifications in a plurality of NM management specification data areas divided into data areas A first control unit for transmitting to the communication bus,
A second electronic control unit that is each of all the other electronic control units not conforming to a part of the plurality of NM management specifications,
Receiving the NM frame from the communication bus, reading the data in the NM management specification data area corresponding to the NM management specification to which the NM frame conforms, and changing from one of the wake-up and sleep states to the other state An in-vehicle communication network system having a second control unit for switching. The in-vehicle communication network system according to claim 1,
The second control unit sends a request frame indicating an instruction to switch from one of the wake-up and sleep states to the other state for the first electronic control unit in the NM management specification to which the second control unit complies. Send to the communication bus,
The in-vehicle communication network system, wherein the first control unit receives the request frame from the communication bus and transmits the NM frame.