Data exchange device and data exchange method for a vehicle, device and method for a vehicle component of a vehicle, and computer program

Abstract

The invention relates to a data exchange device and a data exchange method for a vehicle, a device and a method for a vehicle component of a vehicle, and a computer program. A data exchange device (10) comprises at least one interface (12), which is configured to communicate with a first plurality of vehicle components (30) of the vehicle (100) and to communicate with a second plurality of vehicle components (40) of the vehicle (100). The data exchange device (10) further comprises a control module (14), which is configured to communicate with the first plurality of vehicle components (30) of the vehicle based on at least one first data format and to communicate with the second plurality of vehicle components (40) of the vehicle based on at least one second data format. The control module (14) is configured to provide a communication interface for communication between the first plurality of vehicle components (30) and the second plurality of vehicle components (40). The control module (14) is configured to provide access to first information of the first plurality of vehicle components (30) by providing second information for the second plurality of vehicle components (40). The first information is based on at least one first data format. The second information is based on at least one second data format.

Description

Technical Field

[0001] The invention relates to a data exchange device and a data exchange method for a vehicle, a device and a method for a vehicle component of a vehicle, and a computer program. Background Art

[0002] Vehicles usually include a large number of vehicle components, from the sensors and actuators of the engine via the control device of the heating function to the infotainment system (an abbreviation for a system for information and entertainment / recreation). Since these vehicle components are mostly not used in isolation, but rather exchange data with each other, communication protocols and networks have been created for decades, which are used to network different vehicle components. For example, in many vehicles, these vehicle components are connected to each other via a star network architecture, in which a central gateway (Gateway, English for relay point) is used to provide communication between different components. The communication between vehicle components with actuators and sensors is mostly based on hardware-related communication protocols, which are optimized in the following aspects: requiring as little transmission capacity as possible and as low processing power as possible. Since most of these components come from multiple suppliers, most of these components also use the following communication protocols, which are compatible with a large number of vehicle manufacturers and therefore usually do not fully utilize the various possibilities of modern communication protocols. On the other hand, there are also a number of vehicle components, such as infotainment systems, which have powerful processors and are therefore able to handle more complex protocols which offer greater possibilities. Summary of the invention

[0003] There is a need for improved solutions for communication within a vehicle, which take into account not only the capabilities of less complex actuators and sensors but also the capabilities of vehicle components with efficient processors.

[0004] The embodiment thus creates a data exchange device for a vehicle. The data exchange device can be used to provide an exchange between a "simpler" protocol of an actuator / sensor (which is based on at least one first data format) and a more complex protocol (which is based on at least one second data format). To this end, the data exchange device in a simple form only provides an assignment of data equivalents between at least one first data format and at least one second data format. Optionally, the data exchange device provides a conversion between the two data formats, resolves redundancies in the data, prepares the data for retrieval or performs the transmission of error flags if the data cannot be transmitted without errors.

[0005] Embodiments create a data exchange device for a vehicle. The device includes at least one interface, which is configured to communicate with a first plurality of vehicle components of the vehicle and to communicate with a second plurality of vehicle components of the vehicle. The device further includes a control module, which is configured to communicate with a first plurality of vehicle components of the vehicle based on at least one first data format and to communicate with a second plurality of vehicle components of the vehicle based on at least one second data format. The control module is configured to provide a communication interface for communicating between the first plurality of vehicle components and the second plurality of vehicle components. The control module is configured to provide access to first information of the first plurality of vehicle components by providing second information for the second plurality of vehicle components, wherein the first information is based on at least one first data format, and wherein the second information is based on at least one second data format. By providing a communication interface, the second plurality of vehicle components that communicate based on at least one second data format can use data or trigger functions of the first plurality of vehicle components that communicate based on at least one first data format. Thus, those of the second plurality of vehicle components may use more complex and powerful protocols for communications without losing access to the first plurality of vehicle components.

[0006] In at least some embodiments, the control module is configured to provide conversion between at least one first data format and at least one second data format for communication between the first plurality of vehicle components and the second plurality of vehicle components. This enables a universal communication interface to be provided for the second plurality of vehicle components, regardless of which data type and communication protocol the first plurality of vehicle components are communicating based on.

[0007] The control module can also be configured to resolve at least one redundant information in the first information of the first plurality of vehicle components. This enables uniform access to the data of the first plurality of vehicle components, since during access, a plurality of the second plurality of vehicle components always provide information from the same source or sources.

[0008] In some embodiments, the control module is configured to provide end-to-end secure communication between a first vehicle component in the first plurality of vehicle components and a second vehicle component in the second plurality of vehicle components. In at least some embodiments, this enables trusted communication between a vehicle component in the first plurality of vehicle components and a vehicle component in the second plurality of vehicle components.

[0009] For example, the control module can be configured to ensure end-to-end secure communication by determining at least one transmission error and / or forwarding information about at least one transmission error. This can enable the vehicle component to recognize errors in the communication and take error handling measures despite the communication via the provided communication interface.

[0010] For example, the control module may be configured to convert error flags of communications based on a first data format of a first plurality of vehicle components into a second data format and provide to a second plurality of vehicle components. The control module may be configured to convert error flags of communications based on a second data format of a second plurality of vehicle components into the first data format and provide to the first plurality of vehicle components. This may enable the vehicle components to identify errors in communications and take error handling measures despite communications via the provided communication interface.

[0011] In some embodiments, at least one vehicle component may be included in the first plurality of vehicle components and in the second plurality of vehicle components. Thus, for example, the data exchange device may be used to provide auxiliary functions for a large number of vehicle components, such as calculating values ​​used by a plurality of vehicle components.

[0012] The first plurality of vehicle components may correspond, for example, to a plurality of control devices for operating vehicle sensors and / or for operating vehicle actuators. The second plurality of vehicle components may include a plurality of computing units of the vehicle. Thus, for example, the data exchange device may be used to provide data of the control devices for operating vehicle sensors or vehicle actuators to these computing units based on a large number of data formats.

[0013] In some embodiments, the control module is configured to provide a communication interface based on the configuration information. The control module can also be configured to obtain updated configuration information for refreshing the configuration information. Thus, for example, when replacing or updating a vehicle component (e.g., a vehicle component of the first plurality of vehicle components), only the configuration information of the data exchange device can be changed without having to adapt the configuration of the second plurality of vehicle components.

[0014] The control module can be configured to continuously obtain first information of the first plurality of vehicle components from the first plurality of vehicle components so as to determine second information based on the first information and provide it to the second plurality of vehicle components. This enables access to the second information with a small delay. The control module can be configured to continuously obtain first information of the first plurality of vehicle components from the first plurality of vehicle components. The control module can be configured to determine a timeout for obtaining the first information of the first plurality of vehicle components. Thus, for example, it can be prevented that a vehicle component in the first plurality of vehicle components fails, but this is not recognized by a vehicle component in the second plurality of vehicle components because data will continue to be provided.

[0015] In at least some embodiments, the control module is configured to provide the second information to the second plurality of vehicle components via an object-oriented programming interface. The second data format may be an object-oriented data format. This enables abstracted access to the first information for the second plurality of vehicle components.

[0016] Embodiments furthermore create a device for a vehicle component of a vehicle. The device comprises an interface, which is configured to communicate with a data exchange device of the vehicle. The device further comprises a control module, which is configured to use the data exchange device to access first information of a first plurality of vehicle components via the data exchange device in the form of second information based on a second data format, wherein the first information is based on the first data format. This enables the vehicle component to access the information of the first plurality of vehicle components without having to master their data format, which enables flexible replacement of these vehicle components.

[0017] Embodiments further create a data exchange method for a vehicle. The method includes: communicating with a first plurality of vehicle components of the vehicle based on at least one first data format. The method further includes: communicating with a second plurality of vehicle components of the vehicle based on at least one second data format. The method further includes: providing a communication interface for communicating between the first plurality of vehicle components and the second plurality of vehicle components. Providing the communication interface includes providing access to first information of the first plurality of vehicle components by providing second information for the second plurality of vehicle components. The first information is based on at least one first data format. The second information is based on at least one second data format.

[0018] Embodiments further provide a method for a vehicle component of a vehicle. The method includes communicating with a data exchange device of the vehicle. The method further includes using the data exchange device to access first information of a first plurality of vehicle components in the form of second information based on a second data format via the data exchange device, wherein the first information is based on the first data format.

[0019] Exemplary embodiments further provide a program having a program code for performing at least one of the methods, when the program code is executed on a computer, a processor, a controller or a programmable hardware component. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Further advantageous embodiments are described in more detail below based on the exemplary embodiments shown in the drawings, but are generally not limited to the exemplary embodiments as a whole.

[0021] Figure 1a A block diagram showing an embodiment of a data exchange device;

[0022] Figure 1b A flow chart showing an embodiment of a data exchange method;

[0023] Figure 2a A block diagram showing an apparatus for a vehicle component;

[0024] Figure 2b A flow chart illustrating one embodiment of a method for a vehicle component;

[0025] Figures 3a to 3c A schematic diagram showing communications between vehicle components of a vehicle;

[0026] Figure 4 A system overview showing an exemplary communication server;

[0027] Figures 5a to 5h illustrating an exemplary data model for service-oriented communications; and

[0028] Figure 6 A schematic diagram showing communications between vehicle components and a communication server. DETAILED DESCRIPTION

[0029] Various embodiments are now described in more detail with reference to the accompanying drawings, in which some embodiments are shown. In the drawings, the thickness and size of lines, layers and / or regions may be exaggerated for the sake of clarity.

[0030] In the following description of the drawings showing only some exemplary embodiments, the same reference numerals may denote identical or comparable components. In addition, general reference numerals may be used for components and objects that appear multiple times in the embodiments or drawings but are described together with respect to one or more features. Components or objects described with the same or general reference numerals may be implemented identically with respect to individual, multiple or all features (e.g. their dimensions), but may also be implemented differently if necessary, unless otherwise indicated explicitly or implicitly from the description.

[0031] Although the embodiments may be modified and altered in different ways, the embodiments are shown as examples in the figures and are described in detail herein. However, it should be clarified that it is not intended to limit the embodiments to the respective disclosed forms, but rather the embodiments should cover all functional and / or structural modifications, equivalents and alternatives within the scope of the present invention. Throughout the description of the figures, the same reference numerals represent the same or similar elements.

[0032] Note that an element that is referred to as being "connected" or "coupled" to another element may be directly connected or coupled to the other element, or there may be elements located between them. Conversely, if an element is referred to as being "directly connected" or "directly coupled" to another element, there are no elements located between them. Other terms used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.).

[0033] The terms used in this article are only used to describe specific embodiments and should not limit these embodiments. As used in this article, as long as the context does not clearly indicate otherwise, the singular forms "a" and "the" should also include plural forms. In addition, it should be clarified that expressions such as "comprising", "comprising ... ", "having", "including", "including ... " and / or "having ... " used in this article indicate the presence of the mentioned features, integers, steps, workflows, elements and / or parts, but do not exclude the presence or addition of one or more features, integers, steps, workflows, elements, parts and / or combinations thereof.

[0034] Unless otherwise defined, all terms (including technical and scientific terms) used in this document have the same meanings assigned to them by those of ordinary skill in the art to which these embodiments belong. It should also be clarified that, unless exhaustively defined herein, expressions, such as those defined in generally used dictionaries, can be interpreted as if they have the meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an idealized or overly formal sense.

[0035] Figure 1a A block diagram of a data exchange device 10 for a vehicle 100 is shown. Figure 1a In addition, a vehicle 100 is shown, which has a data exchange device 10, a first plurality of vehicle components 30 and a second plurality of vehicle components 40. The data exchange device 10 includes at least one interface 12, which is configured to communicate with the first plurality of vehicle components 30 of the vehicle 100 and to communicate with the second plurality of vehicle components 40 of the vehicle 100. The data exchange device also includes a control module 14, which is configured to communicate with the first plurality of vehicle components of the vehicle based on at least one first data format and to communicate with the second plurality of vehicle components of the vehicle based on at least one second data format. The control module 14 is configured to provide a communication interface for communication between the first plurality of vehicle components and the second plurality of vehicle components. The control module 14 is configured to provide access to the first information of the first plurality of vehicle components by providing second information for the second plurality of vehicle components. The first information is based on at least one first data format. The second information is based on at least one second data format. The at least one interface is coupled to the control module 14.

[0036] Figure 1b A flow chart of a (corresponding) data exchange method for a vehicle 100 is shown. The data exchange method comprises: communicating 110 with a first plurality of vehicle components of the vehicle based on at least one first data format. The data exchange method comprises: communicating 120 with a second plurality of vehicle components of the vehicle based on at least one second data format. The data exchange method comprises: providing 130 a communication interface for communication between the first plurality of vehicle components and the second plurality of vehicle components. Providing 130 the communication interface comprises: providing access to first information of the first plurality of vehicle components by providing second information for the second plurality of vehicle components. The method can be performed, for example, by a data exchange device and / or a computing unit of the vehicle.

[0037] The following description relates both to the data exchange device and to the data exchange method. In this case, the functional capabilities of the control module and the at least one interface correspond to the method steps of the data exchange method.

[0038] The embodiment is based on the use of a data exchange device 10 for providing a (simplified) communication between a first plurality and a second plurality of vehicle components. In this case, the data exchange device 10 is designed to provide, for example, a conversion of first information in a first data format into a second data format by assigning the content of first information in a first data format to a second data format and / or by converting the content of first information in a first data format into a second data format. The data exchange device can correspond, for example, to a vehicle data exchange device. The method steps of the data exchange method can be performed by a vehicle data exchange device (inside the vehicle).

[0039] Here, the control module 14 is configured to communicate with the first plurality of vehicle components and with the second plurality of vehicle components via at least one interface 12. To this end, for example, at least one interface 12 can be configured to communicate with the first plurality of vehicle components and with the second plurality of vehicle components via the same communication network, for example, via Ethernet. For example, the communication between the control module 14 and / or the interface 12 and the first and second plurality of vehicle components can be based on the same communication network, for example, a network based on Ethernet. Alternatively, at least one interface 12 can be configured to communicate with the first plurality of vehicle components and with the second plurality of vehicle components via different communication networks, for example, communicating with the first plurality of vehicle components via at least one first communication network and communicating with the second plurality of vehicle components via a second communication network. At least one first communication network can correspond to a control network bus (also in English: Controller Area Network Bus (controller local area network bus), CAN bus) and / or a local connection network (also in English: Local Interconnect Network (local interconnect network), LIN). For example, the second communication network can correspond to an Ethernet-based network.

[0040] The first plurality of vehicle components may, for example, correspond to a plurality of control devices for operating vehicle sensors and / or for operating vehicle actuators. For example, the first plurality of control devices may correspond to a plurality of microchips that are configured to provide control and / or communication for only one vehicle component, respectively. For example, the first plurality of vehicle components may include, for example, a plurality of control devices of a drive system of a vehicle, or correspond to said control devices. The plurality of control devices may, for example, have a lower computing power than a plurality of computing units of the vehicle 100, which may correspond to a second plurality of vehicle components of the vehicle.

[0041] For example, the second plurality of vehicle components may include a plurality of computing units of the vehicle 100. The second plurality of vehicle components may be, for example, a software-based vehicle component of the vehicle, such as a control device or a vehicle functionality, which is centrally executed on a plurality of computing units of the vehicle 100. For example, the second plurality of vehicle components may be a computing unit or a software-based vehicle component executed by a computing unit. In at least some embodiments, the first plurality of vehicle components are implemented by a dedicated application-specific microchip, while the second plurality of vehicle components are implemented by software designed to be executed by a central computing unit of the vehicle. In some embodiments, at least one vehicle component may be included in the first plurality of vehicle components and included in the second plurality of vehicle components. Therefore, for example, a software-based vehicle component may not only be included in the first plurality of vehicle components, so as to provide auxiliary functions for other vehicle components in the second plurality of vehicle components, but also may be included in the second plurality of vehicle components, so as to be able to use the first information of the first plurality of vehicle components.

[0042] The control module is configured to communicate with a first plurality of vehicle components based on at least one first data format and to communicate with a second plurality of vehicle components based on at least one second data format. The first information is based on at least one first data format. The second information is based on at least one second data format. For example, the first data format can result in a smaller message size than the second data format. For example, the first data format can be based on: the information to be transmitted has a fixed arrangement, such as a fixed bit position, within the data format. Therefore, the data transmitted via the first data format can use the following data type, which is large enough for the data to be transmitted but does not correspond to a multiple of 8 or 16 bits: if only 64 different values ​​are set, for example, only 6 bits can be set for some data. Differently, at least one second data format can be based on the following data type, which is based on a multiple of 8 bits (or 16 bits, 32 bits). For example, all data types of the at least one second data format can have a multiple of 8 bits. Such data types may be, for example, the data types "integer", "float", "double" (floating point numbers with 32-bit precision (float) or 64-bit precision (double)), "enum" or "boolean" (binary data type with the value true or false). For example, the second data format may be an object-oriented data format. The second data format may be based on structured text data, for example implemented similarly to eXtensible Markup Language (XML) or JavaScript Object Notation (JSON). In at least some embodiments, communication via the first data format corresponds to signal communication and communication via the second data format corresponds to business / service-oriented communication. In at least some embodiments, the second data format is based on SomeIP (Scalable serice-Oriented MiddlewarE over IP) or on ViWi (Volkswagen Infotainment WebInterface) protocol.

[0043] The control module 14 is configured to provide a communication interface for communication between a first plurality of vehicle components and a second plurality of vehicle components. The communication interface may be configured, for example, to provide second information for the second plurality of vehicle components to call and / or (actively) transmit the second information of the second plurality of vehicle components. The control module 14 may be configured to continuously (e.g., periodically or based on an event) obtain (e.g., receive or call) first information of the first plurality of vehicle components from the first plurality of vehicle components so as to determine the second information based on the first information and provide it to the second plurality of vehicle components. The communication interface may be configured to: once the first plurality of vehicle components provide the first information, the first information is received from the first plurality of vehicle components, or the first information is called from the first plurality of vehicle components (periodically or based on an event). In at least some embodiments, the control module 14 is further configured to, for example, store the first information and / or the second information in a storage module. For example, the data exchange device may include a storage module.

[0044] In at least some embodiments, the control module 14 can also be configured to continuously (e.g., periodically or based on an event) obtain (e.g., receive or call) first information of the first plurality of vehicle components from the first plurality of vehicle components, wherein the control module 14 is configured to determine a timeout (also in English: Timeout) for obtaining the first information of the first plurality of vehicle components. For example, the control module 14 can be configured to provide an error notification and / or an error flag for the second plurality of vehicle components if a timeout has been determined for obtaining the first information of the first plurality of vehicle components. Alternatively or additionally, the control module 14 can be configured to output an error value or a zero value when providing second information corresponding to the first information if a timeout has been determined for obtaining the first information of the first plurality of vehicle components.

[0045] In at least some embodiments, the second information is based on the first information. For example, the content of the second information may correspond to the content of the first information or may be based on the content of the first information. The second information may correspond to a processed, for example, classified, filtered and / or converted version of the first information. For example, the control module 14 may be constructed to provide the second information to the second plurality of vehicle components via an object-oriented programming interface. For example, the control module 14 may be constructed to provide the content and / or functionality of the first information by providing the second information to the second plurality of vehicle components via an object-oriented programming interface. Here, the content may be, for example, a value, such as state information or a sensor value of the first plurality of vehicle components, and the functionality may represent the possibility of triggering the functionality of a vehicle component in the first plurality of vehicle components. For example, the second information may be designed to provide the content of the first information via a query access function (also in English: accessormethods (accessor method)) and provide access to the functionality of the first plurality of vehicle components via an object method.

[0046] In at least some embodiments, the control module 14 is further configured to provide conversion between at least one first data format and at least one second data format for communication between a first plurality of vehicle components and a second plurality of vehicle components. For example, the control module 14 may be configured to provide conversion between a data type of at least one first data format and a data type of at least one second data format. The control module 14 may be configured to provide conversion between a refresh rate (also in English: Refresh Rate) in the first data format and a refresh rate in the first data format. In at least some embodiments, the control module 14 may be configured to provide conversion between event-based communication and periodic communication between the first data format and the second data format (and vice versa). In at least some embodiments, the at least one first data format and the at least one second data format are different.

[0047] For example, the control module 14 can also be configured to resolve at least one redundant information in the first information of the first plurality of vehicle components. For example, the control module 14 can be configured to determine one of the second information based on at least two redundant information of the first information, for example based on a selection of information from the two redundant information, based on an average value, a combined value or an interpolated value of the two redundant information, or based on other transformations of the two redundant information.

[0048] In some embodiments, the control module is configured to provide end-to-end communication between a first vehicle component and a second vehicle component of a first plurality of vehicle components. For example, ensuring safe communication may involve identifying transmission errors. The control module 14 can be configured to notify and / or forward the transmission error in the communication between the first vehicle component and the second vehicle component to the first and / or second vehicle component. The control module 14 can be configured to protect the communication that ensures safety end-to-end by determining at least one transmission error and / or passing information about at least one transmission error. Then the transmission error notification, transmission or display can be given to the first and / or second vehicle component. For example, the control module 14 can be configured to convert the error flag of the communication based on the first data format of the first plurality of vehicle components into the second data format and provide it to the second plurality of vehicle components. The control module 14 can be configured to convert the error flag of the communication based on the second data format of the second plurality of vehicle components into the first data format and provide it to the first plurality of vehicle components.

[0049] The control module 14 may be configured to provide a communication interface based on the configuration information. For example, the configuration information may include at least one element in the group consisting of: information about the (mutual) correspondence between information in the first information and information in the second information, information about conversion rules for converting between at least one first data format and at least one second data format, information about rules for decomposing at least one redundancy, and information about rules for determining transmission errors. The control module 14 may be configured to obtain updated configuration information for refreshing the configuration information. After refreshing the configuration information, the control module 14 may be configured to provide a communication interface based on the updated configuration information.

[0050] In an embodiment, the control module 14 (and / or as combined Figure 2a The control module 24 described herein may correspond to any controller or processor or programmable hardware component. For example, the control module 14; 24 may also be implemented as software programmed for the corresponding hardware component. In this regard, the control module 14; 24 may be implemented as programmable hardware with correspondingly adapted software. In this context, any processor, such as a digital signal processor (DSP), may be used. In this context, the embodiments are not limited to a specific type of processor. Any processor or multiple processors for implementing the control module 14; 24 are conceivable.

[0051] At least one interface 12 (and / or as combined Figure 2aThe at least one interface 22 described may correspond, for example, to one or more inputs and / or one or more outputs for receiving and / or transmitting information based on a code, for example as a digital bit value, within a module, between modules or between modules of different entities. The at least one interface 12; 22 may be configured for communication via a network inside the vehicle. Communication between the first plurality of vehicle components, the data exchange device and / or the second plurality of vehicle components may occur inside the vehicle.

[0052] In at least some embodiments, vehicle 100 may correspond to, for example, a land vehicle, a water vehicle, an air vehicle, a rail vehicle, a road vehicle, an automobile, an off-road vehicle, a motor vehicle, or a truck.

[0053] The storage module may, for example, include at least one element selected from the group consisting of: a computer-readable storage medium, a magnetic storage medium, an optical storage medium, a hard disk, a flash memory, a disk, a random access memory (also known as Random Access Memory in English), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electronically erasable programmable read-only memory (EEPROM) and a network storage.

[0054] Before or after binding (e.g. Figures 2a to 6 ) The examples or schemes described in the foregoing list further details and aspects of the data exchange device 10 and / or the data exchange method. The data exchange device 10 and / or the data exchange method may include one or more additional optional features corresponding to one or more aspects of the examples or proposed schemes as described before or after.

[0055] Figure 2a A block diagram of an exemplary embodiment of a device 20 for a vehicle component 200 of a vehicle 100 is shown. Figure 2a Furthermore, a vehicle component 200 with a device 20 and a vehicle 100 are shown, which comprises: a vehicle component 200 with a device 20, a data exchange device 10 and a first plurality of vehicle components. The device 20 comprises an interface 22, which is designed for communication with the data exchange device 10 of the vehicle 100. The data exchange device 10 can correspond, for example, to Figure 1aThe vehicle component can be, for example, one of the second plurality of vehicle components. The device 20 further comprises a control module 24, which is configured to use the data exchange device 10 in order to access first information of the first plurality of vehicle components via the data exchange device 10 in the form of second information based on a second data format, wherein the first information is based on the first data format. The at least one interface 22 is coupled to the control module 24.

[0056] Figure 2a A flow chart of an embodiment of a corresponding method for a vehicle component of a vehicle is shown. The method steps can be performed, for example, by the vehicle component, for example, by a control module of the vehicle component. The method comprises: communicating 210 with a data exchange device 10 of the vehicle 100. The method further comprises: using 220 the data exchange device 10 in order to access first information of a first plurality of vehicle components in the form of second information based on a second data format via the data exchange device 10, wherein the first information is based on a first data format. The method can be performed, for example, by the vehicle component, for example, by a control module of the vehicle component.

[0057] The following description relates both to the device and to the method. In this case, the functional capabilities of the control module and at least one interface correspond to these method steps of the method.

[0058] The control module 24 is configured to use the data exchange device 10 to access the first information of the first plurality of vehicle components in the form of second information via the data exchange device 10. For example, the control module 24 can be configured to call the second information from the data exchange device 10 or receive the second information from the data exchange device 10. The control module 24 can be configured to extract the first information from the second information or derive the first information from the second information. For example, the second information can include the content of the first information and / or provide the functionality of the first information. The control module can be configured to access the content and / or functionality of the first information via the second information.

[0059] Before or after binding (e.g. Figures 1a to 2a , 3a to 6) The examples or schemes described in the examples or schemes list more details and aspects of the device 20 and / or the method. The device 20 and / or the method may include one or more additional optional features, which correspond to one or more aspects of the examples or proposed schemes as described before or after.

[0060] At least some embodiments create a communication server. The communication server and the communication server proposed below may correspond to or include, for example, a combination of Figures 1a to 2bThe data exchange device 10 is presented. Embodiments of the communication server provide in a distributed automotive E / E architecture (end-to-end architecture in the field of transportation): a transformation from signal-based communication to service-oriented communication.

[0061] In some systems, a gateway in the vehicle provides the data of the vehicle networking to a plurality of functions via a static interface. This has the disadvantage that the data is statically specified and no abstraction from the vehicle networking at the functional level occurs. This can be disadvantageous for the update / upgrade capability (update / equipment capability) and portability of the functions.

[0062] Therefore, an embodiment provides an on-board application server (ICAS, in-vehicle application server) having a communication server, which pre-processes static CAN signals as services, via which functions (applications) can be dynamically accessed; and the communication server can use different functions via service discovery (service identification in the network).

[0063] Here, the embodiments follow a general approach that is independent of the application situation. A communication server that can, for example, correspond to a data exchange device can provide service communications (business communications) from multiple signal sources (physical bus / network and communication protocol), and vice versa. At least some embodiments of the communication server use multi-protocol service-oriented communication. The communication server can be constructed to classify / convert binary data ("untyped") (e.g., a first data format) into a complete data structure (type-based, e.g., a second data format). The communication server can be constructed to monitor the communication of both parties. The communication server can be constructed to convert time-controlled communication into event-controlled communication and vice versa. The communication server can be constructed to ensure secure communication according to ISO26262 (a standard of the International Organization for Standardization ISO).

[0064] A communication server (ComServ, short for Communication Server, in English) can be designed to exchange signal communication, such as is used at the sensor / actuator level, and service-oriented communication, such as is used at the MEB (Modular Electrified Block) computing level.

[0065] ComServ can provide services (as a server / service computer) via which information can be called up or ordered from signal communications (eg communications based on the second data format) and / or information can be sent to users via signal communications.

[0066] ComServ can use other services (businesses) as a client (as a calling computer) to call up data and send the data as a signal and / or transfer data from a signal to a service (server).

[0067] Figure 3a A schematic diagram of in-vehicle communications is shown with service-oriented communications between vehicle applications 302 (eg, second plurality of vehicle components) and signal communications between vehicle sensors / actuators 304 (eg, first plurality of vehicle components). A communications server 306 provides a communications interface between signal communications and service-oriented communications.

[0068] Figure 3b The functional architecture of an exemplary communication server is shown. The communication server may, for example, include a server module 310 and a signaling technology plug-in (additional component) 320. For example, the server module 310 can be used for different signaling technologies. The server module provides protocol-related service features (e.g., via SomeIP or ViWi protocols). The server module also optionally provides a transformation of redundant data (as a general artifact) and / or an E2E converter (end-to-end converter to provide end-to-end secure communication).

[0069] For this purpose, the server module comprises a service communication interface 312, which communicates via service-oriented communication (e.g., a second data format) and can optionally include a service interface for end-to-end secure communication. In a first level 314, data can be sorted between a database 316 and the communication interface 312. In the database 316, in level 3, redundancy can also be optionally resolved.

[0070] The signal technology plug-in 320 includes a signal communication interface 324, which communicates via signal communication (PDU, Payload Data Unit, useful data unit) and can optionally include a PDU interface for end-to-end secure communication. The signal technology plug-in 320 also includes a level 1 filter 324 for filtering the signal communication and optionally includes a level 2 transformation 322 for converting the signal communication into a data format for service communication. The signal technology plug-in can, for example, provide communication monitoring, mapping (dispatching) of signals to service elements (general artifacts, similar to a "routing matrix") and / or an E2E transformer (end-to-end transformer for providing end-to-end secure communication).

[0071] At least some embodiments of the communication server support the protocols SOME / IP and ViWi. The communication server can comply with the following requirements: as a maximum data age of 2 ms from a signal change to a service (and vice versa) and as a maximum startup time, support service provision after a maximum of 200 ms. The communication server can hold up to 1 MB of data. At least some embodiments support the safety settings of the system OBD (On-Board-Diagnose, diagnostics in vehicles) and ASIL D (AutomotiveSafetyIntegrityLevelD, vehicle safety integrity level D). At least some embodiments of the communication server also support updatability. For example, updates cannot affect other applications on ICAS1.

[0072] The communication server provides data conversion between the sensor / actuator level and the computing level. Figure 3c Such a transformation is illustrated. The signal communication arrives at the communication server 330 via the signal communication interface 332. The communication server is configured to provide a syntactic transformation 334 between the signal communication and the service-oriented communication. The syntactic transformation includes level 1 (filtering / classification) and optionally level 2 (data type transformation) and level 3 (resolving redundancy). Service-oriented communication is then provided within the scope of multiple services of multiple service enhancers (Serviceaufwerter) (e.g., a second plurality of vehicle components) 350 via the service communication interface 336, which optionally perform a semantic transformation 340 representing level 4. In addition, the communication server optionally provides an end-to-end guarantee 338 between the signal communication interface 332 and the service communication interface 336. In combination Figure 1a The at least one interface 12 introduced may include, for example, a signal communication interface 332 and a service communication interface 336 .

[0073] Figure 4 A system overview of an exemplary communication server 400 is shown. The communication server includes a signal to service converter 410 that provides dispatching between signal communications and service communications and optionally provides conversion between signal communications and service communications. Service 1 420, service 2 430, and service 4 440 access the communication server by means of service communications, for example based on a pull mode by invoking data (service 2, service 1 on function 1 422) or based on a push mode by receiving data provided by the communication server 400 (service 4).

[0074] For example, a communication server maps a Sender / Receiver interface from the signal world to a service interface, eg, provides a service interface (server) for receiving information from the signal world and / or eg acts as a server / client for sending information into the signal world.

[0075] The communication server includes a signal 2 service converter (eg, data switching device 10).

[0076] Figure 5a An example for a service data model is shown (the service data model is based on the second data format, for example). A service 512 includes a plurality of resources 514 that can be represented as objects. In the present case, the service has "vw.service.carbody" ("vw" and "service" are used as manufacturer- and protocol-specific prefixes, and "carbody" is the service identifier), and the resources 514 "sidewindows", "roof", "backdoor", "backwindow", "windshield" and "sidedoor" are resources of the service. The resource "sidedoors" is defined by the object "sidedoor" 516, which is described by the properties "position", "isOpened", "isLocked", "isSecured", ..., "isTAGActive" and "IsTIGActive". The "sidedoor" object is used by the resource "sidedoors" in four instances 518 for the "sidedoor" object with positions "driver," "codriver," "driver rear," and "codriver read" to provide access to the "sidedoor" resource.

[0077] exist Figure 5b In FIG. 5 , it is shown that the communication server 520 is used to communicate with the Figure 5aThe communication server is designed to assign the signal data for the signal sources TSG_FT_01 (driver's door), TSG_BT_01 (front passenger door), TSG_HFS_01 (door behind the driver) and TSG_HBFS_01 (door behind the front passenger) with corresponding information with the suffixes _Tuer_geoeffnet, _verriegelt, _gesafet, _TAG_betaetigt, _TIG_betaetigt to the corresponding service data of the service data model.

[0078] The different signal types are described below. The following signal types are distinguished:

[0079] - Type 0 ("1-bit"): the signal has a length of 1 bit - The initialization value ("init-value") is one of two possible values ​​(usually 0)

[0080] - Type 1 ("Pure Logic"): The signal has only logic value + initialization value

[0081] - Type 2 ("Logic with Error"): The signal has only logic value + initialization value + error value

[0082] - Type 3 ("Purely Physical"): the signal has only physical value + initial value

[0083] - Type 4 ("Physical with Error") signals have only physical value + initialization value + error value

[0084] - Type 5 ("logical and physical") signals have physical and logical values ​​+ initialization value + error value

[0085] - Type 6 ("Constant Signal"): The signal has a logical value. In vehicles, the signal has a constant logical value. A subset of type 1

[0086] In at least some embodiments (of conversion between at least one first data format and at least one second data format), these signal types are translated into a service data model as follows. In the following, reference numerals indicate:

[0087] - 530 Service (business) identification code

[0088] - 532 Service version number

[0089] - 534 Identifier of the service

[0090] - 536 Service resource identification code

[0091] - 538 Identifier of the resource

[0092] - 540 Resource characteristics (attributes)

[0093] - 542 Data type of the attribute

[0094] - 544 Property Value

[0095] In the case of type 0 ("1 bit"), the signal is mapped onto an attribute (property) of the "Boolean" type. FIG. 5 c shows an example in which the service ExteriorLight has the resource "lightFunctions" with the following properties: "id" (identifier) ​​of the data type "uuid" (Universally Unique Identifier); "functionIdentifier" of the data type "enum" and the value "1 - ParkingLights" (parking lights); and "isActivated" of the data type "Boolean" and the value (object) "LV_Standlicht_Anzeige" (is activated).

[0096] In the type 1a ("pure logic") case, the signal has only a logical value and an (implicit) initialization value. This represents the mapping of the signal onto a characteristic of type "integer", such as Figure 5d . There, the "EmergencyAssist" service has the resource "notifications" with the following properties: "id" (identifier) ​​of the data type "uuid", "type" of the data type "enum" and the value "1 - EmergencyAssistNotification" and "value" of the data type "integer" with the value "EA_Texte" (Emergency Assistance Text). The received signal value is provided in the "attribute value". Even in the event of a source failure, a constant signal (without an initialized value) can still be operated with the last value.

[0097] In the case of type 1b ("pure logic"), the signal has only a logical value and an (implicit) initialization value. This represents a mapping of the signal to an attribute of type "integer". The "valueType" property of type "enum" indicates whether an initialization value is present. Figure 5eThe example of a service "EmergencyAssist" with a resource "notifications" is shown, which has the following properties: "id" (identifier) ​​of the data type "uuid", "type" of the data type "enum" and the value "1 -EmergencyAssistNotification", "value" of the data type "integer" with the value "EA_Texte" and "valueType" of the data type "enum [0 = init, 1 = error, 2 = logicalValue, 3 = physicalValue]" with the value "EA_Texte". The received signal value is provided in the attribute value. When an "initialization" value is received, this is provided in "value" and "valueType" is set to "0".

[0098] In the case of type 2 ("Logic with error"), the signal has only logical values, initialization values ​​and error values. In this case, the signal is mapped to an attribute of the "integer" type. The "valueType" property of the "enum" type indicates whether an initialization value, an error value or a valid value is present. Figure 5f An example is shown for the service "EmergencyAssist" with the resource "notifications" having the following properties: "id" (identifier) ​​of the data type "uuid", "type" of the data type "enum" and the value "1 - EmergencyAssistNotification", "value" of the data type "integer" with the value "EA_Texte" and "valueType" of the data type "enum [0 = init, 1 = error, 2 = logicalValue, 3 = physicalValue]" with the value "EA_Texte". The received signal value is provided as the property "value". When an initialization value or an error value is received, it is provided in "value" and "valueType" is set to "0" or "1". When a valid value is received, "valueType" is set to "2 = logicalValue".

[0099] In the case of type 3 ("purely physical"), the signal has only a physical value and an initialization value, in the case of type 4 an additional error value. This represents the mapping of the signal to an attribute of the type "integer" or "double". The "valueType" property of the "enum" type indicates whether an initialization value or a valid value is present. Figure 5g An example is shown for the service "Odometrie V2" with the resource "velocities" having the following properties: "id" (identifier) ​​of the data type "uuid", "type" of the data type "enum" and the value "1-VelocityNCAP" (Velocity New Car Assessment Program), "value" of the data type "double" with the value "EML_AnanzeGeschw", and "valueType" of the data type "enum [0 = init, 1 = error, 2 = logicalValue, 3 = physicalValue]" with the value "EML_AnweiseGeschw". The received signal value is provided in the property "value". When an initialization value or an error value is received, this is provided in "value" and "valueType" is set to "0" or "1". When a valid value is received, "valueType" is set to "3 = physicalValue".

[0100] In the case of type 5 ("logical and physical"), the signal has physical and logical values, initialization values ​​and error values. In this case, the signal is mapped to a property of the type "integer" or "double" for physical values ​​and to a property of the type "integer" for logical values. The "valueType" property of the "enum" type indicates whether an initialization value, an error value, a physical value or a logical value is present. Figure 5hAn example is shown for a service "Odometrie V2" with a resource "velocities" having the following properties: "id" of the data type "uuid", "type" of the data type "enum" and the value "1 - VelocityNCAP", "physicalValue" of the data type "double" with the value "EML_AnzeigeGeschw", "logicalValue" of the data type "integer" and the value "EML_AnzeigeGeschw" and "valueType" of the data type "enum [0 = init, 1 = error, 2 = logicalValue, 3 = physicalValue]" with the value "EML_AnzeigeGeschw". The received signal value is provided in the attribute "physicalValue" (transformed original value) and in the attribute "logicalValue" (original value). "ValueType" is set corresponding to the received value.

[0101] In at least some embodiments, the communication server (eg, data exchange device) is a service-to-signal converter, whereby, for example, information can be sent from the service world to the signal world by a user (eg, the second plurality of vehicle components).

[0102] Figure 6 A schematic diagram of such communication is shown. The communication server 600 provides services to the signal converter (e.g., communication interface). This enables the data flow 640 to be converted from the service world to the signal world. The communication server 600 can be used as both a server 650 and a client 660 in the communication with the service 610; 620 or function 630. The communication server is thus, for example, a client of service 1 610 and a server for service 2 620 and function 1 630.

[0103] The following two implementation variants can be provided by the communication server (eg via a communication interface):

[0104] - Variant 1 ("Communication Server Collection"): The Communication Server is the client and the Service is the server

[0105] - Variant 2 ("Cyclic Set"): The communication server is the server and the service is the client

[0106] In variant 1, if Figure 6As shown in , Service 1 610 is the server and Communication Server 600 is the client. The Communication Server "subscribes" to changes in the corresponding service / resource / attribute (which contains the signal value to be written) at Service 1. As long as Service 1 is available, the Communication Server writes the currently existing value to the Signal World.

[0107] In variant 2, as also in Figure 6 As shown in , Service 2 620 is the client and Communication Server 600 is the server. Service 2 calls the "Set" method from the Communication Server to write the signal value to the Signal World. As long as the "Set" function is called again within the time interval Ttimeout, ComServ writes the currently existing value to the Signal World.

[0108] Before combining (e.g. Figures 1a to 2b ) The examples or schemes described in the foregoing list further details and aspects of the communication server. The communication server may include one or more additional optional features corresponding to one or more aspects of the examples or proposed schemes as described before or after.

[0109] Another embodiment is a computer program for performing at least one of the above methods when the computer program is run on a computer, a processor or a programmable hardware component. Another embodiment is also a digital storage medium, which is machine or computer readable and has electronically readable control signals, which can cooperate with the programmable hardware component to perform one of the above methods.

[0110] The features disclosed in the above description, the subsequent claims and the drawings may be essential and realized both individually and in any combination for the realization of the exemplary embodiments in their different embodiments.

[0111] Although some aspects have been described in conjunction with an apparatus, it goes without saying that these aspects are also descriptions of corresponding methods, so that blocks or devices of an apparatus should also be understood as corresponding method steps or features of method steps. Similarly, aspects that have been described in conjunction with method steps or as method steps are also descriptions of corresponding blocks or details or features of corresponding apparatus.

[0112] Depending on the specific implementation requirements, embodiments of the present invention may be implemented in hardware or in software. The implementation may be performed using a digital storage medium, such as a floppy disk, DVD, Blu-ray disc, CD, ROM, PROM, EPROM, EEPROM or flash memory, hard disk or other magnetic or optical storage, on which electronically readable control signals are stored, wherein the electronically readable control signals may cooperate with or cooperate with programmable hardware components to cause the corresponding method to be performed.

[0113] A programmable hardware component can be formed by a processor, a computer processor (CPU = Central Processing Unit), a graphics processor (GPU = Graphics Processing Unit), a computer, a computer system, an application-specific integrated circuit (ASIC = Application-Specific Integrated Circuit), an integrated circuit (IC = Integrated Circuit), a system on a chip (SOC = System on Chip), a programmable logic element or a field programmable gate array (FPGA = Field Programmable Gate Array) with a microprocessor.

[0114] Thus, the digital storage medium may be machine or computer readable. Thus, some embodiments comprise a data carrier having electronically readable control signals capable of cooperating with a programmable computer system or a programmable hardware component such that one of the methods described herein is performed. Thus, one embodiment is a data carrier (or a digital storage medium or a computer readable medium) having recorded thereon a program for performing one of the methods described herein.

[0115] In general, embodiments of the present invention can be implemented as a program, firmware, computer program or computer program product with a program code or as data, wherein when the program is run on a processor or a programmable hardware component, the program code or the data is effective for performing one of the methods. The program code or the data can also be stored on a machine-readable carrier or a data carrier, for example. The program code or the data can exist in particular as source code, machine code or byte code and as other intermediate codes.

[0116] Another embodiment is also a data stream, a signal sequence or a sequence of signals representing a program for executing one of the methods described herein. The data stream, signal sequence or sequence of signals can be configured, for example, so as to be transmitted via a data communication connection, for example via the Internet or another network. An embodiment is therefore also a signal sequence representing data suitable for delivery via a network or a data communication connection, wherein the data represents a program.

[0117] The program according to the embodiment can be implemented during its execution, for example, by implementing one of the methods in the following way, that is, the program reads a storage location or writes one or more data to the storage location, thereby causing switching processes or other processes in transistor structures, amplifier structures or other components that work electrically, optically, magnetically or according to other functional principles. Accordingly, by reading the storage location, data, values, sensor values ​​or other information can be detected, determined or measured by the program. Thus, the program can detect, determine or measure parameters, values, measurement parameters and other information by reading one or more storage locations, and can cause, prompt or perform actions and manipulate other devices, machines and components by writing one or more storage locations.

[0118] The above embodiments are merely illustrative of the principles of the present invention. It goes without saying that modifications and variations of the devices and details described herein will be apparent to other skilled persons. Therefore, it is intended that the present invention shall be limited only by the scope of protection of the following patent claims and not by the specific details presented herein according to the description and illustration of the embodiments.

[0119] Reference numerals list

[0120] 10 Data exchange equipment

[0121] 12 Interface

[0122] 14 Control Module

[0123] 20 Equipment

[0124] 22 Interface

[0125] 24 Control Module

[0126] 30 First plurality of vehicle components

[0127] 40 Second plurality of vehicle parts

[0128] 100 Transportation

[0129] 110 Communicate with a first plurality of vehicle components

[0130] 120 Communicate with a second plurality of vehicle components

[0131] 130 Provide communication interface

[0132] 210 Communicate with data exchange equipment

[0133] 220 Using Data Exchange Devices

[0134] 302 Transportation Applications

[0135] 304 Transportation Sensors / Actuators

[0136] 306 Communication Server

[0137] 310 Server Module

[0138] 312 Service Communication Interface

[0139] 314 First level: classification

[0140] 316 Database

[0141] 320 Signal Technology Plug-in

[0142] 322 Level 2: Transformation

[0143] 324 Level 1: Filter

[0144] 326 Signal communication interface

[0145] 330 Communication Server

[0146] 332 signal communication interface

[0147] 334 Syntactic transformation

[0148] 336 Service Communication Interface

[0149] 338 End-to-end security

[0150] 340 Semantic Transformation

[0151] 350 Service Enhancer

[0152] 400 Communication Server

[0153] 410 Signal to Service Converter

[0154] 420 Service 1

[0155] 422 Function 1

[0156] 430 Services 2

[0157] 440 Services 4

[0158] 512 Services

[0159] 514 Resources

[0160] 516 Object Description

[0161] 518 Object instances

[0162] 520 Communication Server

[0163] 522 Signal Data Model

[0164] 530 Service (business) identification code

[0165] 532 Service version number

[0166] 534 Identifier of the service

[0167] 536 The identifier of the resource served

[0168] 538 Resource identifier

[0169] 540 Resource Characteristics

[0170] 542 Data type of the attribute

[0171] 544 The value of the property

[0172] 600 Communication Server

[0173] 610 Service 1

[0174] 620 Services 2

[0175] 630 Function 1

[0176] 640 Data Stream

[0177] 650 Servers

[0178] 660 Client.

Claims

1. A data exchange device (10) for a vehicle (100), the data exchange device (10) comprising: at least one interface (12) configured to communicate with a first plurality of vehicle components (30) of the vehicle (100) and to communicate with a second plurality of vehicle components (40) of the vehicle (100), wherein the second plurality of vehicle components (40) use a communication protocol for service-oriented communication and the first plurality of vehicle components (30) use a communication protocol for signal communication; and a control module (14) configured to communicate with the first plurality of vehicle components (30) of the vehicle based on at least one first data format and to communicate with the second plurality of vehicle components (40) of the vehicle based on at least one second data format, wherein the control module (14) is configured to provide a communication interface for communication between the first plurality of vehicle components (30) and the second plurality of vehicle components (40), wherein the control module (14) is configured to provide access to first information of the first plurality of vehicle components (30) by providing second information for the second plurality of vehicle components (40), wherein the first information is based on the at least one first data format, and wherein the second information is based on the at least one second data format, wherein the control module (14) is configured to provide the second information to the second plurality of vehicle components (40) via an object-oriented programming interface, and wherein the second data format is an object-oriented data format, The data exchange device (10) is configured to provide the following functions: Filtering / sorting; Data type conversion; Break down redundancy.

2. A data exchange device (10) according to claim 1, wherein the control module (14) is constructed to provide conversion between the at least one first data format and the at least one second data format for communication between the first plurality of vehicle components (30) and the second plurality of vehicle components (40).

3. A data exchange device (10) according to claim 1 or 2, wherein the control module (14) is constructed to provide end-to-end secure communication between a first vehicle component in the first plurality of vehicle components (30) and a second vehicle component in the second plurality of vehicle components (40).

4. The data exchange device (10) according to claim 3, wherein the control module (14) is configured to ensure the end-to-end secure communication by determining at least one transmission error and / or forwarding information about the at least one transmission error.

5. The data exchange device (10) according to claim 1 or 2, wherein the control module (14) is configured to convert error flags of the communication of the first plurality of vehicle components (30) based on the first data format into the second data format and provide the error flags to the second plurality of vehicle components (40), And / or wherein the control module (14) is configured to convert error flags of the communication of the second plurality of vehicle components (40) based on the second data format into the first data format and provide the error flags to the first plurality of vehicle components (30).

6. The data exchange device (10) according to claim 1 or 2, wherein at least one vehicle component is included in the first plurality of vehicle components (30) and is included in the second plurality of vehicle components (40).

7. A data exchange device (10) according to claim 1 or 2, wherein the first plurality of vehicle components (30) correspond to a plurality of control devices for controlling vehicle sensors and / or for controlling vehicle actuators, and / or wherein the second plurality of vehicle components (40) include a plurality of computing units of the vehicle (100).

8. The data exchange device (10) according to claim 1 or 2, wherein the control module (14) is constructed to provide a communication interface based on configuration information, wherein the control module (14) is further constructed to obtain updated configuration information for refreshing the configuration information.

9. The data exchange device (10) according to claim 1 or 2, wherein the control module (14) is configured to continuously obtain first information of the first plurality of vehicle components (30) from the first plurality of vehicle components (30), to determine the second information based on the first information and to provide the second information to the second plurality of vehicle components (40), And / or wherein the control module (14) is configured to continuously obtain first information of the first plurality of vehicle components (30) from the first plurality of vehicle components (30), wherein the control module (14) is configured to determine a timeout for obtaining the first information of the first plurality of vehicle components (30).

10. A device (20) for a vehicle component of a vehicle, the device comprising: an interface (22) configured to communicate with a data exchange device (10) of the vehicle (100); and a control module (24) configured to use the data exchange device (10) to access first information of a first plurality of vehicle components (30) via the data exchange device (10) in the form of second information based on a second data format, wherein the first information is based on a first data format, wherein the second information uses a communication protocol used for service-oriented communication and the first information uses a communication protocol used for signal communication, And wherein the second data format is an object-oriented data format, wherein the data exchange device (10) provides the following functions: Filtering / sorting; Data type conversion; Break down redundancy.

11. A data exchange method for a vehicle (100), the data exchange method comprising: communicating with a first plurality of vehicle components of the vehicle based on at least one first data format (110); communicating with a second plurality of vehicle components of the vehicle based on at least one second data format (120); providing (130) a communication interface for communicating between the first plurality of vehicle components and the second plurality of vehicle components, wherein providing (130) the communication interface includes providing access to first information of the first plurality of vehicle components by providing second information for the second plurality of vehicle components, wherein the first information is based on at least one first data format, and wherein the second information is based on at least one second data format, wherein the second information uses a communication protocol used for service-oriented communication and the first information uses a communication protocol used for signal communication, And wherein the second data format is an object-oriented data format, wherein the data exchange device (10) provides the following functions: Filtering / sorting; Data type conversion; Break down redundancy.

12. A method for a vehicle component of a vehicle, the method comprising: Communicating (210) with a data exchange device (10) of the vehicle (100); and using (220) the data exchange device (10) to access first information of a first plurality of vehicle components via the data exchange device (10) in the form of second information based on a second data format, wherein the first information is based on the first data format, wherein the second information uses a communication protocol used for service-oriented communication and the first information uses a communication protocol used for signal communication, And wherein the second data format is an object-oriented data format, wherein the data exchange device (10) provides the following functions: Filtering / sorting; Data type conversion; Break down redundancy.

13. A program product having a computer program, the computer program comprising a program code, wherein the computer program is configured to perform the method according to any one of claims 11 or 12 when the program code is executed on a computer, a processor, a controller or a programmable hardware component.

Images