METHOD OF CONTROLLING COMMUNICATION OVER A LOCAL INTERCONNECT NETWORK BUS

Abstract

A method of controlling communication over a Local Interconnect Network (LIN) bus is provided. The method comprises a redundancy master node detecting whether or not a first master node responds to data transmitted over the LIN bus; wherein in case the first master node does not respond, the redundancy master node will act as master node on the LIN bus.

Claims

1. A method of controlling communication over a Local Interconnect Network, LIN, bus, the method comprising: a redundancy master node detecting whether or not a first master node responds to data transmitted over the LIN bus; wherein in case the first master node does not respond, the redundancy master node acts as master node on the LIN bus.

2. The method of claim 1, wherein the detecting comprises: detecting a wakeup frame being transferred on the LIN bus; and detecting whether or not the first master node responds to the wakeup frame within a set time period (T); wherein in case the first master node does not respond within the set time period (T), the redundancy master node acts as master node on the LIN bus.

3. The method of claim 2, wherein the redundancy master node acts as the master node during a current LIN bus communication cycle and again detects whether or not the first master node responds to a next issued wakeup frame within the set time period (T) to determine whether to continue to act a master node on the LIN bus.

4. The method of claim 2, further comprising: detecting whether or not the first master node has failed to respond to the wakeup frame within a set time period (T) for a set number (N) of consecutive wakeup frames having been transferred on the LIN bus; wherein in case the set number (N) has been reached, the redundancy master node acts as master node on the LIN bus.

5. The method of claim 1, wherein in case the first master node responds to data transmitted over the LIN bus, the redundancy master node remains silent or acts as a slave node on the LIN bus.

6. The method of claim 1, wherein the first master node and the redundancy master node further are interconnected via a Controller Area Network, CAN, bus over which the redundancy master node receives a message from the first master node that the first master node is ready to resume a role as master node on the LIN bus.

7. A computer program comprising computer-executable instructions for causing a redundancy master node to perform the steps recited in claim 1 when the computer-executable instructions are executed on a processing unit included in the redundancy master node.

8. A computer program product comprising a computer readable medium, the computer readable medium having the computer program according to claim 7 embodied thereon.

9. A redundancy master node configured to control communication over a Local Interconnect Network, LIN, bus, the redundancy master node comprising a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby the redundancy master node is operative to: detect whether or not a first master node responds to data transmitted over the LIN bus; wherein in case the first master node does not respond, the redundancy master node acts as master node on the LIN bus.

10. The redundancy master node of claim 9, further being operative to, when detecting whether or not the first master node responds to data transmitted over the LIN bus: detect a wakeup frame being transferred on the LIN bus; and to detect whether or not the first master node responds to the wakeup frame within a set time period (T); wherein in case the first master node does not respond within the set time period (T), the redundancy master node acts as master node on the LIN bus.

11. The redundancy master node of claim 10, wherein the redundancy master node is operative to act as the master node during a current LIN bus communication cycle and again detect whether or not the first master node responds to a next issued wakeup frame within the set time period (T) to determine whether to continue to act as master node on the LIN bus.

12. The redundancy master node of claim 10, further being operative to: detect whether or not the first master node has failed to respond to the wakeup frame within a set time period (T) for a set number (N) of consecutive wakeup frames having been transferred on the LIN bus; wherein in case the set number (N) has been reached, the redundancy master node acts as master node on the LIN bus.

13. The redundancy master node of claim 9, wherein in case the first master node responds to data transmitted over the LIN bus, the redundancy master node is operative to remain silent or act as a slave node on the LIN bus.

14. The redundancy master node of claim 9, wherein the first master node and the redundancy master node further are configured to be interconnected via a Controller Area Network, CAN, bus over which the redundancy master node is operative to receive a message from the first master node that first master node is ready to resume role as master node on the LIN bus.

15. A vehicle comprising a LIN network to which the redundancy master node of claim 9 is connected.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Aspects and embodiments are now described, by way of example, with reference to the accompanying drawings, in which:

[0011] FIG. 1 illustrates a motor vehicle comprising an ECU controlling a plurality of components;

[0012] FIG. 2 illustrates a prior art LIN network;

[0013] FIG. 3 illustrates a motor vehicle comprising a plurality of ECU master nodes according to an embodiment;

[0014] FIG. 4 illustrates a LIN network according to an embodiment;

[0015] FIG. 5 shows a flowchart illustrating a method of controlling communication over a LIN bus according to an embodiment;

[0016] FIG. 6 shows a flowchart illustrating a method of controlling communication over the LIN bus according to a further embodiment;

[0017] FIG. 7 shows a flowchart illustrating a method of controlling communication over the LIN bus 206 according to still a further embodiment;

[0018] FIG. 8 illustrates a LIN network according to a further embodiment; and

[0019] FIG. 9 illustrates a redundancy master node according to an embodiment.

DETAILED DESCRIPTION

[0020] The aspects of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown.

[0021] These aspects may, however, be embodied in many different forms and should not be construed as limiting; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and to fully convey the scope of all aspects of invention to those skilled in the art. Like numbers refer to like elements throughout the description.

[0022] FIG. 1 illustrates a motor vehicle 100 in the form of car. The vehicle 100 is typically equipped with an Electronic Control Unit (ECU, 101), which may be implemented by one or more microprocessors executing appropriate software for controlling various systems and components in the vehicle. A car may contain a number of interconnected ECUs for controlling all properties of the car, thereby providing for instance a brake control module (BCM), a speed control module (SCM) or a battery management system (BMS).

[0023] The ECU 101 is interconnected with various components via a LIN bus, such as components providing functionality relating to locks 102, brakes 103, lighting 104, battery 105, etc. Each component may have its own ECU (or similar device) controlling the associated component and communicating over the LIN bus with the master ECU 101. For instance, the lock module 102 is typically a mechanical device for physically locking/unlocking one or more doors of the car, which mechanical lock module is connected to an ECU-type device, i.e. a lock control module, from which it receives signals for a door to lock/unlock, while e.g. brake functionality generally is controlled by the BCS and battery functionality it controlled by the BMS.

[0024] The ECU 101 may further by equipped with an interface for wireless transmission of data, for instance for wireless communication of various parameters and data and/or measured properties of the vehicle 100 to a remote location.

[0025] Individual components may also be equipped with an interface for wireless transmission of data. For instance, the lock module 102 (or a node in communication with the lock module) may be equipped with a Bluetooth or Near-Field Communication (NFC) interface for wireless communication with a car key, a smart phone or an NFC card to allow a user to lock/unlock the vehicle 100.

[0026] FIG. 2 illustrates a LIN network 110 formed by a master nodethe ECU 101and four slave nodesthe locks 102, brakes 103, lighting 104 and battery 105all interconnected via a LIN bus 106.

[0027] Now, in a prior art LIN network no as that shown in FIG. 2, only one master node is allowed to be connected to the LIN bus 106. All messages sent over the LIN bus 106 are initiated by the master node with at most one slave node replying to a message identifier addressing a particular slave node on the bus. The master node can also act as a slave node by replying to its own messages.

[0028] The LIN protocol specifies a sleep-mode and an active mode bus state, where all LIN nodes are requested to be in active state if data is on the bus. After a specified timeout, the nodes enter sleep mode and will be released back to active state by a wakeup frame. This frame may be sent by any node requesting activity on the bus, either the LIN Master following its internal schedule, or one of the attached LIN Slaves being activated by its internal software application. After all nodes are awakened, the master node continues to schedule data on the bus.

[0029] However, if the ECU master node 101 fails, it is not possible to provide the functionality of the slave nodes 102-105, since all communication over the LIN bus 106 is initiated by the master node 101.

[0030] This is problematic since, for instance, assuming that a user wants to unlock the vehicle by sweeping her NFC-capable car key over the lock module 102. The lock module 102 will thus, after having received a message from the ECU 101 addressing the lock module 102 thereby allowing the lock module 102 to use the bus 106, transmit a message to the ECU 101 over the LIN bus 106 asking the ECU 101 to authenticate credentials transmitted over the NFC interface by the car key.

[0031] If the ECU 101 can verify the correctness of the credentials, a message is transmitted over the LIN bus 106 to the lock module 102 which accordingly will unlock the doors of the vehicle 100.

[0032] However, if the ECU 101 for some reason does not function correctly, a lock control module controlling the lock module 102 will not receive the message that the credentials are authenticated. This will have as a consequence that the user cannot unlock the vehicle 100.

[0033] This is solved in an embodiment illustrated with reference to FIG. 3 where the vehicle 100 is illustrated to comprise a LIN network formed by a first master nodea first ECU 201aand four slave nodeslock control module 202, brake control module 203, lighting control module 204 and battery control module 205and further a redundancy master node in the form of a second ECU 201b all interconnected via a LIN bus.

[0034] FIG. 4 illustrates the LIN network 210 implemented in the vehicle 100 of FIG. 3 comprising the first ECU master node 210a, the redundancy ECU master node 201b and the four slave nodes; the lock control module 202, brake control module 203, lighting control module 204 and battery control module 205, all interconnected via a LIN bus 206.

[0035] Now, to comply with LIN network requirements, a collision avoidance mechanism is required if a redundancy ECU master node 201b is to be connected to the LIN bus 206 for possibly taking over the role as master node from the first ECU master node 201a.

[0036] FIG. 5 shows a flowchart illustrating a method of controlling communication over the LIN bus 206 to which the redundancy LIN master node 201b is connected.

[0037] It is to be noted that the two nodes 201a, 201b never will act as master nodes simultaneously but are used for redundancy purposes; either the one or the other will assume the role of a master node.

[0038] Now, in a first step S101, the redundancy ECU master node 201b, will monitor communication on the LIN bus 206. If the first ECU master node 201a does not respond to data being transmitted over the LIN bus 206, the first ECU master node 201a is assumed to not function correctly, in which case the redundancy ECU master node 201b will act as a single master node on the LIN bus 206. In contrast, if the first ECU master node 201a responds to data being transferred over the LIN bus 206, the redundancy ECU master node 201b will remain silent, as the first ECU master node 201b indeed appears to function correctly. As an alternative to remaining silent, the redundancy ECU master node 201b may act as a slave node on the LIN bus 206.

[0039] Advantageously, with this embodiment, in case the regular master node failsi.e. the first ECU master node 201athe redundancy ECU master node 201b will assume the role of single master node on the LIN bus 206. Thereby, redundancy is provided for, and the LIN network 210 will function seamlessly even if one master node suffers from a failure.

[0040] The LIN protocol is well-known and will thus not be described in any detail herein. However, the master node transmits a header consisting of a break signal followed by synchronization and identifier fields uniquely addressing each slave node on the LIN bus 206. The slave nodes respond with a data frame that consists of between 2, 4 and 8 data bytes plus 3 bytes of control information.

[0041] FIG. 6 shows a flowchart illustrating a method of controlling communication over the LIN bus 206 according to an embodiment where the redundancy ECU master node 201b detects in step S101a if a wakeup frame is transferred over the LIN bus 206. This wakeup frame may be issued by any one of the nodes connected to the LIN bus 206.

[0042] In the LIN protocol, all nodes should wakeup within 100 ms from the end of the wakeup frame. The first master node Zola must transmit data over the LIN bus 206 within 150 ms from the end of the wakeup frame. Hence, regardless of whether any of the slave nodes 202-205 issues the wakeup frame or the first ECU master node Zola itself issues the wakeup frame, the first ECU master node Zola must respond to the issued wakeup frame by transmitting data over the LIN bus within 150 ms.

[0043] The redundancy ECU master node 201b then detects in step S101b whether the first ECU master node Zola responds to the wakeup frame within a set time period T, preferably being 150 ms to comply with the LIN protocol even though other timings may be envisaged.

[0044] In case no response is detected from the first ECU master node Zola on the LIN bus 206 within the exemplified set time period T=150 ms, the redundancy ECU master node 201b will act as a single master node on the LIN bus. In case a reply indeed is received within the set time period T, the redundancy ECU master node 201b will not act as the master node on the LIN bus 206 and accordingly remain silent and not transmit data over the LIN bus 206 since the first ECU master node 201a will continue to assume the role as the single master node on the LIN bus 206.

[0045] In an embodiment, the redundancy ECU master node 201b assumes the role as the master node on the LIN bus 206 during a current, ongoing LIN bus communication cycle. After the nodes again go into sleep state and subsequently wake up, the redundancy ECU master node 201b will again perform steps S101a and S101b for detecting whether the first ECU master node 201a functions as expected or not.

[0046] Hence, the redundancy ECU master node 201b acts as the master node for a current LIN bus communication cycle and again detects whether or not the first ECU master node 201a responds to a next issued wakeup frame within the set time period T. As long as the first ECU master node 201a does not signal that it is capable of acting as master node on the LIN bus 206, the redundancy ECU master node 201b will assume the responsibility as master node.

[0047] FIG. 7 shows a flowchart illustrating a method of controlling communication over the LIN bus 206 according to an embodiment where the first ECU master node 201a must fail to respond within the set time period T=150 ms an issued wakeup frame for a set number N of consecutively issued wakeup frames. In the following example, N=.sub.3.

[0048] As previously, in step S101a, the redundancy ECU master node 201b detects if a wakeup frame is being transferred over the LIN bus 206. The redundancy ECU master node 201b then detects in step S101b whether the first ECU master node 201a responds to the wakeup frame within the time period T=150 ms.

[0049] In case no response is detected from the first ECU master node 201a on the LIN bus 206 within the set time period T=150 ms, the redundancy ECU master node 201b detects in step S101c whether or not this is the third (N=.sub.3) wakeup frame to which the first ECU mater node fails to respond within T=150 ms.

[0050] If so, the redundancy ECU master node 201b will act as master node on the LIN bus 206. In case N=3 has not yet been reached, the redundancy ECU master node 201b will detect a further wakeup frame to which the first ECU master node 201a fails to respond within T=150 ms. Should the first ECU master node 101a respond adequately before N=.sub.3 is reached, the redundancy ECU master node 201b will remain silent on the LIN bus 206.

[0051] As in FIG. 6, if the first ECU master node 201a indeed responds within the set time period T in step S101b, the redundancy ECU master node 201b will not act as the master node on the LIN bus 206 and accordingly remain silent and not transmit data over the LIN bus 206 since the first ECU master node Zola will continue to assume the role as the single master node on the LIN bus 206.

[0052] FIG. 8 illustrates the LIN network 210 of FIG. 4 but where the first ECU master node Zola and the redundancy ECU master node 201b is interconnected by means of a Controller Area Network (CAN) bus 207 according to an embodiment.

[0053] In this embodiment, the CAN bus 207 is used by the first ECU master node Zola to signal, after the redundancy ECU master node 201b has assumed responsibility as master node on the LIN bus 206, that the first ECU master node Zola is ready to resume the role as master node on the LIN bus 206. After the redundancy ECU master node 201b has received a message over the CAN bus 207 that the first ECU master node Zola is ready to again act as the master node on the LIN bus 206, the redundancy ECU master node 201b will revert to remaining silent on the LIN bus 206.

[0054] FIG. 9 illustrates a redundancy master node 2o1b according to an embodiment. The steps of the method performed by the redundancy master node 201b of controlling communication over a LIN bus according to embodiments are in practice performed by a processing unit 220 embodied in the form of one or more microprocessors arranged to execute a computer program 221 downloaded to a suitable storage volatile medium 222 associated with the microprocessor, such as a Random Access Memory (RAM), or a non-volatile storage medium such as a Flash memory or a hard disk drive. The processing unit 220 is arranged to cause the redundancy master node 2o1b to carry out the method according to embodiments when the appropriate computer program 21 comprising computer-executable instructions is downloaded to the storage medium 222 and executed by the processing unit 220. The storage medium 222 may also be a computer program product comprising the computer program 221. Alternatively, the computer program 221 may be transferred to the storage medium 222 by means of a suitable computer program product, such as a Digital Versatile Disc (DVD) or a memory stick. As a further alternative, the computer program 221 may be downloaded to the storage medium 222 over a network. The processing unit 220 may alternatively be embodied in the form of a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), etc.

[0055] The aspects of the present disclosure have mainly been described above with reference to a few embodiments and examples thereof. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the invention, as defined by the appended patent claims.

[0056] Thus, while various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.