Assembly and method for an analysis system

Abstract

An assembly for an analysis system includes: a first entity configured to transmit and receive data; a second entity configured to transmit and receive data; at least one third entity configured to receive data from the first entity and / or data from the second entity; and an interface configured to transmit data of the first entity to the second entity and the third entity and / or to transmit data of the second entity to the first entity and the third entity, where the interface defines a file for a Web Component Interface Type WIT or Web Component Interface Type, and where data from an exit of the third entity is used to analyze the system.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a component for an analysis system and a method. BACKGROUND

[0002] For testing applications or systems in real scenarios in a car environment, e.g. in a vehicle, vehicle manufacturers and responsible suppliers are conducting test drives on real roads to evaluate the performance.

[0003] In these test drives, the application or system under test has to be clearly separated from the rest of the environment. A currently common solution is to add a dedicated hardware to the system, where a specific communication interface is required to transfer data from the environment to the dedicated hardware.

[0004] Therefore, additional hardware is required and a vehicle level concept for distributing input data of the application or system under test has to be developed and deployed. This can lead, for example, to an additional increase of switch hardware and performance. Furthermore, all input data of the application or system under test has to be part of the official vehicle communication.

[0005] Therefore, there is a need for a component for an analysis system and a method without additional hardware components or additional communication interfaces. SUMMARY

[0006] According to the independent claims, the present disclosure provides a component for an analysis system, a method for an analysis system and a vehicle. Embodiments are given in the dependent claims, the description and drawings.

[0007] In one aspect, the present disclosure relates to a component for an analysis system. The component comprises a first entity configured to send and receive data, a second entity configured to send and receive data, at least one third entity configured to receive data from the first entity and / or data from the second entity, and an interface configured to transfer data of the first entity to the second entity and the third entity and / or to transfer data of the second entity to the first entity and the third entity, wherein the interface is defined by a Web Component Interface Type (WIT) or a Web Component Interface Type Definition file, and wherein data from the third entity is used for the analysis system.

[0008] In other words, the interface can be configured to receive data from an outlet of the first entity and transmit the data of the first entity to at least one of an inlet of the second entity or an inlet of the third entity. The interface can be configured to receive data from an outlet of the second entity and transmit the data from the outlet of the second entity to at least one of an inlet of the first entity or an inlet of the third entity. The interface can also be configured to receive data from at least one of an outlet of the first entity or an outlet of the second entity and transmit the received data from the first entity and / or the second entity to the non-blocking queue. The non-blocking queue can be a memory comprising a sufficient storage size such that the transmitted data of the interface can always be stored. This can ensure a data flow of the respective data from the interface.

[0009] The first entity can be hardware or software, in particular, the first entity can be an application. The application can be an application for autonomous driving or an application for an advanced driver assistance system in a vehicle.

[0010] The second entity can also be hardware or software, in particular, the second entity can be a sensor, such as a radar sensor, a lidar sensor, or a video camera. The data transmitted from the second entity to the first and / or third entity can comprise sensor-acquired data. It is to be understood that the second entity can also be an application, in particular, the second entity can be the same application as the first entity. Thus, the interface can split between various parts of one application.

[0011] The at least one third entity can be one of hardware, software, or a non-blocking queue. In particular, the third entity can be a shadow application, wherein the shadow application can be a new application or an updated version of an existing application, such as an updated version of the application of the first entity. The third entity can comprise a measured application in a real-world scenario. The non-blocking queue can be a memory configured to store data.

[0012] The data described herein can be sensor data or internal system data. The data can be sent and received through the interface such that the same data or a copy of the data can be obtained at the first entity, the second entity, and the third entity, in particular, at the same time. Exemplary data can be radar target data, ego motion data (e.g., velocity and rotation rate), GPS position data, map data, or expected car acceleration or steering data.

[0013] A Web Component Interface Type (WIT), also abbreviated as Wasm, can define a portable binary code format and a corresponding text format for the interface to facilitate the interaction between the entities described herein.

[0014] Data exported from the third entity can be used in an analysis system or for testing applications, where the analysis system can include triggering shadow mode applications, performing specialized analysis, logging data, or some other manner. It should be appreciated that the analysis system can also be based on data of the first entity or data of the second entity transmitted to the third entity using the interface. Specifically, if the third entity is a non-blocking queue, the data of the first entity and the data of the second entity can be used in the analysis system or testing applications. Further, the analysis can be based on at least one of the transmitted data of the first entity or the transmitted data of the second entity and the data exported from the third entity.

[0015] The analysis of the system can include data analysis related to errors that can occur during testing of the system. Specifically, the system analysis can include at least one of the following: critical event monitoring, logging patterns, intrusion detection, shadow mode applications, and / or redundancy.

[0016] The components can include a plurality of computer hardware components (e.g., a processor (e.g., a processing unit or a processing network), at least one memory (e.g., a memory unit or a memory network), and at least one non-transitory data storage device). It should be appreciated that the same or additional computer hardware components can be provided and used to perform the steps of the methods disclosed below.

[0017] According to one embodiment, the interface is configured to filter the data of the first entity and / or filter the data of the second entity. The filtering can include selecting certain data from the data of the first entity or from the data of the second entity. The filtered or selected data can depend on the test applied to the system. The data can be filtered prior to transmitting the data to the third entity using the interface. Thus, only data related to the current test can be transmitted to the third entity through the interface.

[0018] According to one embodiment, the interface is configured to transform the data of the first entity and / or transform the data of the second entity. The transformation can include converting, manipulating, changing, deleting, or adjusting the data of the first entity or the data of the second entity. How the data is transformed can depend on the test applied to the system under test or the test applied to the application under test. The data can be transformed prior to transmitting the data to the third entity using the interface.

[0019] According to one embodiment, the interface includes a first channel and a second channel, where the first channel and the second channel are defined by a Web Component Interface Type (WIT) or a Web Component Interface Type Definition file. The WIT language can define the content and direction of the first channel and the second channel.

[0020] According to one embodiment, the first channel is configured to receive data from the first entity and to transmit the data of the first entity to the second entity, wherein the first channel is further configured to transmit the data of the first entity to the third entity. The first channel can be configured to filter the data received from the first entity. Alternatively or additionally, the first channel can be configured to transform the data received from the first entity. Further, the first channel can be configured to transmit the data received from the first entity, or the filtered data of the first entity, or the transformed data of the first entity to the third entity. Thus, the first channel can be used to distribute data from the first entity to the second entity and the third entity.

[0021] According to one embodiment, the second channel is configured to receive data of the second entity and to transmit the data of the second entity to the first entity, wherein the second channel is further configured to transmit the data of the second entity to the third entity. The second channel can be configured to filter the data received from the second entity. Alternatively or additionally, the second channel can be configured to transform the data received from the second entity. Further, the second channel can be configured to transmit the data received from the second entity, or the filtered data of the second entity, or the transformed data of the second entity to the third entity. Thus, the second channel can be used to distribute data from the second entity to the first entity and the third entity.

[0022] According to one embodiment, the interface is configured to operate independent of the operating system of the components. The first entity and the second entity can operate using different operating systems and / or different processors. The operating system can be one of Linux, vxWorks, QNX, freeRTOS, Zephyr, or MICROSAR. The interface can support any language on any operating system.

[0023] According to one embodiment, the first entity and the second entity are configured to communicate only via the interface. Thus, the first entity and the second entity can be completely decoupled. The data transfer between the first entity and the second entity can be performed only via the interface. The first entity and the second entity can only send respective data to the interface, and the interface can transmit the received data to at least one other entity of the component or one other interface.

[0024] The first entity and the second entity can be configured to communicate only via the first channel and / or the second channel. Thus, the first entity and the second entity can be completely decoupled. The data transfer between the first entity and the second entity can be performed only via the first channel and / or the second channel. The first entity and the second entity can only send respective data to the first channel and / or the second channel, and the first channel and / or the second channel can transmit the received data to at least one other entity of the component or one other channel.

[0025] According to one embodiment, the assembly further comprises a further interface, wherein the further interface is defined by a Web Component Interface Type (WIT) or a Web Component Interface Type Definition file, wherein the further interface is configured to receive data from the interface and to transmit data from the interface to a third entity. Thus, data can be transmitted from the first entity and / or the second entity to the third entity via the interface and the further interface. It is to be understood that the further interface can be configured as the interface. In particular, the further interface can comprise at least two channels, wherein each of the at least two channels can be defined by a Web Component Interface Type (WIT) and each of the at least two channels can be configured to send and receive data from other entities or other interfaces of the assembly. It is to be understood that each interface or each channel described herein can be configured to filter and / or transform data.

[0026] According to one embodiment, the assembly further comprises a fourth entity configured to compare data of the first entity, data of the second entity, and / or data of the third entity, wherein the further interface is configured to receive data from the third entity and data from the interface and to transmit the data of the third entity and the data of the interface to the fourth entity. The fourth entity can be a comparator or an analyzer. The fourth entity can be configured to compare data of at least two entities. It is to be understood that the fourth entity can be configured to compare data of the first entity and data of the second entity.

[0027] In another aspect, the present disclosure is directed to a method for analyzing a system. The method comprises receiving data of a first entity through an interface, receiving data of a second entity through the interface, transmitting the data of the first entity and the data of the second entity to a third entity through the interface, and analyzing the system based on data from an outlet of the third entity, wherein the interface is defined by a Web Component Interface Type (WIT) or a Web Component Interface Type Definition file.

[0028] According to one embodiment, the method further comprises filtering the data of the first entity through the interface and / or filtering the data of the second entity through the interface, before transmitting the data of the first entity and the data of the second entity to the third entity.

[0029] According to one embodiment, the method further comprises transforming the data of the first entity through the interface and / or transforming the data of the second entity through the interface, before transmitting the data of the first entity and the data of the second entity to the third entity.

[0030] According to one embodiment, the method further comprises receiving data from the interface through a further interface and transmitting the data from the interface to the third entity through the further interface.

[0031] According to an embodiment, the method further comprises receiving data from a third entity via a further interface and receiving data from the interface, transmitting the data of the third entity and the data of the interface to a fourth entity via the further interface, and comparing the transmitted data of the third entity and the transmitted data of the interface by the fourth entity.

[0032] The methods described herein can be computer-implemented methods. In another aspect, the disclosure relates to a non-transitory computer-readable medium comprising instructions that, when executed by a computer system, cause the computer system to perform some or all of the steps or aspects of the (computer-implemented) methods described herein. The computer-readable medium can be configured as an optical medium, such as a compact disc (CD) or a digital versatile disc (DVD), a magnetic medium, such as a hard disk drive (HDD), a solid-state drive (SSD), a read-only memory (ROM), such as a flash memory, or the like. Further, the computer-readable medium can be configured as a data storage that can be accessed via a data connection, such as an internet connection. The computer-readable medium can be, for example, an online data repository or a cloud storage.

[0033] The disclosure is also directed to a computer program for instructing a computer to perform some or all of the steps or aspects of the computer-implemented methods described herein.

[0034] In another aspect, the disclosure is directed to a vehicle comprising the components described herein. BRIEF DESCRIPTION OF DRAWINGS

[0035] Exemplary embodiments and functionalities of the present disclosure are described herein with reference to the following drawings, which are schematic illustrations:

[0036] Figure 1 is a component for an analysis system according to an embodiment;

[0037] Figure 2 is another component for an analysis system according to an embodiment;

[0038] Figure 3 is another component for an analysis system according to an embodiment;

[0039] Figure 4 is another component for an analysis system according to an embodiment;

[0040] Figure 5 is another component for an analysis system according to an embodiment;

[0041] Figure 6 is another component for an analysis system according to an embodiment; and

[0042] Figure 7is a flowchart of a method for analyzing a system. DETAILED DESCRIPTION

[0043] The present disclosure relates to a web component interface type as a unit for efficient networking, observability, tracing, and security. By using components and methods for analyzing a system as described herein, improvements can be realized for testing applications or systems in vehicles in real-world scenarios.

[0044] Automotive manufacturers can have started to introduce shadow mode testing of applications or systems in real-world scenarios. There, a pre-release version of software can be taken and monitored under real-world conditions to see how the potential software performs on the road. However, this can require the tested application to be explicitly separated from the rest of the environment, including additional communication overhead, or general input / output (I / O) requirements.

[0045] Thus, the current common solution can require the addition of dedicated hardware in the system, such as a protected region blade. The protected region blade can be a hardware in the vehicle. It can be located within a scalable computing platform (SCP) and can also be located next to an advanced driver assistance system (ADAS) blade, which is responsible for all ADAS functions or autonomous driving (AD) functions in the vehicle.

[0046] As the protected region blade can be isolated from any interference of the rest of the system, the highest security standards can be achieved, at the same time, the protected region can be used for development purposes.

[0047] The protected region can provide two main advantages for development: a pre-release version of software can be tested under real-world conditions to see how the pre-release software performs in practice. This process can be referred to as shadow mode. Also, the computing power of the protected region blade can be utilized to perform intelligent data aggregation and collection. This process can be referred to as power mode.

[0048] However, a problem that can arise with the solution using the protected region blade can be the need for additional hardware and the need to develop and deploy a vehicle-level concept for distributing input data of the tested application. This can lead to additional increases in, for example, switch hardware and performance. Furthermore, all input data of the tested application can have to be part of the official vehicle communication.

[0049] The methods and systems described herein can be configured such that the application or system under test has communication input requirements and only consumes compute cycles. The application or system under test can not use any external I / O, such as accessing an external neural network accelerator. However, it should be appreciated that these applications can still benefit from the proposed solution, but still need to be executed on external hardware. The same solution scope can be used, and the external hardware can be limited to support these applications. This can reduce hardware costs.

[0050] With a regular operating system environment, the compute resources of the application under test can be encapsulated and restricted from the regular system. By ensuring that the communication efforts within the normal system do not change, this can allow for a reduction in actual requirements to remain immune to interference.

[0051] Figure 1 A component 100 for an analysis system is shown, according to one embodiment. The component 100 can include a first entity 102, a second entity 104, and an interface 108. The first entity 102 and the second entity 104 can be configured to transmit and receive data 132, data 134, respectively. The interface 108 can be configured to transfer the data 132 of the first entity 102 to the second entity 104. The interface 108 can also be configured to transfer the data 134 of the second entity 104 to the first entity 102. The interface 108 can be a Web Component Interface Type (WIT) or a Web Component Interface Type Definition file. The first entity 102 and the second entity 104 can be configured to only communicate, i.e., transmit and receive data 132, data 134, via the interface 108. These basic features can apply to all components further described in the following Figures 2 to 5 , even if not explicitly shown in the figures.

[0052] The interface 108 can include a first channel 110 and a second channel 112, where the first channel 110 and the second channel 112 can be defined by a Web Component Interface Type (WIT) or a Web Component Interface Type Definition file. The first channel 110 can be configured to receive data 132 from the first entity 102 and transfer the data 132 of the first entity 102 to the second entity 104. The second channel 112 can be configured to receive data 134 from the second entity 104 and transfer the data 134 of the second entity 104 to the first entity 102. Moreover, these basic features can apply to all components further described in the following Figures 2 to 5 , even if not explicitly shown in the figures.

[0053] The assembly 100 can further include a third entity 106. The interface 108 can be configured to transmit the data 132 of the first entity 102 to the third entity 106 or to transmit the data 134 of the second entity 104 to the third entity 106, or both to transmit the data 132 of the first entity 102 and the data 134 of the second entity 104 to the third entity 106. Thus, the interface 108 can be configured to transmit the data 132 of the first entity 102 not only to the second entity 104, but also to the third entity 106. In particular, the first channel 110 of the interface 108 can be configured to transmit the data 132 of the first entity 102 not only to the second entity 104, but also to the third entity 106. The interface 108 can further be configured to transmit the data 134 of the second entity 104 not only to the first entity 102, but also to the third entity 106. In particular, the second channel 112 of the interface 108 can be configured to transmit the data 134 of the second entity 104 not only to the first entity 102, but also to the third entity 106. These features of the interface 108, in particular of the first channel 110 and the second channel 112, can apply to all assemblies further described in the following Figures 2 to 5

[0054] The interface 108 can be used to separate parts of the execution environment from the actual application. It is to be understood that the interface 108 can also be used to separate application assemblies, e.g. within an application. For example, if the first entity 102 and the second entity 104 can comprise the same application, the interface 108 can separate between the applications. Thus, internal data of the application can be transmitted through the interface 108 to the third entity 106.

[0055] The first channel 110 can further be configured to transmit the data 132 of the first entity 102 to the third entity 106. The second channel 112 can further be configured to transmit the data 134 of the second entity 104 to the third entity 106.

[0056] ​The component 100 can further comprise a further interface 118. The further interface 118 can also be a web component interface type WIT or a web component interface type definition file. The further interface 118 can be configured to receive data 132, data 134 from the interface 108 and to transmit data 132, data 134 from the interface 108 to the third entity 106. The further interface 118 can comprise at least one further channel 120, 122, e.g. a third channel 120 and a fourth channel 122. The at least one further channel 120, 122 can be defined by a web component interface type (WIT) or a web component interface type definition file, wherein the at least one further channel 120, 122 can be configured to receive data 132, data 134 from the interface 108 and to transmit the data 132, data 134 received from the interface 108 to the third entity 106.

[0057] The interface 108 can be configured to send data 132, data 134 to the further interface 118. In particular, the interface 108 can be configured to send data 132 from the first entity 102 to the further interface 118 and / or the interface 108 can be configured to send data 134 from the second entity 104 to the further interface 118. The interface 108 can not receive data from the further interface 118. On the other hand, the further interface 118 can not transmit or send data to the interface 108. The communication or data transfer can only be from the interface 108 to the further interface 118. Data from the actual application, e.g. the application of the first entity 108, can only be sent to the application under test, e.g. the application of the third entity 106, and cannot be received from the application under test. Thus, a test environment comprising at least the third entity 106 can be separated from the rest of the system. This allows analyzing the system or testing the application while the system is operating. It is to be understood that the first channel 110 and / or the second channel 112 can be configured to send data 132, data 134 to the further interface 118 or to the third channel 120 and / or the fourth channel 122 of the further interface 118 instead of the interface 108.

[0058] The third entity 106 can be configured to receive data 132 directly from the first entity 102 via the interface 108 or the first channel 110. The third entity 106 can further be configured to receive data 134 directly from the second entity 104 via the interface 108 or the second channel 112. Thus, the further interface 118 can not be required. Data from the third entity 106 can be used for analyzing the system or for testing the application.

[0059] The default mode on the first channel 110, the second channel 112, or the at least one other channel 120, 122 can be a no share concept. This means that any communication via the channel 110, 112, 120, 122 can require an accompanying code that is responsible for copying, moving, or sharing it from one side of the respective channel 110, 112, 120, 122 to the other side. Communication in this sense can mean receiving and sending data from one entity to another.

[0060] The code, in other words, the communication engine, can be responsible for providing data from one part of the application to another part of the application. This can be the default behavior of the first channel 110, the second channel 112, or the at least one other channel 120, 122. In addition, the first channel 110, the second channel 112, or the at least one other channel 120, 122 can also be extended to provide data to a non-blocking queue. Since the application can always provide this communication to the non-blocking queue, no additional communication unit, such as a specific communication interface, is required, regardless of whether a shadow application, for example, a shadow application within the third entity 106, is running.

[0061] Additionally, the interface 108 can be configured to decide which data is to be transmitted. Thus, the interface 108 can be configured to filter the data 132 of the first entity 102 and / or to filter the data 134 of the second entity 104. The interface 108 can then transmit the filtered data of the first entity 102 to the second entity 104 and the third entity 106. Alternatively or additionally, the interface 108 can transmit the filtered data of the second entity 104 to the first entity 102 and the third entity 106. Filtering can mean selecting specific data from the data of the first entity 102 and / or from the data of the second entity 104. For example, a safety switch can be implemented to filter data, for example, the safety switch can be configured to filter reliable data. For example, the safety switch can filter a command to accelerate a vehicle when the vehicle user steps on the brake pedal. Another example of filtering data can be filtering a defective area of sensor data, for example, data of a camera or a radar sensor. Another example of filtering data can be filtering known error patterns or situations in the data.

[0062] The interface 108 can also be configured to transform the data 132 of the first entity 102 and / or to transform the data 134 of the second entity 104. The interface 108 can then transmit the transformed data of the first entity 102 to the second entity 104 and the third entity 106. Alternatively or additionally, the interface 108 can transmit the transformed data of the second entity 104 to the first entity 102 and the third entity 106. Transforming can mean manipulating, changing, deleting, or adjusting the data from the first entity 102 and / or the data from the second entity 104.

[0063] It is to be understood that the interface 108 can be configured to filter and transform the data 132 of the first entity 102 and / or the data 134 of the second entity 104. For example, the interface 108, in particular the first channel 110 or the second channel 112, can filter the data 132 from the outlet of the first entity 102. After filtering the data, the interface 108, in particular the first channel 110 of the interface 108, can transform the filtered data, for example change the filtered data or at least a part of the filtered data. After transforming the filtered data, the interface 108 can transmit the filtered and transformed data of the first entity 102 to the second entity 104 and / or the third entity 106.

[0064] In another example, the interface 108, in particular the first channel 110 or the second channel 112, can be configured to transform the data 134 received from the outlet of the second entity 104 and transmit the transformed data of the second entity 104 to the third entity 106 or the non-blocking queue.

[0065] Furthermore, the interface 108, in particular the first channel 110 or the second channel 112, can be configured to provide data from the outlet of one entity of the component 100 to the inlet of at least one other entity of the component 100 or to the non-blocking queue.

[0066] The interface 108 can collect statistics of data or events defined by data attributes in the first channel 110 and / or the second channel 112 and send the statistics to a fleet management system over a mobile communication channel, for example, determine the number of radar targets that suddenly jump between left and right at the edge of sensitivity. A further example can be to determine the number of sudden braking events that are masked by subsequent processing stages, or to determine the number of unclassified vehicles in a particular area.

[0067] The component 100 can further comprise a fourth entity 114. The fourth entity 114 can be configured to compare the data 132 of the first entity 102, the data 134 of the second entity 104, and / or the data of the third entity 106 with each other. A further interface 118 can be configured to receive the data from the third entity 106 and the data from the interface 108 and transmit the data of the third entity 106 and the data of the interface 108 to the fourth entity 114. Another option is to use machine learning to analyze patterns in the data received at the fourth entity 114, for example intrusion detection or failure prediction.

[0068] Thus, the data transmitted from the interface 108 to the further interface 118 can be used to trigger a shadow pattern application, to perform a dedicated analysis or logging or any other unit.

[0069] Figure 1The arrows shown in the middle can indicate a data flow of the respective data. The data flow can be performed via a bus system in the vehicle or wirelessly, for example, via Bluetooth or WLAN.

[0070] During development, the code (communication engine) can be configured in a default mode, but can be extended when integrated with a dedicated version. The configuration of the interface 108 can be changed via wireless software or configuration update (OTA).

[0071] Figure 2 Another component 100 for an analysis system according to an embodiment is shown. The first entity 102, the second entity 104, the third entity 106 and the interface 108 comprising the first channel 110 and the second channel 112 can be the same as described in Figure 1 The interface 108 can receive data 132 of the first entity 102. In particular, the first channel 110 can receive data 132 of the first entity 102. The interface 108 can also receive data 134 of the second entity 104. In particular, the second channel 112 can receive data 134 of the second entity 104. The interface 108 can transmit the data 132 of the first entity 102 and the data 134 of the second entity 104 to the third entity 106. The interface 108 can be a Web Component Interface Type (WIT) or a Web Component Interface Type Definition file. The third entity 106 can receive the data 132 from the first entity 102 and the data 134 from the second entity 104. The third entity 106 can process the received data 132, 134 and generate output data 136. The output data 136 from the outlet of the third entity 106 can be used for an analysis system or a test application.

[0072] Before the data 132 of the first entity 102 and the data 134 of the second entity 104 are transmitted to the third entity 106, the data 132 of the first entity 102 and the data 134 of the second entity 104 can be filtered by the interface 108, or by the first channel 110 and the second channel 112.

[0073] Alternatively or additionally, before the data 132 of the first entity 102 and the data 134 of the second entity 104 are transmitted to the third entity 106, the data 132 of the first entity 102 and the data 134 of the second entity 104 can be transformed by the interface 108, or by the first channel 110 and the second channel 112.

[0074] Figure 3 Another component 100 for an analysis system according to an embodiment is shown. The first entity 102, the second entity 104, the third entity 106 and the interface 108 comprising the first channel 110 and the second channel 112 can be the same as described in Figure 1 orFigure 2 The same as described in the middle. The component 100 can further comprise a further interface 118 and a fourth entity 114. The further interface 118 can comprise a third channel 120 and a fourth channel 122, similar to the interface 108. The further interface 118, in particular the third channel 120 and / or the fourth channel 122, can be configured to receive data 132, data 134 from the interface 108. The further interface 118, in particular the third channel 120 and / or the fourth channel 122, can be further configured to transmit or send data 132, data 134 from the interface 108 to the third entity 106. The further interface 118, in particular the third channel 120 and / or the fourth channel 122, can be further configured to receive data 136 from the third entity 106 and to send the data 136 received from the third entity 106 to the fourth entity 114 of the component 100. The further interface 118, in particular the third channel 120 and / or the fourth channel 122, can be configured to filter and / or transform the data 132, data 134 received from the interface 108, in particular the data 132, data 134 received from the first channel 110 and / or from the second channel 112.

[0075] The fourth entity 114 can process the received data 136 of the third entity 106 and generate output data 138. The output data 138 from the outlet of the fourth entity 114 can be used for an analysis system or a test application.

[0076] As Figure 3 shown, the interface 108 can receive data 134 of the second entity 104. In particular, the second channel 112 can receive data 134 of the second entity 104. The interface 108 can transmit the data 134 of the second entity 104 to the first entity 102 and to the further interface 118, in particular to the fourth channel 122. The further interface 118, in particular the fourth channel 122, can transmit the data 134 of the second entity 104 to the third entity 106. Thus, the same data 134 or a copy of the data 134 of the second entity 104 can be received from the first entity 102 and the third entity 106. The third entity 106 can process the data 134 received from the second entity 104 and generate output data 136. The output data 136 of the third entity 106 can be received by the further interface 118, in particular by the third channel 120. The further interface 118, in particular the third channel 120, can transmit the data 136 of the third entity 106 to the fourth entity 114.

[0077] Further, the interface 108 can receive data 132 of the first entity 102. In particular, the first channel 110 can receive the data 132 of the first entity 102. The interface 108 can transmit the data 132 of the first entity 102 to the further interface 118. In particular, the first channel 110 can transmit the data 132 of the first entity 102 to the third channel 120. The further interface 118, in particular the third channel 120, can transmit the received data 132 of the first entity 102 to the fourth entity 114.

[0078] The fourth entity 114 can be an analyzer configured to analyze the received data and to generate output data 138 of the analysis result. For example, the fourth entity 114 can compare the received data 136 of the third entity 106 with predefined data or the fourth entity 114 can compare the received data 136 of the third entity 106 with the received data 132 of the first entity 102. The output data 138 from the outlet of the fourth entity 114 can be used for an analysis system or a test application.

[0079] Figure 4 A further component 100 for an analysis system according to an embodiment is shown. The first entity 102, the second entity 104, the third entity 106, the fourth entity 114, the interface 108 comprising the first channel 110 and the second channel 112 and the further interface 118 comprising the third channel 120 and the fourth channel 122 can be the same as described in Figure 3 The interface 108 can receive data 134 of the second entity 104. In particular, the second channel 112 can receive the data 134 of the second entity 104. The interface 108 can further receive data 132 of the first entity 102. In particular, the first channel 110 can receive the data 132 of the first entity 102. The interface 108 can transmit the data 134 of the second entity 104 to the further interface 118, in particular to the fourth channel 122. The interface 108 can transmit the data 132 of the first entity 102 to the further interface 118, in particular to the third channel 120. The further interface 118, in particular the third channel 120, can transmit the received data 132 of the first entity 102 to the fourth entity 114.

[0080] The further interface 118, in particular the fourth channel 122, can transmit the data 134 of the second entity 104 to the third entity 106 and the fourth entity 114. Thus, the same data 134 or a copy of the data 134 of the second entity 104 can be received from the third entity 106 and the fourth entity 114. The third entity 106 can process the received data 134 and generate output data 136. The output data 136 of the third entity 106 can be received by the further interface 118, in particular by the third channel 120. The further interface 118, in particular the third channel 120, can transmit the output data 136 of the third entity 106 to the fourth entity 114.

[0081] The fourth entity 114 can analyze the data 136 received from the third entity 106. For example, the fourth entity 114 can compare the data 136 received from the third entity 106 with the data 134 received from the second entity 104. The fourth entity 114 can also compare the data 132 received from the first entity 102 with the data 134 received from the second entity 104 or compare the data 132 received from the first entity 102 with the data 136 received from the third entity 106. The output data 138 of the fourth entity 114 comprising the results of the analysis of the fourth entity 114 can be used for the analysis system. This can lead to a more complex combination of the recording mode and the shadow mode of the component 100.

[0082] Figure 5 A further component 100 for an analysis system according to an embodiment is shown. Figure 5 The component 100 can describe a live analysis or live monitoring of two entities 102, 104. The analysis can be performed using an artificial intelligence method. The first entity 102 can be, for example, an application for autonomous driving or an application for an advanced driver assistance system in a vehicle. The second entity 104 can be, for example, a sensor that collects data of the vehicle. The fourth entity 114, the interface 108 comprising the first channel 110 and the second channel 112, and the further interface 118 comprising the third channel 120 and the fourth channel 122 can be used for the analysis of the vehicle. Figure 3 or Figure 4The interface 108 can receive data 132 of the first entity 102. In particular, the first channel 110 can receive data 132 of the first entity 102. The interface 108 can also receive data 134 of the second entity 104. In particular, the second channel 112 can receive data 134 of the second entity 104. The interface 108 can transmit the data 132 of the first entity 102 and the data 134 of the second entity 104 to a further interface 118. In particular, the first channel 110 can transmit the data 132 of the first entity 102 to a third channel 120 and the second channel 112 can transmit the data 134 of the second entity 104 to a fourth channel 122. The further interface 118, in particular the third channel 120 and the fourth channel 122, can transmit the received data 132 of the first entity 102 and the received data 134 of the second entity 104 to a fourth entity 114. The fourth entity 114 can analyze and / or monitor the data 132 received from the first entity 102 and the data 134 received from the second entity 104. Output data 138 of the fourth entity 114 comprising the results of the analysis of the fourth entity 114 can be used for an analysis system. Intrusion detection, fault detection, trigger event recording, etc. can be typical use cases for this embodiment.

[0083] Figure 6 A further component 100 for an analysis system according to an embodiment is shown. The first entity 102 and the third entity 106 can be software, e.g. two completely independent low quality algorithms. Alternatively, the first entity 102 and the third entity 106 can be sensors, e.g. the first entity 102 can be a radar sensor and the third entity 106 can be a video camera. Thus, the data 132 of the first entity 102 can be radar data from a radar sensor and the data 136 of the third entity 106 can be image data from a video camera. The second entity 104 can be hardware, e.g. an interface of a vehicle or an emergency braking system of a vehicle.

[0084] The interface 108 comprising the first channel 110 and the second channel 112 and the further interface 118 comprising the third channel 120 and the fourth channel 122 can be in communication with Figures 3 to 5 The same as described in the above embodiments. However, contrary to the above embodiments, in this embodiment, the interface 108 can also receive data from the further interface 118 and the further interface 118 can also transmit or send data to the interface 108.

[0085] The fourth entity 114 can be software, such as a high-quality algorithm. The fourth entity 114 can process the data 132 received by the first entity 102 and the data 136 received by the third entity 106 and generate output data 138. Specifically, the fourth entity 114 can compare the low-quality data 132 of the first entity 102 with the low-quality data 136 of the third entity 106, or test the redundancy of the low-quality data 132 of the first entity 102 and the low-quality data 136 of the third entity 106. In this context, low-quality data can mean that data 132 and data 136 may be erroneous and therefore have low reliability.

[0086] Output data 138 from the fourth entity 114 can be returned from the fourth entity 114 to the second entity 104 for further processing. Output data 138 can be of high quality, meaning that high-quality output data 138 can be more reliable than the low-quality received data 132 from the first entity 102 and the low-quality received data 136 from the third entity 106. Therefore, output data 138 from the fourth entity 114 can be data with higher confidence than the data 132 from the first entity 102 and the data 136 from the third entity 106.

[0087] like Figure 6 As shown, interface 108 can receive low-quality data 134 from the second entity 104. Specifically, the second channel 112 can receive data 134 from the second entity 104. Interface 108 can transmit the data 134 from the second entity 104 to the first entity 102 and another interface 118, particularly to the fourth channel 122. The other interface 118, particularly the fourth channel 122, can transmit the data 134 from the second entity 104 to the third entity 106. Therefore, the same data 134 or a copy of data 134 from the second entity 104 can be received from the first entity 102 and the third entity 106. The third entity 106 can process the data 134 received from the second entity 104 and generate output data 136. The output data 136 of the third entity 106 can be received by another interface 118 (particularly by the third channel 120). The other interface 118 (particularly the third channel 120) can transmit the data 136 of the third entity 106 to the fourth entity 114.

[0088] Furthermore, interface 108 can receive data 132 from the first entity 102. Specifically, the first channel 110 can receive data 132 from the first entity 102. Interface 108 can transmit the data 132 from the first entity 102 to another interface 118. Specifically, the first channel 110 can transmit the data 132 from the first entity to a third channel 120. The other interface 118, and particularly the third channel 120, can transmit the received data 132 from the first entity 102 to a fourth entity 114.

[0089] The fourth entity 114 can be an analyzer configured to analyze the received data and generate output data 138 of the analysis. For example, the fourth entity 114 can compare the received low quality data 136 of the third entity 106 to the received low quality data 132 of the first entity 102. The fourth entity 114 can test the received low quality data 136 of the third entity 106 for redundancy with the received low quality data 132 of the first entity 102.

[0090] The high quality output data 138 of the fourth entity 114 can be returned to the second entity 104 through the interface 108 and a further interface 118. It is understood that the further interface 118, in particular the third channel 120 and / or the fourth channel 122 of the further interface 118, can be configured to receive the output data 138 of the fourth entity 114 and transmit the output data 138 of the fourth entity 114 to the interface 108. Further, the interface 108, in particular the first channel 110 and / or the second channel 112 of the interface 108, can be configured to receive the output data 138 from the further interface 118, in particular from the third channel 120 and / or the fourth channel 122 of the further interface 118, and transmit the output data 138 of the fourth entity 114 to the second entity 104.

[0091] Figure 7 A flowchart 200 of a method for analyzing a system according to various embodiments is shown. At 202, data of a first entity can be received through an interface. At 204, data of a second entity can be received through the interface. At 206, the data of the first entity and the data of the second entity can be transmitted to a third entity through the interface. At 208, the system can be analyzed based on data from an outlet of the third entity. The interface can be a Web Component Interface Type (WIT), or a Web Component Interface Type definition file.

[0092] By introducing the interface, the original purpose of providing data to a dedicated testing environment can be achieved. In particular, adding additional filtering can improve the security of the testing environment. Further, manipulating the data can allow fuzzing or other testing, and can allow ADAS recording and replaying by using a data logger, for example, in a fourth entity of the component.

[0093] List of reference signs

[0094] 100 component

[0095] 102 first entity

[0096] 104 second entity

[0097] 106 third entity

[0098] 108 interface

[0099] 110 first channel

[0100] 112 second channel

[0101] 114 fourth entity

[0102] 118 interface

[0103] 120 third channel

[0104] 122 fourth channel

[0105] 132 data

[0106] 134 data

[0107] 136 data

[0108] 138 data

[0109] 200 flowchart illustrating a method for analyzing a system according to various embodiments

[0110] 202 a step of receiving data of a first entity

[0111] 204 a step of receiving data of a second entity

[0112] 206 a step of transmitting the data of the first entity and the data of the second entity to a third entity

[0113] 208 a step of analyzing a system

Claims

1. A component for analyzing a system, the component comprising: - a first entity configured to send and receive data, - a second entity configured to send and receive data, - at least one third entity configured to receive data from the first entity and / or data from the second entity, and - an interface configured to transfer data of the first entity to the second entity and the third entity and / or to transfer data of the second entity to the first entity and the third entity, wherein the interface is defined by a Web Component Interface Type, WIT, or a Web Component Interface Type Definition file, and wherein data from an outlet of the third entity is used for analyzing the system.

2. The component according to claim 1, wherein the interface is configured to filter data of the first entity and / or to filter data of the second entity.

3. The component according to claim 1 or 2, wherein the interface is configured to transform data of the first entity and / or to transform data of the second entity.

4. The component according to claim 1 or 2, wherein the interface comprises a first channel and a second channel, the first channel and the second channel are defined by a Web Component Interface Type, WIT, or a Web Component Interface Type Definition file.

5. The component according to claim 4, wherein the first channel is configured to receive data from the first entity and to transfer data of the first entity to the second entity, wherein the first channel is further configured to transfer data of the first entity to the third entity, and / or, wherein the second channel is configured to receive data of the second entity and to transfer data of the second entity to the first entity, wherein the second channel is further configured to transfer data of the second entity to the third entity.

6. The component according to claim 1 or 2, wherein the interface is configured to be operable independent of an operating system of the component.

7. The component according to claim 1 or 2, wherein the first entity and the second entity are configured to communicate only via the interface.

8. The component according to claim 1 or 2, further comprising: - a further interface, wherein the further interface is defined by a Web Component Interface Type, WIT, or a Web Component Interface Type Definition file, wherein the further interface is configured to receive data from the interface and to transfer the data from the interface to the third entity.

9. The component according to claim 8, further comprising: - a fourth entity configured to compare data of the first entity, data of the second entity, and / or data of the third entity, wherein the further interface is configured to receive data from the third entity and data from the interface and to transfer data of the third entity and data of the interface to the fourth entity.

10. A method for analyzing a system, comprising: - receiving data of a first entity by an interface, - receiving data of a second entity by the interface, - transmitting data of the first entity and data of the second entity to a third entity via the interface, and - analyzing the system based on data from an export of the third entity, wherein the interface is defined by a Web Component Interface Type WIT or a Web Component Interface Type Definition file.

11. The method according to claim 10, further comprising: before transmitting data of the first entity and data of the second entity to the third entity, - filtering data of the first entity via the interface, and / or - filtering data of the second entity via the interface.

12. The method according to claim 10 or 11, further comprising: before transmitting data of the first entity and data of the second entity to the third entity, - transforming data of the first entity via the interface, and / or - transforming data of the second entity via the interface.

13. The method according to claim 10 or 11, further comprising: - receiving data from the interface via a further interface, and - transmitting data from the interface to the third entity via the further interface.

14. A vehicle comprising: a component according to at least one of claims 1 to 9.

15. A non-transitory computer readable medium comprising instructions for performing a method according to at least one of claims 10 to 13.

Images