System for Data Transmission in a Motor Vehicle, Motor Vehicle and Method

Abstract

A system for data transmission in a motor vehicle includes a central control unit, a first zonal control module, and a first LIN bus. The central control unit includes at least a first LIN master and a second LIN master. The first zonal control module is operably coupled to the central control unit via a first data connection. The first LIN bus is operably coupled to the first zonal control module. A first LIN slave connected to the LIN bus is assigned to the first LIN master, and a second LIN slave connected to the LIN bus is assigned to the second LIN master.

Claims

1.-19. (canceled)

20. A system for data transmission in a motor vehicle, the system comprising: a central control unit comprising at least a first LIN master and a second LIN master; a first zonal control module operably coupled to the central control unit via a first data connection; and a first LIN bus operably coupled to the first zonal control module; wherein a first LIN slave connected to the LIN bus is assigned to the first LIN master, and wherein a second LIN slave connected to the LIN bus is assigned to the second LIN master.

21. The system as claimed in claim 20, further comprising: at least one further zonal control module operably coupled to the central control unit via the first data connection (13, 33); and at least one further LIN bus operably coupled to the further zonal control module, wherein at least one LIN slave assigned to the first LIN master and/or assigned to the second LIN master is connected to the further LIN bus.

22. The system as claimed in claim 21, wherein each zonal control module of the first zonal control module and the at least one further zonal control module is configured to filter out headers of the first LIN master and the second LIN master transmitted via the first data connection which are addressed to LIN slaves connected to a respective LIN bus of the zonal control module.

23. The system as claimed in claim 20, wherein a single LIN bus is coupled to the first zonal control module.

24. The system as claimed in claim 20, wherein the first zonal control module is configured to control a temporal sequence in which headers of the first LIN master and the second LIN master received on the first zonal control module are transmitted from the first zonal control module onto the first LIN bus according to a communication behavior.

25. The system as claimed in claim 24, wherein the communication behavior provides synchronous transmission in which a LIN master transmits no further header as long as said LIN master has not received a response corresponding to a most recently transmitted header which is transmitted from a LIN slave via the first LIN bus, the first zonal control module, and the first data connection to the LIN master.

26. The system as claimed in claim 24, wherein: the communication behavior provides asynchronous transmission in which a LIN master transmits a further header even if the LIN master has not received a response corresponding to a most recently transmitted header, and the first zonal control module transmits the response together with an associated header ID via the first data connection to the LIN master in order to enable an assignment of the response to the most recently received header on the LIN master.

27. The system as claimed in claim 20, wherein the system has a plurality of LIN masters in the central control unit and a plurality of zonal control modules with respective LIN buses.

28. The system as claimed in claim 27, wherein a quantity of LIN buses of the system is greater than a quantity of LIN masters of the system.

29. The system as claimed in claim 20, wherein the first zonal control module has a buffer memory configured to temporarily store a header received from a LIN master until the first LIN bus is available for transmission of the header received from the LIN master.

30. The system as claimed in claim 20, wherein the first zonal control module is configured to transmit error information relating to the first LIN bus and/or the first data connection to the first LIN master and/or the second LIN master of the central control unit.

31. The system as claimed in claim 20, wherein a data transmission speed of the first data connection between the central control unit and the first zonal control module is higher than a data transmission speed of the first LIN bus.

32. The system as claimed in claim 20, wherein the first data connection is configured according to an Ethernet standard, a CAN standard, a FlexRay standard, a radio-based transmission standard, a PCI Express standard or a home network standard.

33. The system as claimed in claim 20, wherein at least one of a group including the first LIN master, the second LIN master, the first LIN slave and the second LIN slave includes hardware-supported microcontrollers.

34. The system as claimed in claim 20, wherein the system is configured to transmit a frame via the first LIN bus and header information and response information corresponding to the frame via the first data connection within a time duration of a predefined time slot for data transmission of a frame via the first LIN bus.

35. The system as claimed in claim 20, wherein the system is configured to transmit header information from both the first LIN master and the second LIN master in a common data packet via the first data connection.

36. The system as claimed in claim 20, wherein one or both of a legacy bus and a discrete signal line with a corresponding control unit is further connected to the first zonal control module, and/or the system has a further zonal control module with one or both of a legacy bus and a discrete signal line with a corresponding control unit, wherein the system is designed to transmit information from the legacy bus via the first data connection to the central control unit.

37. A motor vehicle having a system as claimed in claim 20, wherein at least two zonal control modules of the system are arranged in each case in different zones of the motor vehicle.

38. A method for activating at least a first LIN slave and a second LIN slave which are connected to a common LIN bus, the method comprising: transmitting first header information from a first LIN master to the first LIN slave via the common LIN bus; transmitting second header information from a second LIN master to the second LIN slave via the common LIN bus; receiving response information from the first LIN slave corresponding to the first header information on the first LIN master, and receiving response information from the second LIN slave corresponding to the second header information on the second LIN master.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Exemplary embodiments are explained in detail below with reference to the attached figures, in which:

[0056] FIG. 1 shows a schematic example of a system having a central control unit and a zonal control module;

[0057] FIG. 2 shows a flow diagram of a method for activating a first LIN slave and a second LIN slave;

[0058] FIG. 3 shows a schematic example of a zonal system having four zonal control modules and three LIN masters;

[0059] FIG. 4 shows a schematic example of a system having a zonal control module to which two LIN buses are connected;

[0060] FIG. 5a, b show an example of a data transmission in a zonal system having synchronous operation;

[0061] FIG. 6 shows an example of a data transmission in a zonal system in asynchronous operation;

[0062] FIG. 7 shows an example of a conventional system having a plurality of LIN buses;

[0063] FIG. 8 shows an example of a transmission of header information and response information by means of tunnelling via a first data connection as a backbone bus;

[0064] FIG. 9 shows an example of a transmission of a plurality of frames via the first data connection to a plurality of LIN buses using a time offset; and

[0065] FIG. 10 shows a schematic example of a system having a central control unit and a zonal control module to which two different legacy buses are connected.

DETAILED DESCRIPTION

[0066] Different exemplary embodiments will now be described in detail with reference to the attached drawings in which some exemplary embodiments are shown. The thickness dimensions of lines, layers and/or regions may be shown exaggeratedly in the figures for the sake of clarity. In the following description of the attached figures which merely show some exemplary embodiments, the same reference signs may denote the same or comparable components.

[0067] An element which is referred to as connected or coupled to another element can be directly connected or coupled to the other element or intermediate elements can be present. Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning that an average person skilled in the art in the field to which the exemplary embodiments relate attributes to them.

[0068] FIG. 1 shows a schematic example of a system 10 for data transmission, for example in a motor vehicle. The system comprises a central control unit 11 in which at least a first LIN master 11a and a second LIN master 11b are formed. The system 10 further comprises a zonal control module 12 which is coupled to the central control unit 11 by means of a first data connection 13. The system 10 further comprises a LIN bus 14 which is coupled to the zonal control module 12. A first LIN slave 15a connected to the LIN bus 14 is assigned to the first LIN master 11a, and a second LIN slave 15b connected to the LIN bus 14 is assigned to the second LIN master 11b. The system 10 can be used e.g. in motor vehicles.

[0069] Since it is possible by means of the proposed system 10 to arrange slaves 15a, 15b of different masters 11a, 11b on a common LIN bus 14, the system 10 can enable a reduction in a cable requirement for LIN buses. The use of the first data connection 13 can, for example, enable a zonalization of the LIN buses of a system 10, e.g. a LIN bus can thereby be arranged in each case in required zones only, said LIN buses being connected in each case to the central control unit (e.g. an integration platform) via the first data connection 13. A centralization of LIN masters can thus be enabled with simultaneous decentralization or zonalization of the LIN system.

[0070] The provision of the first data connection 13 with a higher data transmission speed than the LIN bus 14 enables the connection of further LIN buses to the zonal control module 12 without their transmission cables having to be routed in each case individually to the central control unit 11 with the associated LIN masters 11a, 11b. The system 10 can thereby enable a reduction in a cable requirement in cases where a plurality of LIN buses are used. The first data connection 13 can be used, for example, as a central data connection (e.g. central bus or backbone bus; e.g. Ethernet connection or CAN bus) in order to tunnel LIN information, in particular header information and response information, from the respective LIN bus to the associated LIN masters in the central control unit 11.

[0071] Alternatively, instead of the LIN bus, a different bus system can be provided which has a lower data transmission speed than the first data connection 13.

[0072] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 1 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above or below (e.g. FIG. 2-10).

[0073] FIG. 2 shows a flow diagram of a method 20 for activating a first LIN slave and a second LIN slave. The method 20 comprises transmitting 21 first header information from a first LIN master to the first LIN slave via the common LIN bus and transmitting 22 second header information from a second LIN master to the second LIN slave via the common LIN bus. The method 20 further comprises receiving 23 response information from the LIN slave corresponding to the first header information on the LIN master and receiving 24 response information from the second LIN slave corresponding to the second header information on the second LIN master.

[0074] A method according to the proposed concepts can, for example, quite generally provide that information which is transmitted from the LIN master to the LIN slave comprises a header (e.g. identifier) and/or contents (e.g. data component). According to the method, command information, for example, can therefore also be transmitted from the LIN master to the LIN slave.

[0075] The method can advantageously enable the operation of e.g. a multiplicity of slaves which are assigned to two or more different masters on a single bus, e.g. LIN bus. A reduction in a physically required cable length can be enabled in this way, which is advantageous, particularly in vehicles with limited installation space.

[0076] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 2 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1) or below (e.g. FIG. 3-10).

[0077] FIG. 3 shows a schematic example of a zonal system 30 having four zonal control modules ZM.sub.1 to ZM.sub.4. The zonal control modules ZM.sub.1 to ZM.sub.4 are coupled to a central control unit 31 of the system 30 by means of a first data connection 33, e.g. an Ethernet connection. A LIN bus 34.sub.1 to 34.sub.4 (e.g. zonal LIN bus) is arranged on each of the zonal control modules ZM.sub.1 to ZM.sub.4. A plurality of LIN slaves S.sub.LIN1 to S.sub.LINx which are assigned to different LIN masters M.sub.LIN1 to M.sub.LINx can be connected to each of the zonal LIN buses 34.sub.1 to 34.sub.4. The LIN masters M.sub.LIN1 to M.sub.LINx are arranged in the central control unit 31. A LIN slave S.sub.LIN1, for example, which is assigned to the first LIN master M.sub.LIN1, furthermore a second LIN slave S.sub.LIN2, for example, which is assigned to the second LIN master M.sub.LIN2, and a further LIN slave S.sub.LINx which is assigned to a further, e.g. third, LIN master M.sub.LINx, are coupled to the first LIN bus 34.sub.1. Slaves are also assigned to the masters in each case on other LIN buses. The masters with the assigned slaves form e.g. functional LIN buses, wherein the LIN slaves are connected in each case to zonal LIN buses in a physically distributed manner. All masters of the system can be arranged in the central control unit 31.

[0078] A zonal LIN bus thus differs from a functional LIN bus e.g. in that the functional LIN bus has LIN slaves of a single LIN master only, whereas the zonal LIN bus connects LIN slaves of different LIN masters in one zone of the system. Precisely three LIN masters, for example, can be present in the system 31 having four zones, since this can offer advantages in terms of the bus utilization of the four LIN buses.

[0079] Use of the zonal system 31, for example, can result in a slimmer design of a cable harness in the vehicle. The zones are connected by a backbone bus (e.g. first data connection 31). Buses such as LIN, CAN and FlexRay dock on to zonal modules (e.g. zonal control modules ZM.sub.1 to ZM.sub.4). Other concepts, e.g. in the cable harness of a motor vehicle, use LIN buses which are functionally organized and in which each bus itself runs through the entire vehicle. In other concepts, the cable harness can become very thick and heavy and incurs high costs. According to other concepts, each LIN bus itself runs through the entire vehicle.

[0080] Precisely one LIN bus, or alternatively a plurality of LIN buses, can be connected in each case to a zonal control module ZM.sub.1 to ZM.sub.4. One LIN bus, for example, can be connected in each case to two first zonal control modules ZM.sub.1 and ZM.sub.2, and two LIN buses can be connected in each case to two further zonal control modules ZM.sub.3 and ZM.sub.4. A higher degree of system flexibility can thereby be achieved. Two LIN buses, for example, can be used on one zonal control module if a higher number of LIN information elements is to be transmitted to the LIN slaves of the zone concerned. A LIN bus overload, for example, can thereby be avoided.

[0081] The system 31 comprises the aspects of tunnelling of LIN information via the first data connection 33 and zonalization of the LIN buses. A new assignment of the LIN slaves to the buses takes place in the zonalization so that a plurality of LIN masters can (functionally) access the same physical LIN bus (zonally). The LIN information can be tunneled on the basis of unused time reserves (e.g. tolerance times) in the LIN protocol which are not required if the system is suitably designed. In particular, LIN information can be transmitted via the first data connection 33 to or from a LIN master in inter-frame spaces of the protocol of the LIN buses within a LIN frame.

[0082] As also shown below in FIG. 4, two or more LIN buses can also be connected in each case to the zonal control module shown in FIG. 3. Precisely one LIN bus, for example, can be connected in each case to two of the zonal control modules (as shown in FIG. 3) and two LIN buses can be connected in each case to two other of the zonal control modules (as shown e.g. in FIG. 4).

[0083] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 3 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1-2) or below (e.g. FIG. 4-10).

[0084] FIG. 4 shows a schematic example of a system 40 having a zonal control module ZM to which two LIN buses 44a, 44b are connected. Two or more masters M1, M2 are arranged in a modular control platform MCP (e.g. high-integration platform; e.g. central control unit). A first data connection 43 connects the modular control platform MCP to a zonal module ZM (e.g. zonal integration module; e.g. zonal control unit).

[0085] Slaves S1, S2 which are assigned to the first master M1 or to the second master M2 in the modular control platform MCP are connected in each case to both the first LIN bus 44a and to the second LIN bus 44b. Since LIN information for the first or second LIN bus 44a, 44b is received on the zonal control module ZM, a dispatcher device D is provided in the zonal control module ZM which controls when specific LIN information is transmitted from the zonal control module ZM onto the respective LIN bus 44a, 44b. A separate dispatcher can be provided, for example, in the dispatcher device D for each LIN bus 44a, 44b of the zonal control module ZM and/or further elements (e.g. elements of a transmission branch from the first data connection to the LIN bus, as also shown e.g. in FIG. 5a; e.g. a filter and/or a queue and/or a transmit/receive module). According to the proposed concept with divided, zonal LIN buses, for example, a resolution of time constraints in the masters and an introduction of a dispatcher for the zonal LIN buses are provided, e.g. with a queue as a quasi-dynamic schedule table.

[0086] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 4 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1-3) or below (e.g. FIG. 5a-10).

[0087] FIG. 5a, b show an example of a data transmission in a zonalized system 50 in synchronous operation. The zonalized system 50 comprises a central control unit 51 and a zonal control module 52 which are connected via a first data connection 53. A first LIN master M.sub.A which transmits LIN information A (e.g. header and data information) according to a time protocol (e.g. LIN schedule table) is formed in the central control unit 51. A second LIN master M.sub.B which transmits LIN information B is formed accordingly, and also a third LIN master M.sub.C which transmits LIN information C (e.g. header and data information) according to a time protocol (e.g. schedule). The LIN information can be transmitted via the central control unit 51 onto the first data connection 53. The time protocol can provide, for example, that, in the normal case, the LIN information A, B, C is transmitted in 5 ms or 10 ms time slots.

[0088] The zonal module 52 shown presents a signal processing branch for a zonal LIN bus 58. The signal branch comprises a filter 54, a LIN bus schedule module 55, a dispatcher 56 and a transmit/receive module 57 (e.g. transceiver; e.g. physical bus driver), wherein header information can be exchanged via the signal branch between the first data connection 53 and the zonal LIN bus 58. Further filters 54a, 54b of further signal branches which can lead to further zonal LIN buses (not shown in FIG. 5a) which can similarly be connected to the zonal control module 52 are further presented.

[0089] The synchronous operation provides that a LIN master M.sub.A, M.sub.B, M.sub.C transmits further header information only if it has received response information from the LIN slave corresponding to previously transmitted header information. As a result, a maximum of one header per master M.sub.A, M.sub.B, M.sub.C can be present in a queue in the schedule module 55 (e.g. header information A from the first LIN master M.sub.A, header information B from the second LIN master M.sub.B, and third header information C from the third LIN master M.sub.C can be present in the queue).

[0090] If, for example, only one of the three LIN masters transmits header information, the corresponding response information can be transmitted within the intended time slot via the first data connection 53 to the intended LIN slave on the zonal LIN bus 58, and the corresponding response information can also be sent back again via the first data connection 53 to the LIN master.

[0091] If all three LIN masters M.sub.A, M.sub.B, M.sub.C simultaneously transmit header information A, B, C, the function of the queue (e.g. buffer memory) in the schedule module 55 enables this information to be temporarily stored and transmitted according to a transmission protocol to the LIN bus 58 when the latter is available.

[0092] The original, functional schedules of the LIN masters can run in a centralized manner (e.g. on an integration platform) and can be executed e.g. in parallel as a software implementation. The LIN masters can tunnel (Tx mode) LIN headers via the first data connection 53 (e.g. backbone bus), but can stop the schedule until they have received the response to the header. LIN headers from different LIN masters can be stored in chronological order in an Rx buffer (e.g. buffer memory of the zonal control module 52). From the buffer, the oldest header can be transmitted from the Rx buffer (e.g. first-in-first-out (FIFO) principal), e.g. by means of the dispatcher 56. As soon as a response to a header has been completely and correctly transmitted onto the physical LIN bus, the response can be transmitted via the backbone bus to the respective master.

[0093] FIG. 5b shows a schematic time characteristic when all three masters M.sub.A, M.sub.B, M.sub.C in each case simultaneously transmit LIN information A, B, C via the first data connection 53 to the zonal module 52. The figure shows that the dispatcher 56 first selects the LIN information C from the queue in order to transmit it onto the LIN bus 58. A connected LIN slave 15 can process the LIN information (e.g. header information) C there and transmit it back to the LIN master M.sub.C (as response information). A time duration t1 which can correspond to a time slot of the LIN protocol (e.g. 10 ms) can be provided for this purpose. The second LIN information B can be transmitted from the dispatcher 56 onto the LIN bus 58 as soon as the latter is free, e.g. in the time slot following the transmission of the first LIN information A. The third information A can be transmitted accordingly from the dispatcher 56 onto the LIN bus 58 as soon as the latter is free, e.g. in the time slot following the transmission of the second LIN information B.

[0094] The example shows a worst case for the synchronous transmission in which a collision of headers takes place. Three headers are transmitted here simultaneously. The response to the first header of the first master M.sub.A is delayed by two time slots on the zonal LIN 58. The response to the header of the second master M.sub.B is delayed by one time slot on the zonal LIN, whereas the header of the third master M.sub.C can be handled immediately. The masters in the integration platform and the underlying functions are designed accordingly so that they can cope with sporadic delays in the responses. For the masters, for example, the close tie to the original LIN time slots (e.g. 5 or 10 ms slots) can also be dissolved. The queue can be designed in synchronous mode to be no longer than the number of masters (e.g. a correspondingly small buffer memory can suffice; e.g. the capacity of the buffer memory can be designed to be able to temporarily store a maximum number of header information elements corresponding to the number of LIN masters of the system; e.g. a reserve can be provided in the buffer memory so that time delays can be compensated in the dispatcher).

[0095] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 5a, b can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1-4) or below (e.g. FIG. 6-10).

[0096] FIG. 6 shows an example of a data transmission in a zonalized system 50 in asynchronous operation. In contrast to synchronous operation, it is provided that the LIN masters tunnel LIN headers via the first data connection 53 (e.g. backbone bus in transmit mode Tx), but do not wait for the response (Rx) of the respective LIN slave before they transmit the further LIN information. Since an unpredictable sequence is possible here, it can be provided for the assignment of response information to header information that the response is transmitted with the header ID via the backbone bus back to the respective master.

[0097] In asynchronous operation, the queue (e.g. in the schedule module 55) can become even greater than the number of participants (e.g. a plurality of LIN information elements A (e.g. two, three or more), and a plurality of LIN information elements B, C can be temporarily stored). The system 50 can be designed, for example, in such a way that the permissible bus load the zonal LIN buses is not exceeded on average. A limit which is less than 100% (e.g. less than 90%, less than 80% or less than 70%) can be set for the permissible bus load.

[0098] The bus load of a zonal LIN bus can have impacts on the system. With normal utilization (e.g. bus load <95%), it can be provided that the queue does not overflow, with average cycle times being e.g. the cycle times of the functional main schedule, so that the system does not have to be synchronized. Waiting times can be inserted, e.g. in the schedule modules, if required in order to prevent temporary LIN bus overload. Average cycle times, for example, can thereby be maintained with smaller fluctuations. With a high utilization, e.g. with a bus load >95%, use of an algorithm can be provided e.g. to remove duplicate messages from the queue and prevent an overflow. The system can be designed so that short dead times occur on the physical LIN bus (e.g. zonal LIN bus 58). The system does not then have to be synchronized; e.g. the cycle times are subject to greater fluctuations.

[0099] Synchronous Tx/Rx operation (see also FIG. 5a, b) can be referred to as operation with elasticity. A zonal LIN node arrangement is provided in which e.g. no PIDs with duplicate assignment are permitted in a zonal LIN bus system. The schedules can be synchronized with one another in order to prevent dead times and temporary overload on the bus. Self-synchronization, for example, can be used. Conversely, new function timing can be provided in asynchronous Tx/Rx operation. In the zonal LIN node arrangement, for example, no PIDs with duplicate assignment can be permitted in a zonal LIN bus system and the bus utilization has e.g. a strong influence on compliance with the timing requirements.

[0100] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 6 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1-5b) or below (e.g. FIG. 7-10).

[0101] FIG. 7 shows an example of a conventional system having a plurality of LIN buses 140, 140b, 140n according to the prior art. The LIN buses 140, 140b, 140n are all connected directly to a control unit 110 in which respective LIN masters 110, 110b, 110n assigned to the buses are arranged. In contrast to the proposed zonalized system 10 with the first data connection 13, the transmission cable requirement increases as a result with each additional LIN bus, since no common transmission cable can be used for a plurality of LIN buses. A separate LIN bus must further be used for each LIN master according to the prior art.

[0102] FIG. 8 shows an example of transmission of header information H and response information R via a first data connection 13 (e.g. a CAN bus or Ethernet connection; see upper half of FIG. 8) and a LIN bus 14. A time slot 80 is used to transmit a frame comprising a header (header information H) and a response or slave response (response information R) via the LIN bus 14 (see lower half of FIG. 8). The length of the time slot 80 shown is given purely by way of example and can be e.g. 5 ms or other time durations instead of the 10 ms shown.

[0103] As shown, a first part of the time slot 80 is sufficient for transmitting the header information H and response information R via the LIN bus 14, so that a free time window 81 exists until the start of the next time slot and e.g. can be used. The duration of the time window 81, for example, is around 33% of the duration of the time slot 80 (e.g. at most 40% and/or at least 20% of the duration of the time slot 80). The free time window 81 can be provided if the tolerance times defined in the LIN transmission standard are not required for the transmission of the LIN frame.

[0104] The free time window 81 in which no information is transmitted via the LIN bus 14 can be used to transmit the response information R via the first data connection 13 back to the LIN master in the central control unit (e.g. tunnelling of the response information R). Further header information H.sub.n+1 can be transmitted for the transmission of a header via the LIN bus 14 in the next time slot from the LIN master to the zonal control module via the first data connection 13. The header information R for the illustrated LIN frame of the time slot 80 has correspondingly been transmitted in a free time window of the previous time slot (see header information H on the first data connection 13 temporally before the start of the time slot 80). The time duration from the start of the transmission of the header information H via the first data connection 13 to the end of the reception of the associated response information R via the first data connection 13 can thus be less than the time duration of the time slot 80.

[0105] A predetermined time slot (e.g. a 5 ms or 10 ms slot provided according to the LIN transmission) can be used, for example, for the transmission of the header information and the response information via the LIN bus (e.g. LIN frame). It is further provided that the response information and/or further header information are transmitted via the first data connection within a time frame reserved in the time slot. The availability of the time window can be enabled in that a tolerance time reserved in the time slot according to the LIN standard is not required for the transmission on the LIN bus. This can be achieved, for example, as already described, by using hardware-based microcontrollers in the implementation of the LIN master and/or LIN slave.

[0106] It can be provided, for example, that the header is transmitted on the LIN bus at the start of the time slot. The free time window can therefore be provided at the end of the time slot. The response can be received via the LIN bus on the zonal control module before the time window is temporally reached within the time slot, so that corresponding response information can be transmitted via the first data connection to the LIN master in the free time window. The header information for the subsequent time slot is also transmitted e.g. within the time frame via the first data connection to the zonal control module, as shown in FIG. 8, so that a corresponding next header can be transmitted via the LIN bus in a subsequent time slot. Overall, the header information and the response information of a frame (e.g. LIN bus frame) can therefore be transmitted by the LIN master and can again be received on the LIN master via the first data connection within a provided time duration of the time slot (e.g. shifted to the actual time slot on the LIN bus). A time delay in the activation of the LIN slave can thereby be avoided even if the first data connection is used.

[0107] According to one exemplary embodiment, it is provided that the reserved time window has a time duration of at least 0.2 ms (or of at least 0.5 ms, of at least 1 ms, of at least 1.5 ms or of at least 2 ms) and/or of at most 5 ms (or of at most 4 ms or of at most 3.5 ms). The header information and response information, for example, can be transmitted within this time via the first data connection between the central control unit and the zonal control module.

[0108] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 8 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1-7) or below (e.g. FIG. 9-10).

[0109] FIG. 9 shows an example of a transmission of a plurality of frames f.sub.1, f.sub.2, f.sub.3 via the first data connection 13 to a plurality of LIN buses 14, 44a, 44b using a time offset t.sub.off. The time offset t.sub.off can describe e.g. the time duration between the start of the first header information H and the start of the next header information H.sub.2. The duration of the transmission of header information via the first data connection 13 can, for example, be between 50 s and 60 s and the time offset t.sub.off can be 100 s. The time offset t.sub.off can define, for example, a time duration between the end of the transmission of the header information H and the start of the transmission of the header information H.sub.2 and can be e.g. more than 10 s and/or less than 50 s.

[0110] The header information H, H.sub.2, H.sub.3 is transmitted from different LIN masters in succession via the first data connection 13 to the different LIN buses 14, 44a, 44b assigned in each case to the LIN masters. The header information H, H.sub.2, H.sub.3 can also be transmitted, for example, from a single LIN master in each case to different zonal control modules or to one zonal control module (e.g. a plurality of LIN buses and/or LIN slaves assigned to the LIN master can be connected to the one zonal control module; e.g. the header information H, H.sub.2, H.sub.3 can be temporarily stored in a buffer memory of the zonal control module until it is transmitted via a LIN bus). As shown, the slower data transmission of the frames f.sub.1, f.sub.2, f.sub.3 via the LIN buses 14, 44a, 44b takes longer than the data transmission of header information and response information via the first data connection 13. After the transmission of the first header information H from a first LIN master via the first data connection 13, further information H.sub.2, H.sub.3, etc., can therefore be transmitted from further LIN masters, e.g. as long as the frame f.sub.1 is transmitted via the LIN bus 14. A maximum possible number of header information elements H, H.sub.2, H.sub.3, etc., for example, which are transmitted via the common data connection 13 can depend on the data transmission speed and/or the length of the time offset t.sub.off and/or on the duration of the frame f.sub.1. The time offset t.sub.off can be chosen, for example, in such a way that response information can be transmitted via the first data connection 13 in each case between the transmission of two consecutive header information elements in order to achieve e.g. a constantly alternating transmission of header information and response information via the first data connection 13.

[0111] The synchronization of the LIN masters with offset t.sub.off can enable e.g. collision-free scheduling on the backbone bus (e.g. first data connection 13). The time slots of the LIN buses 14, 44a, 44b are, for example, arranged as shifted in each case by the time offset. The use of the synchronization or time offset can enable the plurality of LIN masters to subsequently transmit further headers of subsequent LIN frames for the assigned LIN buses 14, 44a, 44b via the first data connection 13 without producing collisions on the first data connection 13.

[0112] According to one exemplary embodiment, it is provided that the method further comprises transmitting second header information from a second LIN master of the central control unit via the first data connection. The two header information elements are transmitted e.g. temporally shifted with a time offset which is chosen depending on the data transmission speed of the first data connection.

[0113] The first header information is transmitted e.g. to a LIN slave on a first LIN bus and the second, time-shifted, header information is transmitted to a LIN slave on the same first LIN bus or alternatively on a second LIN bus (e.g. coupled to the same or to a different zonal control module). Since the data transmission speed of the first data connection is greater than that of the LIN buses, both header information elements can be transmitted on the common data line. A collision of header information elements on the first data connection can be avoided by using the time offset.

[0114] A time offset, for example, having a duration of at least 20 s (or at least 50 s or at least 100 s) can be chosen between the transmission of two header information elements via the first data connection. A time offset can also be chosen, for example, in such a way that the respective response information elements can be transmitted via the first data connection back to the respective LIN masters without collision with subsequent header information on the first data connection. Latency times, for example, due to collisions can thereby be avoided.

[0115] Examples therefore relate in general to a concept for tunnelling a LIN bus 14 via a backbone bus (e.g. the first data connection 13, e.g. a CAN bus or an Ethernet connection). In order to enable e.g. slimmer and more economical and/or better automated manufacture of a cable harness, one or more backbone buses (e.g. first data connection) are introduced, via which buses such as e.g. LIN, CAN, FlexRay and also discrete signals can be tunneled.

[0116] Tolerances set out in the LIN specification, in particular, can be used. These tolerances (e.g. free time window 51) are e.g. no longer required on the LIN bus in modern, available microcontrollers (Cs) with hardware LIN logic (e.g. hardware-supported). A synchronization can be performed with a time offset of the LIN masters of those buses which are intended to be jointly tunneled. A time buffer, for example, is provided for the tunnelling of LIN buses (e.g. the time window 51). If a plurality of LIN buses are tunneled on the same backbone bus, collisions can be avoided by means of the proposed concepts. A plurality of LIN buses, for example, can be routed from a central control unit to a tailgate control unit and/or roof control unit.

[0117] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 9 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1-8) or below (e.g. FIG. 10).

[0118] FIG. 10 shows a schematic example of a system 90 having a central control unit 91 and a zonal control module 92 to which a plurality of different legacy buses are connected.

[0119] For an efficient data connection, the zonal control module 92 is connected to the central control unit 91 via a first data connection 93 (e.g. faster data transmission than via the legacy buses).

[0120] A first legacy bus 94a and a second legacy bus 92b (or alternatively a discrete signal line 92b are connected to the zonal control module 92. The first legacy bus 92a can be e.g. a LIN bus, and the second legacy bus 92b can be e.g. a CAN bus. Via the first data connection 93, the control units of the legacy buses 94a, 94b can in each case be enabled to transmit information to the central control unit 91 and to receive information from the latter (e.g. communication between the LIN master in the central control unit 91 and a LIN slave on the LIN bus 94a).

[0121] In a system 90 having two zonal control modules, for example, a plurality of buses can be connected in each case to both zonal control modules, for example a LIN bus, a CAN bus and a FlexRay bus can be connected to the first zonal control module, and a LIN bus, a CAN bus and a zonal Ethernet connection can be connected to the second zonal control module. By bundling all functions in the central control unit 91, a high-level functionality can be enabled there (e.g. service-oriented architecture SOA). The system 90 can be connected e.g. efficiently (e.g. wirelessly) to a backend via the central control unit 91, so that one common backend connection can suffice for all functions of the individual control units on the buses of the zonal control module.

[0122] Through the combination of the zonal control modules with the first data connection (e.g. backbone bus), the present legacy functions can be implemented together with their legacy control units (e.g. LIN or CAN control unit) with comparatively little outlay on a zonal physical on-board power supply architecture. Cost benefits can be achieved, since the cable harness can be manufacturable e.g. in an automated manner. The system can enable a high degree of scalability and flexibility. Mixed mode, for example, and discrete signal buses can be jointly connected to the zonal control module. In other words, a central docking point of the All-IP and Service-Oriented Architecture environment onto the legacy environment can be implemented via the backbone bus (in a signal-based manner), so that older technologies of the vehicle domain can be combined with modern technologies.

[0123] The system 90 proposed in FIG. 10 can be used in a motor vehicle e.g. for a zonal on-board power supply system with legacy abstraction and backbone bus in a motor vehicle. A multiplicity of different electrical/electronic components, for example, can be integrated in this way into modern on-board power supply systems (e.g. with an Ethernet connection). In the system shown, the zonal control module 92 can be referred to as e.g. a legacy abstraction switch (e.g. universal gateway for different legacy buses). One advantage can be that a configurable zonal control module 92 can be used which can be programmed accordingly on the basis of legacy buses 94a, 94b that are actually used (e.g. operation as a gateway for the respective legacy buses 94a, 94b can be enabled by means of a corresponding software setting). A universal zonal control module 92 of this type can offer the advantage that it can be used in a wide variety of configurations, as a result of which e.g. cost savings can be made.

[0124] Further details and aspects are mentioned in connection with the exemplary embodiments described above or below. The exemplary embodiment shown in FIG. 10 can have one or more optional additional features which correspond to one or more aspects which are mentioned in connection with the proposed concept or with one or more exemplary embodiments described above (e.g. FIG. 1-9) or below.

[0125] In terms of the error diagnostics in proposed systems and methods which can follow the principles of error diagnostics in accordance with the LIN specification, it can be provided to transmit error information also via the first data connection. Each LIN node performs error detection diagnostics e.g. independently on the (zonal) LIN bus. The error evaluation is performed centrally by the master. The master also reads, e.g. on the bus, and evaluates all communication on the bus. The slave also reads, e.g. on the bus, and evaluates all messages which it has transmitted and received itself; the slave enables transmission of the error status in the payload (response) within an error bit of an unconditional frame. The master evaluates e.g. the error bits of the slaves. Error detection is performed in the slave, e.g. independently from the zonalization, via the payload in the slave response. Error detection for the master is taken over by the dispatcher e.g. in the case of zonalization and is transmitted as a separate status message to the central LIN master. The system can be designed for error diagnostics so that the LIN master can be informed or can inform itself on the integration platform (e.g. central control unit) regarding the state/status of the backbone communication (e.g. communication via the first data connection).

[0126] One proposed aspect relates to the zonalization of a functional LIN bus architecture in the motor vehicle. In contrast to other LIN systems, it can be provided that LIN slaves of different LIN Masters share zonal LIN buses so that e.g. a system with distributed LIN slaves can be implemented with a small cable requirement for LIN buses. The multiplicity of communication buses in a vehicle, for example, can be converted from a functional connection of the control units according to other concepts to a zonal connection of the control units, which can result in a reduction of the cable harness and/or an increase in flexibility. In particular, a concept is proposed for the connection of LIN buses.