System for transmitting data in a motor vehicle, motor vehicle and method

Abstract

The present invention relates to a system (10) for transmitting data in a motor vehicle. The system (10) includes: a central controller (11) in which at least one first LIN master (11a) and a second LIN master (11b) are configured; a partition control module (12) coupled to the central controller (11) via a first data connection (13); and a LIN bus (14) coupled to the partition 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 invention also relates to a method (20) for data transmission.

Description

Technical Field

[0001] This invention relates to a system for transmitting data in a motor vehicle. The system includes a central controller and at least one additional control module. The system is configured to control devices via a legacy bus, particularly a LIN bus. Other embodiments relate to a motor vehicle and a method for controlling a LIN slave device connected to a LIN bus. Background Technology

[0002] In motor vehicles, various devices are controlled via data connections or bus systems. Known buses used in motor vehicles include LIN (Linux In-Network), CAN (Controller Area Network), or FlexRay buses. Furthermore, discrete signals can also be transmitted in cabling throughout the vehicle. Buses are typically designed functionally, meaning controllers that map or form a common function are connected together on a single bus.

[0003] A LIN system consists of a master (LIN master) and one or more slaves (LIN slaves). The master, for example, is configured as a microcontroller, which can act as a bridge connecting the LIN to a CAN bus. On the LIN, the master determines the (e.g., fixed-configuration) time sequence of all messages by sending the beginning of the message, the so-called message header. Therefore, one or more LIN slaves are serially connected to the LIN master via the LIN bus. The transmission protocol specifies that the LIN master sends a message header to the LIN slave. The responding LIN slave, in response to the message header, sends a response back to the LIN master within a specified time slot (e.g., within a 5 ms or 10 ms clock on the LIN bus). The message header and response are combined into a frame, which is transmitted within the duration of the specified time slot.

[0004] In controllers used to control multiple devices or slave units with different functions, the use of LIN buses is increasingly common in motor vehicles. These buses are laid as transmission cables within the vehicle's wiring harness. Due to the large number of LIN buses, the perimeter or cross-section of the wiring harness may be large, making it difficult to accommodate the harness within the limited space of a motor vehicle. Summary of the Invention

[0005] The objective of this disclosure is to provide an improved scheme for transmitting signals, particularly slave devices, in a local network, such as in a vehicle, to control a controller, especially a slave device, using a legacy bus or discrete data lines, particularly a LIN bus.

[0006] This task is solved according to the technical solution of the present invention. Other advantageous embodiments are described in the following description and in conjunction with the accompanying drawings.

[0007] Accordingly, a system for transmitting data in a motor vehicle is proposed. The system includes a central controller, in which at least one first LIN master and a second LIN master are configured. The system also includes at least one partition control module, which is coupled to the central controller via a first data connection. The system further includes a LIN bus (e.g., as a second data connection of the system), which is coupled to the partition control module. It is specified that 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.

[0008] Therefore, the system allows at least two LIN slaves assigned to different LIN masters to use a common LIN bus. This eliminates the need for at least one LIN bus compared to other systems, thus saving on LIN bus cabling. For example, multiple LIN masters can be configured in the central controller, controlling multiple LIN slaves assigned to each master on a common LIN bus. Unlike other systems, a separate LIN bus is not required for each individual LIN master.

[0009] Using a first data connection can make data transmission from the central controller to the zone control modules more efficient. For example, the LIN bus itself does not need to be laid to the central controller. Instead, a first data connection can be used to transmit other signals or information in addition to LIN information (e.g., in-vehicle network connections; such as Ethernet or CAN connections). Data transmission via the first data connection can reduce overall cabling requirements in the vehicle through greater efficiency (e.g., higher data transmission speeds compared to LIN bus data transmission).

[0010] Instead of the LIN bus technology implementation shown in the exemplary examples below, other legacy buses (such as CAN bus and / or FlexRay bus) and / or discrete data lines can also be connected to the partition control module. Accordingly, instead of the LIN host, or in addition to the LIN host, modules for receiving signals from the respective controllers and for sending signals to the respective controllers can also be provided in the central controller.

[0011] This approach allows for the functional integration of different types of bus systems into a single central controller. The partition control module can, for example, serve as a gateway between legacy buses and primary data connections (e.g., Ethernet connections) to achieve compatibility between different technologies. In particular, the proposed system allows any legacy bus to connect to the partition control module, enabling the transmission of corresponding signals (e.g., signals according to CAN / FlexRay / LIN, etc.) via the backbone tunnel of the primary data connection (e.g., Ethernet), thus enabling flexible, such as partitioned or regionalized, systems.

[0012] According to one aspect, the system includes at least one additional partition control module, which is coupled to the central controller via a first data connection. Furthermore, at least one additional legacy bus, particularly a LIN bus, is provided, which is coupled to the additional partition control module. It is specified that at least one LIN slave assigned to a first LIN master and / or at least one LIN slave assigned to a second LIN master is connected to the additional LIN bus of the additional partition control module.

[0013] Therefore, the system can be partitioned, for example, by constructing one or more regions where legacy buses of the system, especially LIN buses (e.g., LIN buses shared by different LIN hosts), are distributed. Accordingly, two or more partition control modules can be configured in the system. Sharing a first data connection by multiple partition control modules can further improve the efficiency of data transmission via the first data connection. For example, instead of multiple LIN buses, the first data connection is sufficient for transmitting LIN information (e.g., message header information and / or response information) between the central controller and the partition control modules.

[0014] On different LIN buses, for example, slave devices assigned to a specific LIN master can be connected separately. This partitioning scheme eliminates the high cabling requirements associated with physically very long LIN buses. Instead, the LIN master can advantageously control its LIN slaves on different local LIN buses. The total physical length of the local or partitioned LIN buses can be reduced here, for example, based on the use of a first data connection, compared to the total physical length of the LIN buses required in other LIN systems.

[0015] For example, it can be specified that the partition control module is configured to filter out only the message headers transmitted by the LIN master via the first data connection, whereby the message headers address LIN slaves connected to the corresponding LIN bus of the partition control module. For example, message headers or message header information for all LIN slaves of the system can be transmitted via the first data connection. Filtering prevents message header information not intended for transmission on the LIN bus of a specific partition control module from being received by that specific partition control module or its signal branches.

[0016] It can also be specified that the partition control module (e.g., the partition control module's filter) is configured to also filter out duplicate messages, such as redundantly sent message headers. This reduces the LIN bus load because redundancy is avoided, and therefore fewer messages need to be sent via the LIN bus. Due to the shared LIN bus, delays may occur in transmitting response information, potentially leading to the transmission of message headers twice. Filtering out redundant information is particularly advantageous in systems with a LIN bus shared by multiple LIN hosts, as the LIN bus's transmission capacity must be considered due to the presence of multiple hosts.

[0017] For example, it can be specified that exactly one LIN bus is coupled to the partition control module. Unlike other solutions, by sharing this single LIN bus, it is not necessary to provide separate LIN buses for LIN slaves of different LIN masters. By using exactly one LIN bus for each partition control module, the cabling requirements for the LIN bus in a region of the system can be reduced, for example.

[0018] For example, the partition control module can be configured to control the timing of message headers from the first and second LIN hosts received on the partition control module and transmitted from the partition control module to the LIN bus, based on communication behavior (e.g., according to a transport protocol; e.g., according to rules for data transmission). Common data transmission of LIN information from multiple LIN hosts requires, for example, providing suitable scheduling for data transmission via the first data connection and / or the LIN bus. Communication behavior can be defined synchronously or asynchronously, for example.

[0019] According to one example, the communication behavior can be specified as synchronous transmission. In synchronous transmission, the LIN host does not send additional headers unless it receives a response corresponding to the last sent header. This response is transmitted from the LIN slave to the LIN host via the LIN bus, the partition control module, and the first data connection. For example, the first LIN host sends the first header information through the first data connection between the central controller and the partition control module, and only sends the subsequent second header information after receiving the response information corresponding to the first header information at the central controller via the first data connection.

[0020] For example, this synchronous communication behavior can be configured to transmit data to the LIN slave of the first partition control module. For instance, the LIN master can send the first header information to the second partition control module even before the first partition control module receives a response from the LIN slave. Synchronous data transmission for the corresponding partition control module can avoid overloading the LIN bus on that module. However, if the header information is sent to the second partition control module, this is independent of the bus load on the LIN bus of the first partition control module.

[0021] As an alternative, the communication behavior could be specified as asynchronous transmission, in which the LIN host also sends another header even before it has received a response corresponding to the last sent header. Here, the partition control module could be specified to transmit the response along with a matching header (e.g., a matching header ID; for example, header ID and / or a protected identifier PID) to the LIN host via a first data connection, so that the distribution of the response and header can be implemented on the LIN host.

[0022] Asynchronous communication allows for more flexible transmission of header information to LIN slaves. For example, if multiple LIN masters simultaneously send header information to a partition control module, a certain amount of time may pass before all header information is transmitted via the shared LIN bus (e.g., pending header information may be cached in the partition control module's memory until transmission via the LIN bus, see also the explanation below). If, during this time, a LIN master wishes to send a header information with higher urgency, it must wait until it receives a previous response, according to synchronous transmission behavior. Conversely, asynchronous transmission allows for header information prioritization. For example, a LIN master can send a header information with higher priority to the partition control module before receiving a response to a previous (or more) header information. Transmission control (e.g., scheduling) on ​​the partition control module can prioritize the transmission of higher-priority header information on the LIN bus. Therefore, even under high bus load, urgent header information can be prioritized on the shared LIN bus, and the transmission time of such important header information is reduced.

[0023] For example, the system can be specified to include multiple LIN hosts in a central controller and multiple partition control modules, each with its own LIN bus. The system can offer high design flexibility, for example, by using a single data connection. The number of partition control modules and / or LIN hosts can therefore be selected individually based on the required application.

[0024] In particular, it can be stipulated that the number of LIN buses on the system's partition control module is greater than the number of LIN hosts in the system. This, for example, can reduce the risk of overloading the transmission capacity of each LIN bus. For instance, the LIN slaves of a single LIN host can be distributed across different LIN buses. This allows for the distributed use of LIN buses over time by a single LIN host, ensuring, at least statistically speaking, the availability of each LIN bus for transmitting information from other LIN hosts. Since the number of LIN buses is greater than the number of LIN hosts, it can provide a buffer in terms of LIN bus transmission capacity, which may be necessary, for example, when LIN hosts do not use the LIN buses in a uniformly distributed manner.

[0025] According to one embodiment, the partition control module may have a buffer (e.g., in the scheduling module) to buffer message headers received from the LIN host for such a long period that the designated LIN bus becomes available for transmitting the message headers. As already mentioned, sharing the LIN bus can cause temporary overload of the LIN bus transmission capacity. This can be avoided by using a buffer. The control unit (e.g., the scheduler) can determine the order in which the message header information stored in the buffer is transmitted to the LIN bus. As mentioned above, the transmission can be performed synchronously or asynchronously, for example. The control unit can also be configured to remove redundant messages present in the buffer, thereby avoiding unnecessary increase in bus load, for example, by repeatedly transmitting the same messages.

[0026] For example, the partition control module can be configured to send fault information about the LIN bus and / or the first data connection to the LIN host of the central controller. This allows for the use of traditional LIN fault management in the proposed partitioning system. Thus, compatibility between the proposed system and other LIN systems can be achieved. For instance, it may be necessary to ensure that fault information sent from the LIN slave is available on the assigned LIN host. The proposed partition control module can, for example, embed the corresponding fault information into the data format of the first data connection so that the fault information can be further transmitted to the LIN host.

[0027] For example, it can be specified that the data transmission speed of the first data connection between the central controller and the partition control module is higher than the data transmission speed of the LIN bus.

[0028] The higher data transfer speed of the first data connection compared to the LIN bus enables faster exchange of header information (e.g., for sending as headers via the LIN bus) and response information (e.g., as responses sent via the LIN bus) between the central controller and the partition control modules. This allows multiple partition control modules to connect to a central controller. For example, multiple header messages can be sent via the first data connection during predefined time slots on the LIN bus (e.g., 5 ms or 10 ms time slots set for LIN transmissions). This can be advantageous, for example, if multiple LIN slaves are connected to the LIN bus of the partition control modules, and these multiple LIN slaves are controlled by corresponding LIN masters of the central controller.

[0029] Therefore, the proposed system, for example, allows information from the LIN host that should be transmitted via the LIN bus to be first sent to the partition control module via a faster connection, from where the information is further transmitted to the slower LIN bus. Thus, unlike conventional systems, the LIN host is not directly located in the partition control module, but rather in a separate central controller.

[0030] By using a faster first data connection, unlike conventional systems, multiple transmission cables for multiple LIN buses can be eliminated between the central controller and the partition control modules, for example, because the header and response information of multiple LIN buses can be transmitted via a common transmission cable of the first data connection. This can be done, for example, without causing time delay when transmitting via the first data connection. For example, using a first data connection can advantageously reduce the cable bundle between the central controller and the partition control modules (e.g., a smaller diameter or smaller cross-section of the cable bundle).

[0031] According to one embodiment, the data transmission speed of the first data connection is at least 10 times (or 20 times or 50 times) the data transmission speed of the LIN bus. This faster transmission speed via the first data connection allows a greater number of LIN buses (e.g., a corresponding number of partition control modules) to operate via a LIN host located in a central controller. It also allows the transmission of other information (e.g., additional and / or information different from message header and response information) via the first data connection without, for example, collisions or delays occurring during transmission via the first data connection.

[0032] For example, the first data connection can be constructed based on Ethernet standards, CAN standards, FlexRay standards, radio-based transmission standards (such as WLAN, 4G, 5G, or Bluetooth), PCI Express standards, or home networking standards (such as HomeGrid-G.hn). Using these standards, the desired data transfer speed for the first data connection can be achieved.

[0033] According to one embodiment, the LIN master and / or LIN slave are hardware-supportedly constructed on the microcontroller used for this purpose. Generally, functionality can be implemented on the microcontroller by means of software or by using predetermined hardware blocks. Software solutions can have the advantage of being more flexible in changing or performing multiple functions, whereas physical hardware blocks, once implemented, can only be used for the corresponding specified functions. Therefore, in hardware-supported implementations, for example, the required execution duration can be adhered to more precisely (e.g., process duration can be better planned), because, for example, no other process can cause execution delays (as is the case in software solutions).

[0034] When transmitting LIN information (e.g., frames; headers and responses), tolerance times are specified according to the LIN transmission standard. The actual required transmission time (e.g., maximum header transmission time) may be up to 40% longer than the nominal or rated transmission time. Therefore, when transmitting via the LIN bus, if fixed time slots (e.g., 5ms or 10ms) are specified, idle time windows are created in the frame time slots if the operating transmission mechanism does not require the reserved tolerance time. When using hardware-supported microcontrollers to implement LIN masters and / or LIN slaves, it is possible to adhere to the nominal or rated transmission time or at least not require the entire reserved tolerance time. Therefore, the unnecessary tolerance time (e.g., time windows) in the LIN bus time slots can be fully utilized elsewhere.

[0035] Hardware-supported microcontrollers can achieve higher reliability by eliminating the need for a specified time window (tolerance time) on the LIN bus. Within this time window, header and / or response information can be advantageously transmitted to or from the LIN host via the first data connection without, for example, delaying the specified clock on the LIN bus. When implementing LIN functionality on modern microcontrollers with LIN stack hardware support, the 40% reserve or tolerance time in the timing is not required, or is not strictly necessary. This time can, for example, be used for tunneling (e.g., header and response information via the first data connection). The available idle time window has, for example, the length of the slot duration (i.e., the nominal transmission time of the header and response multiplied by a factor of 140%) minus the nominal transmission time of the header and response / the rated transmission time (e.g., the maximum tolerance time). However, depending on the data transmission rate of the first data connection, a shorter time window (e.g., shorter than the maximum tolerance time) may also be sufficient for transmitting header and / or response information to or from the LIN host via the first data connection.

[0036] The availability of idle time windows can be better guaranteed by replacing or attaching to hardware-supported microcontrollers, for example, by using software solutions on high-performance computing units or by providing computing units specifically for software solutions.

[0037] For example, when using the proposed system, it is possible to transmit information via the first data connection (e.g., from or to a LIN host allocated to the LIN bus) within the specified time slots of the LIN bus.

[0038] According to one embodiment, the system is configured to transmit frames via the LIN bus and corresponding header and response information via a first data connection within a predefined nominal / rated time slot duration for data transmission of frames (i.e., headers and responses transmitted via the LIN bus). In other words, the unnecessary tolerance time defined by the LIN transmission standard can be used to transmit (e.g., tunneled transmission) header and / or response information via the first data connection (which may be referred to as the backbone bus). This allows for the transmission of corresponding header and / or response information from or to a LIN host located in a central controller during the time slot duration on the LIN bus.

[0039] For example, it is specified that when transmitting via the first data connection, the header information is embedded in the standard data packet of the first data connection. The first data connection may be, for example, a CAN bus, and the header information may be embedded in a CAN frame. Accordingly, the response information may also be embedded in the corresponding standard data packet used. Advantageously, when the data packet length is variable, the smallest possible frame size can be selected when transmitting via the first data connection, in which the header information and / or response information (e.g., the standard minimum available frame size of the first data connection) can be transmitted.

[0040] For example, an Ethernet connection can be used as the primary data connection, and header and / or response information can be embedded into a 64-byte Ethernet frame during transmission over the Ethernet connection. The advantages are that header and response information (e.g., when the host itself sends data) can be transmitted completely within a 64-byte Ethernet frame, and the transmission time via the primary data connection can be very short. For example, an Ethernet connection with a maximum speed of 10 Mbit / s can be used, as this enables sufficiently fast data transmission and / or allows for a more economical design of the primary data connection.

[0041] For example, multiple message headers from different LIN hosts in a central controller can be transmitted together in a single message. For instance, two (or three or more) message headers can be transmitted via a first data connection in a single data packet.

[0042] Another aspect of this disclosure relates to a system in which, in addition to a LIN bus, at least one other legacy bus with a corresponding controller and / or additionally discrete signal lines with corresponding controllers are connected to a partition control module. Alternatively or additionally, the system may have another partition control module and another legacy bus and / or discrete signal lines with corresponding controllers. The system is configured to transmit information from the legacy bus and / or discrete signal lines to a central controller via a first data connection.

[0043] In the automotive industry, older buses are typically those that have been used in vehicles for a long time, such as CAN bus, LIN bus, FlexRay bus, buses with discrete signals, and I2C bus. Therefore, for example, it can be specified that a LIN bus and a CAN bus with a corresponding CAN controller are connected to the partition control module.

[0044] Information from legacy buses or discrete signal lines can be packaged into data packets for the first data connection and sent (e.g., embedded in an Ethernet frame and thus transmitted via the first data connection). Here, a partition control module can be used to assign a (e.g., virtual) MAC address for the Ethernet communication protocol to the corresponding controller on the legacy bus.

[0045] Therefore, the system can flexibly couple different legacy buses to the backbone bus, such as an Ethernet connection, through a partition control module. This partition control module can abstract the information of the legacy bus controller for transmission via a first data connection (e.g., Ethernet). This allows the proposed partitioning system to be used more flexibly to integrate different bus types. Using a first data connection can also, for example, reduce the cabling requirements of the corresponding legacy buses.

[0046] One aspect relates to a motor vehicle having a system according to the above or below description. In particular, it is specified that at least two zone control modules of the system are respectively located in different zones of the motor vehicle.

[0047] Alternatively, the vehicle's system may have only one unique area. In this case, multiple LIN slaves, for example, assigned to different LIN masters, can be connected to a common LIN bus (or multiple LIN buses), which are connected to the system's partition control module. By providing one or more common LIN buses in different areas of the system and / or tunneling data transmission via a first data connection, the required cable length or cabling requirements can be reduced compared to other LIN bus systems. Therefore, the cabling of the system in the vehicle can be simplified and / or the system cost reduced.

[0048] For example, it can be specified that the transmission cables for the first data connection and / or the LIN bus are guided through the pillars of the vehicle. When the transmission cables for the first data connection (e.g., CAN bus or Ethernet cable) pass through the pillars, multiple LIN bus cables in the pillars can be omitted, for example. The system can be implemented such that not all LIN bus cables of the system need to pass through the pillars, but rather the number of LIN bus cables in the pillars can be limited. This can, for example, advantageously make it easier to guide the cable bundle through the pillars.

[0049] As an alternative, the proposed system can also be used in other modes of transportation (such as airplanes or ships) and general local area networks (such as smart home devices or home networks, such as networks defined by the HomeGrid standard).

[0050] One aspect relates to a method for controlling at least one first LIN slave and a second LIN slave, the first and second LIN slaves being connected to a common LIN bus. The method includes sending first header information from a first LIN master to the first LIN slave via the common LIN bus and sending second header information from a second LIN master to the second LIN slave via the common LIN bus.

[0051] The method further includes receiving, on the first LIN host, response information corresponding to the first message header information from the first LIN slave, and on the second LIN host, response information corresponding to the second message header information from the second LIN slave.

[0052] This method allows a common LIN bus to be used by two or more LIN masters. In other methods for transferring data on a LIN bus, each LIN master may be provided with a separate LIN bus. Therefore, in other schemes, the number of cables required for a large number of LIN buses can be very large. In contrast, the proposed method saves cabling because not each LIN master requires a separate LIN bus. This method can be advantageously used in partitioned systems where LIN slaves of a LIN master are set up on different common LIN buses and / or deployed in systems with low bus loads, such as when the LIN master sends information (e.g., message header ID and / or data portion) discontinuously to the assigned LIN slaves. When this method is used, for example, in systems where data transmission is not performed using every time slot specified in the LIN transmission method, it can be implemented without overloading the LIN bus capacity.

[0053] Other details and aspects are mentioned in conjunction with the embodiments described above or below. In particular, the vehicle and method may have the features already described in conjunction with the proposed system. The described embodiments may include one or more optional additional features corresponding to the proposed scheme or above or below (e.g., Figure 1-10 (This refers to one or more aspects mentioned in one or more embodiments described.) Attached Figure Description

[0054] The embodiments are described in detail below with reference to the accompanying drawings. The drawings are as follows:

[0055] Figure 1 A schematic example of a system with a central controller and zone control modules is shown;

[0056] Figure 2 A flowchart illustrating a method for controlling a first LIN slave and a second LIN slave is shown.

[0057] Figure 3 A schematic example of a partition system with four partition control modules and three LIN hosts is shown.

[0058] Figure 4 A schematic example of a system with a partition control module connected to two LIN buses is shown;

[0059] Figure 5a Figures 1 and 2b illustrate an example of data transfer in a partitioned system with synchronous operation;

[0060] Figure 6 This illustrates an example of data transfer in a partitioned system operating asynchronously;

[0061] Figure 7 shows an example of a traditional system with multiple LIN buses;

[0062] Figure 8 This illustrates an example of transmitting header and response information via tunnel transmission through a first data connection that serves as the backbone bus;

[0063] Figure 9 This illustrates an example of transmitting multiple frames to multiple LIN buses via a first data connection when using time offset; and

[0064] Figure 10 A schematic example of a system with a central controller and a partition control module is shown, with two different legacy buses connected to the partition control module. Detailed Implementation

[0065] Various embodiments will now be described in more detail with reference to the accompanying drawings, some of which are illustrated in the drawings. In the drawings, for clarity, the thickness dimensions of lines, layers, and / or regions may be exaggerated. In the following description of the drawings, which show only a few exemplary embodiments, the same reference numerals may denote the same or similar parts.

[0066] An element referred to as being “connected” or “coupled” to another element may be directly connected or coupled to said other element, or there may be an element located therebetween. Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as those of ordinary skill in the art to which the embodiments pertain.

[0067] Figure 1 A schematic example of a system 10 for transmitting data, for example, in a motor vehicle, is shown. The system 10 includes a central controller 11 in which at least one first LIN master 11a and a second LIN master 11b are configured. The system 10 also includes a partition control module, or area control module 12, which is coupled to the central controller 11 via a first data connection 13. The system 10 also includes a LIN bus 14, which is coupled to the partition 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, for example, in a motor vehicle.

[0068] Since the proposed system 10 allows the slave devices 15a, 15b of different hosts 11a, 11b to be configured on a common LIN bus 14, the system 10 can reduce the cabling requirements for the LIN bus. For example, the first data connection 13 allows the LIN bus of the system 10 to be partitioned, allowing for the configuration of only one LIN bus in the required area, each LIN bus being connected to a central controller (e.g., an integrated platform) via the first data connection 13. Therefore, the centralization of the LIN host can be achieved simultaneously with the decentralization or partitioning of the LIN system.

[0069] By providing a first data connection 13 with a higher data transfer speed than the LIN bus 14, more LIN buses can be connected to the partition control module 12, for example, without having to lay separate transmission cables to the central controller 11 with corresponding LIN hosts 11a, 11b. Therefore, system 10 can reduce cabling requirements when using multiple LIN buses. For example, the first data connection 13 can be used as a central data connection (e.g., a central bus or backbone bus; e.g., an Ethernet connection or a CAN bus) to transmit LIN information, especially header and response information, from the corresponding LIN bus tunnel to the corresponding LIN host in the central controller 11.

[0070] As an alternative, another bus system with a lower data transfer speed than the first data connection 13 can also be provided instead of the LIN bus.

[0071] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 1 The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or above or below (e.g., Figure 2-10 (This refers to one or more aspects mentioned in one or more embodiments described.)

[0072] Figure 2 A flowchart illustrating a method 20 for controlling a first LIN slave and a second LIN slave is shown. Method 20 includes: a first LIN master sending 21 first message header information to the first LIN slave via a common LIN bus, and a second LIN master sending 22 second message header information to the second LIN slave via the same LIN bus. Method 20 further includes receiving 23 a response message from the first LIN slave corresponding to the first message header information at the first LIN master, and receiving 24 a response message from the second LIN slave corresponding to the second message header information at the second LIN master.

[0073] For example, the proposed method can be summarized as follows: information sent from the LIN master to the LIN slave includes a message header (such as an identifier) ​​and / or content (such as a data portion). According to this method, command information can also be sent from the LIN master to the LIN slave, for example.

[0074] Advantageously, this method allows multiple slave devices to run on a single bus, such as a LIN bus, with each slave assigned to two or more different masters. This reduces the physically required cable length, which is particularly advantageous in vehicles with limited installation space.

[0075] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 2The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1 ) or below (such as Figure 3-10 (This refers to one or more aspects mentioned in one or more embodiments described.)

[0076] Figure 3 A schematic example of a partition system 30 with four partition control modules ZM1 to ZM4 is shown. Each partition control module ZM1 to ZM4 is coupled to the central controller 31 of the system 30 via a first data connection 33, such as an Ethernet connection. Each partition control module ZM1 to ZM4 is provided with a LIN bus 341 to 344 (e.g., a partition LIN bus). Multiple LIN slave devices S can be connected to each LIN bus 341 to 344. LIN1 To S LINx The LIN slaves are assigned to different LIN hosts M LIN1 To M LINx Each LIN host M LIN1 To M LINx It is located in the central controller 31. For example, a device assigned to the first LIN host M is connected to the first LIN bus 341. LIN1 LIN slave S LIN1 It is also connected to, for example, a second LIN host M. LIN2 Second LIN slave S LIN2 And the connection is assigned to another, for example, a third LIN host M. LINx Another LIN slave S LINx Other slave devices on the LIN bus are also assigned to these masters. The masters, together with the assigned slave devices, form functional LIN buses, where the LIN slaves are physically distributed and coupled to the respective partition LIN buses. All masters of system 30 can be located in the central controller 31.

[0077] Therefore, the difference between a partitioned LIN bus and a functional LIN bus is, for example, that a functional LIN bus has only one LIN master and one LIN slave, while a partitioned LIN bus in a region of the system connects LIN slaves of different LIN masters. For example, in a system 31 with four regions, there can be exactly three LIN masters, because this provides an advantage in terms of bus load of four LIN buses.

[0078] Using a partitioning system 31, for example, allows for a thinner cabling configuration in the vehicle. These zones are connected by a backbone bus (such as the first data connection 33). Buses such as LIN, CAN, and FlexRay interface with so-called zone modules (such as zone control modules ZM1 to ZM4). Other approaches, such as the LIN bus used in automotive cabling, are functionally organized, with each bus itself traversing the entire vehicle. In other approaches, the cabling may become very thick and heavy, resulting in high costs. According to other approaches, each LIN bus itself traverses the entire vehicle.

[0079] Each partition control module ZM1 through ZM4 can be connected to exactly one LIN bus, or alternatively, multiple LIN buses can be connected. For example, one LIN bus can be connected to each of the first two partition control modules ZM1 and ZM2, and two LIN buses can be connected to each of the other two partition control modules ZM3 and ZM4. This allows for greater system flexibility. For example, if a larger number of LIN messages need to be sent to the LIN slaves in a relevant area, two LIN buses can be used on such a partition control module. This, for example, can prevent LIN bus overload.

[0080] System 31 includes aspects of tunneling LIN information via a first data connection 33 and partitioning the LIN bus. During partitioning, LIN slaves are reassigned to the bus, allowing multiple LIN masters to (functionally) access the same physical (partitioned) LIN bus. Tunneling of LIN information can be based on unused time reserves in the LIN protocol (such as tolerance time), which are not required in suitable system designs. LIN information can be sent to or from LIN masters via the first data connection 33, specifically within the inter-frame space of the LIN bus protocol within a LIN frame.

[0081] As shown below Figure 4 As shown, it can also be found in Figure 3 Two or more LIN buses can be connected to the partition control modules respectively. For example, exactly one LIN bus can be connected to each of the two partition control modules (e.g., ...). Figure 3 (As shown) and connect two LIN buses to the other two partition control modules respectively (such as... Figure 4 (As shown).

[0082] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 3 The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1-2 ) or below (such as Figure 4-10 (This refers to one or more aspects mentioned in one or more embodiments described.)

[0083] Figure 4 A schematic example of a system 40 with a partition control module ZM is shown, on which two LIN buses 44a and 44b are connected. Two or more hosts M1 and M2 are provided in a modular control platform MCP (e.g., a highly integrated platform; e.g., a central controller). A first data connection 43 connects the modular control platform MCP to the partition module ZM (e.g., a partition integration module; e.g., a partition controller).

[0084] Slave devices S1 and S2 are connected to the first LIN bus 44a and the second LIN bus 44b, respectively. These slave devices are assigned to either the first master device M1 or the second master device M2 in the modular control platform MCP. Since LIN information for the first or second LIN buses 44a and 44b is received on the partition control module ZM, a scheduler device D is provided in the partition control module ZM. This scheduler device controls when and which LIN information is transmitted from the partition control module ZM to the corresponding LIN buses 44a and 44b. For example, a separate scheduler can be provided for each LIN bus 44a and 44b of the partition control module ZM in the scheduler device D, and / or other components (e.g., components for the transmission branches from the first data connection to the LIN bus, which are also...) can be provided. Figure 5a As shown in the diagram; for example, filters and / or wait queues and / or transmit / receive modules). According to the proposed scheme of a partitioned LIN bus with divided regions, for example, time constraints in the host are removed and a scheduler is introduced for the partitioned LIN bus, for example, with wait queues as quasi-dynamic scheduling tables.

[0085] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 4 The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1-3 ) or below (such as Figure 5a-10 (This refers to one or more aspects mentioned in one or more embodiments described.)

[0086] Figure 5a Figure 5b illustrates an example of data transmission in a synchronously operating partitioned system 50. The partitioned system 50 includes a central controller 51 and a partition control module 52, which are connected via a first data connection 53. A first LIN host M is configured in the central controller 51 to send LIN information A (such as message headers and data information) according to a time protocol (e.g., a LIN schedule). A Accordingly, a second LIN host M is constructed to send LIN information B (such as message headers and data information) according to the time protocol. BAnd the third LIN host M that sends LIN information C (such as message headers and data information) according to the time protocol. C LIN messages can be transmitted to the first data connection 53 via the central controller 51. The timing protocol can, for example, specify that LIN messages A, B, and C are sent in 5ms or 10ms time slots under normal circumstances.

[0087] The partitioning module 52 shown illustrates a signal processing branch for partitioning the LIN bus 58. This signal branch includes a filter 54, a LIN bus scheduling module 55, a scheduler 56, and a transmit / receive module 57 (e.g., a transceiver, such as a physical bus driver), through which header information can be exchanged between the first data connection 53 and the partitioned LIN bus 58. Other filters 54a and 54b of other signal branches are also shown, which can lead to other (in...) Figure 5a (Not shown) Partition LIN bus, which can also be connected to partition control module 52.

[0088] Synchronous operation is required only when the LIN host M... A M B M C When the LIN master M receives the corresponding response information from the LIN slave for the previously sent message header information, A M B M C Only then is another header message sent. This allows the waiting queue in scheduling module 55 to hold a maximum of each host M. A M B M C A message header (e.g., in a wait loop (Warteschleife) can exist on the first LIN host M) A A message header information A, second LIN host M B A message header information B and a third LIN host M C A third message header information (C).

[0089] For example, if only one of the three LIN hosts sends the message header information, the corresponding response information can be sent to the designated LIN slave on the partitioned LIN bus 58 via the first data connection 53 within the specified time slot, and the corresponding response information can also be sent back to the LIN host via the first data connection 53.

[0090] The wait loop (e.g., buffer) function in scheduling module 55 enables all three LIN hosts M A M B M CWhen sending message headers A, B, and C simultaneously, these message headers can be cached and then sent to the LIN bus 58 when it is available, according to the transmission protocol.

[0091] The raw function scheduling of the LIN host can be run centrally (e.g., on an integrated platform) and implemented, for example, in parallel as a software implementation. The LIN host can transmit LIN message headers (Tx mode) via a tunnel through the first data connection 53 (e.g., the backbone bus), but scheduling can be halted until the LIN host receives a response to the message header. LIN message headers from different LIN hosts can be stored in chronological order in an Rx buffer (e.g., the buffer of the partition control module 52). The oldest message header in the Rx buffer can be sent from the buffer, for example, by means of the scheduler 56 (e.g., following a first-in, first-out (FIFO) principle). Once the response to the message header has been fully and correctly transmitted onto the physical LIN bus, the response can be sent to the corresponding host via the backbone bus.

[0092] Figure 5b Showing when all three hosts M A M B M C Simultaneously, the schematic time process of sending LIN messages A, B, and C to the partition module 52 via the first data connection 53 is illustrated. As shown in the figure, the scheduler 56 first selects LIN message C from the waiting queue to transmit it to the LIN bus 58. The LIN slave 15 connected to the LIN bus can process the LIN message (such as message header information) C and send it back to the LIN master M. C (As a response message). For this purpose, a duration t1 can be specified, which may correspond to a time slot in the LIN protocol (e.g., 10 ms). Once the LIN bus 58 is idle, the scheduler 56 can transmit the second LIN message B to the LIN bus 58, for example, in a time slot following the transmission of the first LIN message A. Correspondingly, once the LIN bus 58 is idle, the scheduler 56 can transmit the third LIN message A to the LIN bus 58, for example, in a time slot following the transmission of the second LIN message B.

[0093] Therefore, this example illustrates the worst-case scenario for synchronous transmission, where a header collision occurs. Three headers are sent simultaneously. For the first host M... A The message header response is delayed by two time slots on the partitioned LIN bus 58. For the second host M B The response to the message header is delayed by one time slot on the partitioned LIN bus, while the third host M... CThe message headers can be delivered immediately. The hosts and their underlying functionality within the integrated platform are therefore designed to handle occasional delays in the response. For the hosts, for example, the strict constraints on the original LIN timeslots (such as 5 or 10 ms timeslots) can be relaxed. The wait queue can be designed to be no longer than the number of hosts in synchronous operation (e.g., a correspondingly small buffer is sufficient; for example, the buffer capacity can be configured to cache a maximum number of message headers corresponding to the number of LIN hosts in the system; for example, reserves can be set in the buffer to compensate for time delays at the scheduler).

[0094] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 5a , 5b The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1-4 ) or below (such as Figure 6-10 (This refers to one or more aspects mentioned in one or more embodiments described.)

[0095] Figure 6 This illustrates an example of data transmission in a partitioned system 50 operating asynchronously. In contrast to synchronous operation, the LIN master transmits the LIN message header via a tunnel through the first data connection 53 (e.g., the backbone bus in the sending operation Tx), but does not wait for a response (Rx) from the corresponding LIN slave until the LIN master sends additional LIN information. Since unpredictable ordering may occur here, in order to assign response information to the message header information, it can be specified that the response, along with the message header ID, is sent back to the corresponding master via the backbone bus.

[0096] In asynchronous operation, the waiting queue (e.g., in scheduling module 55) can also be larger than the number of participants (e.g., multiple LIN messages A (e.g., two, three, or more) and multiple LIN messages B, C can be cached). System 50 can, for example, be designed to not exceed the permissible bus load of the partitioned LIN bus on average. A limit value less than 100% (e.g., less than 90%, less than 80%, or less than 70%) can be determined for the permissible bus load.

[0097] The bus load of the partitioned LIN bus can affect the system. Under normal load (e.g., bus load < 95%), the wait queue can be kept from overflowing, the average cycle time is approximately the cycle time of the functional master scheduler, and the system does not require synchronization. When needed, wait times can be added, for example, to the scheduling module to temporarily prevent the LIN bus from becoming overloaded. Thus, for example, an average cycle time with smaller fluctuations can be maintained. Under high load (e.g., bus load > 95%), algorithms can be specified to remove, for example, duplicate messages from the wait queue and prevent overflow. The system can be constructed such that a short dead time is generated on the physical LIN bus (e.g., partitioned LIN bus 58). This allows the system to avoid synchronization; for example, the cycle time can be subject to greater fluctuations.

[0098] Synchronous Tx / Rx operation (see also) Figure 5a b) can be described as flexible operation. This involves setting up partitioned LIN node devices, where dual-occupancy PIDs are not permitted, for example, in a partitioned LIN bus system. Schedulers can coordinate with each other to prevent dead time and temporary overload on the bus. Self-synchronization can be used, for example. Conversely, new functional timings can be specified in asynchronous Tx / Rx operation. Dual-occupancy PIDs are not permitted in partitioned LIN node devices, for example, in a partitioned LIN bus system, and bus load has a significant impact on timing compliance, for example.

[0099] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 5a , 5b The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1-5b The above or one or more aspects mentioned in one or more embodiments described below (as shown in Figures 7-10).

[0100] Figure 7 illustrates an example of a conventional system with multiple LIN buses 140, 140b, and 140n according to the prior art. All LIN buses 140, 140b, and 140n are directly connected to a controller 110, which has corresponding LIN masters 110a, 110b, and 110n assigned to each bus. Compared to the proposed partitioned system 10 with a first data connection 13, the need for transmission cables increases with each additional LIN bus because there is no common transmission cable available for multiple LIN buses. Furthermore, according to the prior art, a separate LIN bus must be used for each LIN master.

[0101] Figure 8 This is shown via the first data connection 13 (e.g., CAN bus or Ethernet connection; see [link]). Figure 8An example of transmitting message header information H and response information R via the LIN bus 14 (see the upper half). Time slot 80 is used so that the message header information H and response information R can be transmitted via the LIN bus 14 (see the upper half). Figure 8 The lower half of the transmission includes a frame containing a message header (message header information H) and a response or slave response (response information R). The length of slot 80 shown is purely exemplary and could be 5 ms or other durations instead of the shown 10 ms.

[0102] As can be seen, the first part of time slot 80 is sufficient for transmitting message header information H and response information R via LIN bus 14, therefore an idle time window 81 exists before the start of the next time slot, and this idle time window can be utilized, for example. The duration of time window 81 is approximately 33% of the duration of time slot 80 (e.g., at most 40% and / or at least 20% of the duration of time slot 80). Idle time window 81 can be provided when the tolerance time defined in the LIN transmission standard is not required for transmitting LIN frames.

[0103] The idle time window 81—during which no information is transmitted via the LIN bus 14—can be used to transmit the response information R back to the LIN host in the central controller via the first data connection 13 (e.g., tunneling the response information R). Additionally, another header information H is used to transmit the message header via the LIN bus 14 in the next time slot. n+1 It can be sent from the LIN host to the partition control module via the first data connection 13. The message header information R for the LIN frame used for the displayed time slot 80 has already been transmitted accordingly in the idle time window of the previous time slot (see the message header information H on the first data connection 13 between the start of time slot 80 and the start of time slot 80). Therefore, the duration from the transmission of message header information H via the first data connection 13 until the receipt of the matching response information R via the first data connection 13 can be a shorter duration than the duration of time slot 80.

[0104] For example, to transmit header and response information (e.g., LIN frames) via the LIN bus, predetermined time slots (e.g., 5 ms or 10 ms time slots as specified by LIN transmission) can be used. Furthermore, it is specified that response information and / or another header information are transmitted via the first data connection within a time window reserved in the time slot. The availability of the time window can be achieved such that the tolerance time reserved in the time slot according to the LIN standard does not need to be used for transmission on the LIN bus. As mentioned above, this can be achieved, for example, by using a hardware-based microcontroller when implementing the LIN master and / or LIN slave.

[0105] For example, it can be specified that the message header is transmitted on the LIN bus at the beginning of a time slot. Therefore, an idle time window can be provided at the end of the time slot. Before reaching the time window within the time slot, a response can be received at the partition control module via the LIN bus, allowing the corresponding response information to be sent to the LIN master via the first data connection within the idle time window. To send the corresponding next message header via the LIN bus in subsequent time slots, for example, the message header information for subsequent time slots can also be sent to the partition control module via the first data connection within the time window. Figure 8 As shown in the diagram. Therefore, in general, the header and response information of a frame (such as a LIN bus frame) can be sent by the LIN master and received again at the LIN master via the first data connection within the specified duration of the time slot (e.g., shifted to the actual time slot on the LIN bus). Thus, time delays when controlling LIN slaves can also be avoided when using the first data connection.

[0106] According to one embodiment, the reserved time window has a duration of at least 0.2 ms (or at least 0.5 ms, at least 1 ms, at least 1.5 ms, or at least 2 ms) and / or up to 5 ms (or up to 4 ms or up to 3.5 ms). During this time, message header information and / or response information may be transmitted, for example, via a first data connection between the central controller and the partition control module.

[0107] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 8 The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1 -7) or below (e.g. Figure 9-10 (This refers to one or more aspects mentioned in one or more embodiments described.)

[0108] Figure 9 This shows the time offset t. off An example of transmitting multiple frames f1, f2, and f3 via the first data connection 13 to multiple LIN buses 14, 44a, and 44b. Time offset t off For example, the duration between the start of the first header information H and the start of the next header information H2 can be described. For example, the transmission of the header information via the first data connection 13 can last 50 to 60 μs with a time offset t. off It can be 100 μs. For example, time offset t. off The duration between the end of the transmission of message header information H and the start of the transmission of message header information H2 can be defined, and for example, greater than 10 μs and / or less than 50 μs.

[0109] Message header information H, H2, and H3 are successively sent from different LIN hosts to different LIN buses 14, 44a, and 44b, respectively, via the first data connection 13. For example, message header information H, H2, and H3 can also be sent from a single LIN host to different partition control modules or a single partition control module (for example, multiple LIN buses and / or LIN slaves assigned to that LIN host can be connected to the partition control module; for example, message header information H, H2, and H3 can be buffered in the partition control module's buffer until transmission via the LIN bus). It can be seen that the slower data transmission of frames f1, f2, and f3 via LIN buses 14, 44a, and 44b takes longer than the data transmission of message header information and response information via the first data connection 13. Therefore, other message header information H2, H3, etc., can be sent from other LIN hosts via the first data connection 13 after the first message header information H is sent from the first LIN host, for example, when frame f1 is transmitted via LIN bus 14. For example, the maximum possible number of header messages H, H2, H3, etc., that can be sent via the common data connection 13 can depend on the data transmission speed and / or time offset t. off The length and / or frame duration f1. For example, the time offset t can be selected like this. off This allows a response message to be transmitted via the first data connection 13 between the transmission of two successive header messages, so as to enable, for example, the continuous alternation of header and response messages via the first data connection 13.

[0110] With offset t off Synchronization of LIN hosts can be achieved, for example, through conflict-free scheduling on the backbone bus (e.g., the first data connection 13). For instance, the time slots of LIN buses 14, 44a, and 44b are set with time offsets. Using synchronization or time offsets allows multiple LIN hosts to continuously send additional message headers for subsequent LIN frames to their respective LIN buses 14, 44a, and 44b via the first data connection 13 without conflicts occurring on the first data connection 13.

[0111] According to one embodiment, the method further includes a second LIN host of the central controller sending second header information via a first data connection. The transmission of these two header information is, for example, time-shifted to a time offset selected based on the data transmission speed of the first data connection.

[0112] The first header message is sent to a LIN slave, for example, on the first LIN bus, and the second time-shifted header message is sent to a LIN slave on the same first LIN bus or alternatively on a second LIN bus (e.g., coupled to the same or different partition control modules). Since the data transfer rate of the first data connection is greater than that of the LIN bus, the two header messages can be transmitted on a common data line. Using a time offset avoids conflicts in the header messages on the first data connection.

[0113] For example, a time offset of at least 20 μs (or at least 50 μs or at least 100 μs) can be selected between the transmission of two header messages via the first data connection. Alternatively, the time offset can be selected such that the corresponding response information can be transmitted back to the corresponding LIN host via the first data connection without conflicting with subsequent header messages on the first data connection. This, for example, avoids collision-based latency.

[0114] Therefore, in summary, the example relates to a scheme for tunneling a LIN bus 14 via a backbone bus (such as a first data connection 13, such as a CAN bus or an Ethernet connection). To enable finer, cheaper, and / or better automated cable bundle manufacturing, one or more backbone buses (such as the first data connection) are introduced, through which buses such as LIN, CAN, FlexRay, and discrete signal lines can be tunneled.

[0115] In particular, the tolerances present in the LIN specification can be fully utilized. In modern microcontrollers (μCs) with hardware LIN logic (such as hardware support), these tolerances (e.g., idle time window 51) are no longer needed, for example, on the LIN bus. LIN masters on a LIN bus that should be tunneled together can use time offsets for synchronization. For example, time buffers (e.g., time window 51) can be provided for tunneled connections of the LIN bus. In the case of tunneling multiple LIN buses on the same backbone bus, conflicts can be avoided using the proposed scheme. For example, multiple LIN buses can be deployed from the central controller to the rear controller and / or roof controller.

[0116] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 9 The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1-8 ) or below (such as Figure 10 (This refers to one or more aspects mentioned in one or more embodiments described.)

[0117] Figure 10A schematic example of a system 90 is shown, which has a central controller 91 and a partition control module 92 connected to multiple different legacy buses. The partition control module 92 is connected to the central controller 91 via a first data connection 93 for efficient data connectivity (e.g., faster data transfer than via legacy buses).

[0118] A first legacy bus 94a and a second legacy bus 92b (or alternatively, discrete signal line 92b) are connected to the partition control module 92. The first legacy bus 92a may be, for example, a LIN bus and the second legacy bus 92b may be, for example, a CAN bus. A first data connection 93 enables the controllers of the legacy buses 94a and 94b to send information to and receive information from the central controller 91 (e.g., communication between the LIN master in the central controller 91 and the LIN slave on the LIN bus 94a).

[0119] For example, in a system 90 with two partition control modules, multiple buses can be connected to each partition control module. For instance, a LIN bus, a CAN bus, and a FlexRay bus can be connected to the first partition control module, and a LIN bus, a CAN bus, and a partition Ethernet connection can be connected to the second partition control module. By integrating all functions into a central controller 91, advanced functions (such as service-oriented architecture, SOA) can be implemented. Through the central controller 91, the system 90 can efficiently connect (e.g., wirelessly) to a backend, so that a common backend connection can satisfy all the functions of the individual controllers on the partition control module buses.

[0120] By combining a partition control module with a primary data connection (e.g., a backbone bus), current legacy functions, along with their legacy controllers (e.g., LIN or CAN controllers), can be converted to a partitioned physical vehicle network architecture with relatively low overhead. Cost advantages can be achieved because cabling can be manufactured automatically, for example. The system can achieve high scalability and flexibility. For example, hybrid mode and discrete signal buses can be connected together to the partition control module. In other words, the central interface between the "all-IP" and "service-oriented architecture" software world and the legacy (signal-based) world can be realized through the backbone bus, enabling older technologies in the vehicle field to be integrated with modern technologies.

[0121] Figure 10The system 90 proposed can, for example, be used in a motor vehicle with a partitioned in-vehicle network having a legacy abstraction and backbone bus. In this way, a large number of different electrical / electronic components can be integrated into a modern in-vehicle network (e.g., via Ethernet connection). In the illustrated system 90, the partition control module 92 can, for example, be referred to as a legacy abstraction switch (e.g., a universal gateway for various legacy buses). One advantage is that a configurable partition control module 92 can be used, which can be programmed accordingly based on the actual legacy buses 94a, 94b used (e.g., to operate as a gateway for the corresponding legacy buses 94b, 94a through appropriate software settings). This universal partition control module 92 can have the advantage of being used in different configurations, thereby saving costs, for example.

[0122] Other details and aspects are mentioned in conjunction with the embodiments described above or below. Figure 10 The embodiments shown may include one or more optional additional features, which correspond to the combination of the proposed scheme or the above (e.g.) Figure 1-9 (or one or more aspects mentioned in one or more embodiments described below).

[0123] Regarding fault diagnosis in the introduced system and method—which can follow the principles of fault diagnosis according to the LIN specification—it can be specified that fault information is also transmitted via the first data connection. Each LIN node performs diagnosis independently, for example, to identify faults on the (partitioned) LIN bus. Fault evaluation is performed centrally by the master. The master reads and evaluates all communications on the bus together, for example. Slaves read and evaluate all messages they send and receive together on the bus; slaves are allowed to transmit fault status in the payload (response) within the error bits of unconditional frames. The master evaluates the error bits of the slaves, for example. Fault identification is performed at the slaves, for example, independently of partitioning, through the payload in the slave responses. Fault identification for the master is undertaken by the scheduler, for example, in the case of partitioning, and is sent to the central LIN master via a separate status message. The system can be configured for fault diagnosis such that the status / condition of backbone communications (e.g., communications via the first data connection) can be notified to the LIN master on the integrated platform (e.g., the central controller).

[0124] The proposed aspect relates to the partitioning of a functional LIN bus architecture in motor vehicles. Unlike other LIN systems, it can be specified that LIN slaves of different LIN masters share a partitioned LIN bus, thereby enabling systems with distributed LIN slaves, for example, with lower cabling requirements for the LIN bus. Here, for example, a large number of communication buses in the vehicle can be converted from functional connections of the controller according to other schemes to partitioned connections of the controller, which can reduce cabling and / or improve flexibility. In particular, a scheme for connecting the LIN bus is proposed.

Claims

1. A system (10) for transmitting data in a motor vehicle, the system (10) comprising: A central controller (11) is configured with at least one first LIN host (11a) and a second LIN host (11b). A partition control module (12, ZM1) is coupled to the central controller (11) via a first data connection (13); and A LIN bus (14, 341) is coupled to the partition control module (12, ZM1). The first LIN slave (15a) connected to the LIN bus (14, 341) is assigned to the first LIN master (11a), and the second LIN slave (15b) connected to the LIN bus (14, 341) is assigned to the second LIN master (11b), so that at least two LIN slaves assigned to different LIN masters can use a common LIN bus. The data transmission speed of the first data connection (13) between the central controller (11) and the partition control module is higher than that of the LIN bus (14).

2. The system (10) of claim 1, wherein, The system also includes: At least one additional partition control module (ZM2), which is coupled to the central controller (11, 31) via a first data connection (13, 33); and At least one additional LIN bus (342), said additional LIN bus being coupled to said additional partition control module (ZM2), At least one LIN slave assigned to the first LIN master (11a) and / or a LIN slave assigned to the second LIN master (11b) is connected to the additional LIN bus (342) of the additional partition control module (ZM2).

3. The system (10) according to claim 2, wherein, The partition control modules (12, ZM1, ZM2) are configured to filter out only the message headers of the corresponding LIN hosts transmitted via the first data connection (13), which address the LIN slaves connected to the corresponding LIN buses (14, 341, 342) of the partition control modules (12, ZM1, ZM2).

4. The system (10) according to any one of claims 1 to 3, wherein, A LIN bus (14) is coupled to the partition control module (12).

5. The system (10) according to any one of claims 1 to 3, wherein, The partition control module (12) is configured to control the timing of the transmission of message headers of the first LIN host (11a) and the second LIN host (11b) received on the partition control module (12) to the LIN bus (14) based on communication behavior.

6. The system (10) according to claim 5, wherein, The communication behavior specifies synchronous transmission. In the synchronous transmission, if the corresponding LIN host does not receive a response corresponding to the last sent message header, the LIN host will not send another message header. The response is transmitted from the LIN slave to the LIN host via the LIN bus (14), the partition control module (12), and the first data connection (13).

7. The system (10) according to claim 5, wherein, The communication behavior specifies asynchronous transmission. In the asynchronous transmission, even if the corresponding LIN host has not yet received the response corresponding to the last sent message header, the LIN host also sends another message header. The partition control module (12) transmits the response together with the matching message header or the matching message header ID to the LIN host via the first data connection (13) so that the allocation of the message header in the response can be implemented on the LIN host.

8. The system (10, 30, 40) according to any one of claims 1 to 3, wherein, The system (10, 30, 40) includes multiple LIN hosts in the central controller (11) and multiple partition control modules (ZM1, ZM2, ZM3, ZM4) with their own LIN buses (341, 342, 343, 344).

9. The system (10) according to claim 8, wherein, The number of LIN buses (341, 342, 343, 344) in the system (10) is greater than the number of LIN hosts in the system (10).

10. The system (10) according to any one of claims 1 to 3, wherein, The partition control module (12) has a buffer (55) so that it can cache the message header received from the corresponding LIN host for such a long time that the LIN bus (14) becomes available for transmitting the message header.

11. The system (10) according to any one of claims 1 to 3, wherein, The partition control module (12) is configured to send fault information about the LIN bus (14) and / or the first data connection (13) to the corresponding LIN host of the central controller (11).

12. The system (10) according to any one of claims 1 to 3, wherein, The first data connection (13) is constructed according to Ethernet standard, CAN standard, FlexRay standard, radio-based transmission standard, PCI Express standard or home network standard.

13. The system (10) according to any one of claims 1 to 3, wherein, The corresponding LIN master and / or corresponding LIN slave are hardware-supported on the microcontroller used for this purpose.

14. The system (10) according to any one of claims 1 to 3, wherein, The system (10) is configured to transmit the frame via the LIN bus and the corresponding message header and response information via the first data connection during the duration of a predefined time slot (80) for transmitting the frame via the LIN bus (14).

15. The system (10) according to any one of claims 1 to 3, wherein, The system is configured to send header information of at least two LIN hosts in a common data packet via a first data connection (13).

16. The system (10) according to any one of claims 1 to 3, wherein, The partition control module (12) is also connected to an old bus and / or discrete signal lines with corresponding controllers, and / or the system (10) has another partition control module together with an old bus and / or discrete signal lines with corresponding controllers, the system being configured to transmit information from the old bus to the central controller (11) via a first data connection (13).

17. A motor vehicle having the system (10) according to any one of claims 1 to 16, wherein, The system (10) has at least two zone control modules (ZM1, ZM2) respectively located in different zones of the motor vehicle.

18. A method (20) for controlling at least one first LIN slave (15a) and a second LIN slave (15b) in a system according to any one of claims 1 to 16, the first LIN slave and the second LIN slave being connected to a common LIN bus (14), the method (20) comprising: The first LIN master (11a) sends (21) first message header information to the first LIN slave (15a) via the common LIN bus (14); The second LIN master (11b) sends (22) the second message header information to the second LIN slave (15b) via the common LIN bus (14); The first LIN host (11a) receives (23) the response information corresponding to the first message header information from the first LIN slave (15a); as well as The second LIN master (11b) receives (24) the response information corresponding to the second message header information from the second LIN slave (15b).

Images