System and method for sensor management in vehicles

Abstract

Simplify the configuration of the vehicle system. [Solution] A system, method, and apparatus for automatically managing sensors in a vehicle system are provided. According to an exemplary embodiment, the system includes a first sensor, a second sensor, a first controller connected to the first and second sensors, and a second controller connected to the first controller. The first controller is configured to perform a first operation using data from the first sensor, and the second controller is configured to perform a second operation using data from the second sensor via the first controller, the second sensor is not connected to the second controller so that the second controller receives data from the second sensor via the first controller.

Description

Technical Field

[0005] ,

[0001] Exemplary embodiments of the present disclosure relate to vehicle systems, and more specifically, to the management of sensors in vehicle systems.

Background Art

[0002] Modern vehicles can perform a wide range of complex functions such as generating telemetry data, transmitting and receiving data via the Internet, and the like. To perform such functions, a vehicle includes various sensors that measure and acquire data regarding the vehicle itself and the vehicle environment, and various controllers that execute functions based on the data output by the sensors.

[0003] In the prior art, each sensor is directly connected to a controller that mainly utilizes the data from that sensor.

[0004] FIG. 1 shows an exemplary sensor-controller configuration of a vehicle system in the prior art. As shown in FIG. 1, a controller related to an advanced driver assistance system (ADAS) (Controller A) is connected to a camera sensor A whose data from the camera sensor is mainly used by the ADAS controller, and a controller related to the cockpit (Controller C) is connected to a camera sensor C whose data from the camera sensor is mainly used by the cockpit controller. Further, to ensure that other controllers can access the data from sensors that are not currently connected to them, a bidirectional connection between the controllers is established to enable the controllers to communicate and exchange the data from their respective sensors. For example, as shown in FIG. 1, the ADAS controller and the cockpit controller are connected bidirectionally to each other.

Summary of the Invention

[0005] <0000〇20>Exemplary embodiments consistent with this disclosure enable simplification of the vehicle system configuration, thereby improving the accuracy, reliability, and efficiency of the tests.

[0006] According to an exemplary embodiment, a system is provided. The system includes a first sensor, a second sensor, a first controller connected to the first and second sensors, and a second controller connected to the first controller. The first controller is configured to perform a first operation using data from the first sensor, and the second controller is configured to perform a second operation using data from the second sensor via the first controller. The second sensor is not connected to the second controller so that the second controller receives data from the second sensor via the first controller.

[0007] According to an exemplary embodiment, the first controller is connected to the first sensor and the second sensor so that data from the first sensor and data from the second sensor are transmitted to the first controller in one direction.

[0008] According to an exemplary embodiment, the second controller is connected to the first controller so that data from the first controller is transmitted to the second controller in one direction, and the data from the first controller includes data from the second sensor.

[0009] According to an exemplary embodiment, the first controller includes a first system-on-a-chip (SoC), and the second controller includes a second SoC separated from the first SoC.

[0010] According to an exemplary embodiment, the first SoC includes a safety-critical SoC, and the second SoC includes a non-safety-critical SoC.

[0011] According to an exemplary embodiment, the first sensor includes a safety-related sensor, and the second sensor includes a non-safety-related sensor.

[0012] According to an exemplary embodiment, all sensors in the vehicle system are connected to a first controller.

[0013] According to an exemplary embodiment, a method is provided. The method includes the steps of: receiving data from a first sensor and data from a second sensor by a first controller connected to a first sensor and a second sensor; performing a first operation using the data from the first sensor by the first controller; receiving data from the first controller by a second controller connected to the first controller, wherein the data from the first controller includes data from the second sensor; and performing a second operation using the data from the second sensor included in the data from the first controller by the second controller.

[0014] According to an exemplary embodiment, the first controller is connected to the first sensor and the second sensor so that data from the first sensor and data from the second sensor are transmitted to the first controller in one direction.

[0015] According to an exemplary embodiment, the second controller is connected to the first controller so that data from the first controller is transmitted to the second controller in one direction.

[0016] According to an exemplary embodiment, the first controller includes a first system-on-a-chip (SoC), and the second controller includes a second SoC separated from the first SoC.

[0017] According to an exemplary embodiment, the first SoC includes a safety-critical SoC, and the second SoC includes a non-safety-critical SoC.

[0018] According to an exemplary embodiment, the first sensor includes a safety-related sensor, and the second sensor includes a non-safety-related sensor.

[0019] According to an exemplary embodiment, all sensors in the vehicle system are connected to a first controller.

[0020] According to an exemplary embodiment, a non-temporary computer-readable recording medium is provided. The non-temporary computer-readable recording medium records instructions that can be executed by at least one processor, the instructions causing at least one processor to perform a method including: receiving data from a first sensor and data from a second sensor by a first controller connected to a first sensor and a second sensor; performing a first operation using the data from the first sensor by the first controller; receiving data from the first controller by a second controller connected to the first controller, wherein the data from the first controller includes data from the second sensor; and performing a second operation using the data from the second sensor included in the data from the first controller by the second controller.

[0021] According to an exemplary embodiment, the first controller is connected to the first sensor and the second sensor so that data from the first sensor and data from the second sensor are transmitted to the first controller in one direction.

[0022] According to an exemplary embodiment, the second controller is connected to the first controller so that data from the first controller is transmitted to the second controller in one direction.

[0023] According to an exemplary embodiment, the first controller includes a first system-on-a-chip (SoC), and the second controller includes a second SoC separated from the first SoC.

[0024] According to an exemplary embodiment, the first SoC includes a safety-critical SoC, and the second SoC includes a non-safety-critical SoC.

[0025] According to an exemplary embodiment, the first sensor includes a safety-related sensor, and the second sensor includes a non-safety-related sensor.

[0026] Additional aspects are partially described in the following description, become partially apparent from the description, or can be realized by practicing the presented embodiments of the disclosure.

Brief Description of the Drawings

[0027] [Figure 1] FIG. 1 shows an exemplary sensor-controller configuration of a vehicle system in the related art. [Figure 2] FIG. 2 shows a block diagram of an exemplary system configuration for managing sensors in a vehicle according to one or more exemplary embodiments. [Figure 3] FIG. 3 shows a flowchart of an exemplary method for managing sensors according to one or more exemplary embodiments. [Figure 4] FIG. 4 shows a block diagram of an exemplary component in a system according to one or more exemplary embodiments.

Modes for Carrying Out the Invention

[0028] The features, advantages, and significance of the exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings. In the accompanying drawings, like reference numerals indicate like elements.

[0029] A detailed description of exemplary embodiments follows with reference to the accompanying drawings. The foregoing disclosure provides examples and descriptions, but is not intended to be exhaustive or to limit embodiments to the exact forms disclosed. Modifications and variations are possible in light of the foregoing disclosure or can be obtained from the implementation of the embodiments. Furthermore, one or more features or components of one embodiment may be incorporated into another embodiment (or one or more features of another embodiment) or combined with another embodiment (or one or more features of another embodiment). In addition, it should be understood that in the flowcharts and descriptions of operations provided below, one or more operations may be omitted, one or more operations may be added, one or more operations may be performed (at least partially) simultaneously, and the order of one or more operations may be changed.

[0030] Even if specific combinations of features are enumerated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible embodiments. In fact, many of these features can be combined in embodiments not specifically enumerated in the claims and / or not specifically disclosed in the specification. Each of the dependent claims described below may directly depend on only one claim, but the disclosure of possible embodiments includes each dependent claim in combination with all other claims in the set of claims.

[0031] Any element, action, or command used herein should not be construed as essential or mandatory unless expressly stated otherwise. Furthermore, when used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” When only one item is intended, the term “one” or similar wording is used. Also, when used herein, terms such as “have,” “possess,” “include,” and “contain” are intended to be open-ended. Furthermore, the phrase “based on” is intended to mean “based at least partially” unless expressly stated otherwise. Additionally, expressions such as "[A] and / or [B]," “at least one of [A] and [B],” or "[A] or [B]" should be understood as including only A, only B, or both A and B.

[0032] Expressions such as "at least one processor" that implement multiple operations or execute multiple instructions should be understood as either a single processor that implements multiple operations, etc., or multiple processors that implement at least some (not necessarily all) of those operations, etc.

[0033] Throughout this specification, references to “one embodiment,” “embodiment,” “non-limiting exemplary embodiment,” or similar language mean that certain features, structures, or characteristics described in relation to the embodiments shown are included in at least one embodiment of the present solution. Therefore, throughout this specification, the phrases “in one embodiment,” “in an embodiment,” “in one non-limiting exemplary embodiment,” and similar language may, but not necessarily, refer to the same embodiment.

[0034] Furthermore, the features, advantages, and characteristics described herein can be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize, in light of the description herein, that the disclosure can be implemented without having one or more of the specific features or advantages of a particular embodiment. In other examples, additional features and advantages that may not be present in all embodiments of the disclosure may be recognized in certain embodiments.

[0035] Furthermore, as used herein, the term “vehicle” refers to any suitable type of vehicle on which exemplary embodiments of the present disclosure may be implemented. For example, “vehicle” refers to a car, truck, bus, motorcycle, or any other suitable type of motor vehicle powered by an engine, motor, or other mechanical means. Alternatively or in addition, “vehicle” as used herein may, without departing from the scope of the present disclosure, refer to a bicycle, skateboard, and any other suitable type of non-electric vehicle.

[0036] As mentioned above with respect to Figure 1, in the vehicle system of the related technology, each sensor is directly connected to a controller that primarily uses the data from that sensor.

[0037] In this regard, since various sensors are connected to various controllers, and these various controllers need to be connected to each other to exchange data, the complexity of the system configuration, including such sensors and controllers, increases as the number of sensors and controllers increases. This increase in complexity makes testing such a system difficult, resulting in reduced reliability and efficiency.

[0038] Therefore, there is a need for a system that can simplify the system design and configuration while ensuring that multiple controllers can utilize data from sensors without increasing the complexity of the design.

[0039] The features, advantages, and significance of the exemplary embodiments described herein are only a part of the disclosure and are not intended to be exhaustive or to limit the scope of the disclosure. Further descriptions of the features, components, configurations, operations, and implementations of the exemplary embodiments of the disclosure are provided below.

[0040] Figure 2 shows a block diagram of an exemplary system configuration 200 for managing sensors in a vehicle, according to one or more exemplary embodiments. As shown in Figure 2, the system configuration 200 includes a plurality of controllers (first controller 210 and second controller 220) and a plurality of sensors (first sensor 212 and second sensor 222). According to the exemplary embodiment, the system configuration 200 is incorporated into a vehicle (vehicle system).

[0041] The first controller 210 includes a processor, a system-on-a-chip (SoC), an electronic control unit, and equivalents thereof. According to an exemplary embodiment, the first controller 210 is configured to perform a first operation using data from a first sensor 212. The first operation includes operations relating to vehicle safety. According to an exemplary embodiment, the first controller 210 is a first SoC, the first SoC includes a safety-critical SoC, where the safety-critical SoC includes an SoC configured to perform operations relating to vehicle safety (i.e., the first operation). For example, the safety-critical SoC includes an SoC configured to perform operations relating to an advanced driver-assistance system (ADAS), a driver monitoring system (DMS), and equivalents thereof.

[0042] The second controller 220 includes a processor, a system-on-a-chip (SoC), an electronic control unit, and equivalents thereof. According to an exemplary embodiment, the second controller 220 is configured to perform a second operation using data from the second sensor 222 via the first controller 210. The second operation includes operations that are not related to vehicle safety. According to an exemplary embodiment, the second controller 220 is a second SoC, and the second SoC includes a non-safety-critical SoC, where a non-safety-critical SoC includes an SoC configured to perform operations that are not related to vehicle safety (any kind of operation) (i.e., the second operation). For example, a non-safety-critical SoC includes an SoC configured to perform operations relating to the cockpit, user experience (UX) / human-machine interface (HMI), and equivalents thereof.

[0043] According to an exemplary embodiment, the second controller 220 and the first controller 210 are separated from each other.

[0044] The first sensor 212 includes sensors whose data is primarily used by the first controller 210. According to an exemplary embodiment, the first sensor 212 includes safety-related sensors, and the data from such safety-related sensors is primarily used by a safety-critical SoC (i.e., the first controller 210). For example, the first sensor 212 includes an in-vehicle camera whose data is used by the DMS·ScO to monitor the vehicle's driver. In another example, the first sensor 212 includes a radar / lider or external camera whose data is used by the ADAS·SoC for data acquisition purposes, image signal processing (ISP), artificial intelligence (AI) processing, and equivalents.

[0045] The second sensor 222 includes sensors whose data is primarily used by the second controller 220. According to an exemplary embodiment, the second sensor 222 includes non-safety-related sensors, and the data from such non-safety-related sensors is primarily used by a non-safety-critical SoC (i.e., the second controller 220). For example, the second sensor 222 includes an in-vehicle camera or microphone whose data is used by the UX / HMI SoC for gesture recognition, display image processing, audio processing, and similar purposes.

[0046] In this regard, as further shown in Figure 2, the first controller 210 is connected to the first sensor 212 and the second sensor 222, and the second controller 220 is connected to the first controller 210.

[0047] In particular, the first controller 210 is connected to the first sensor 212 and the second sensor 222 so that data from the first sensor 212 and data from the second sensor 222 are transmitted to the first controller in one direction.

[0048] In an exemplary embodiment, the first controller 210 is configured to receive data from the first sensor 212 and data from the second sensor 222 to the first controller in one direction. For example, the first controller 210 is configured with an interface that allows data to be transmitted only in the direction from the first sensor 212 and the second sensor 222 to the first controller 210. In another example, the first controller 210 is configured with a protocol that allows data to be transmitted only in the direction from the first sensor 212 and the second sensor 222 to the first controller 210. In yet another example, the first controller 210 is physically configured with components, configurations, designs, and equivalents that allow data to be transmitted only in the direction from the first sensor 212 and the second sensor 222 to the first controller 210. The use of the above expression “only” is one example of limiting the direction in which data is transmitted and is not intended to otherwise limit the scope of the disclosure.

[0049] It is understood that the data from the first sensor 212 and the data from the second sensor 222 include any type of measurement data output by such sensors. For example, if the second sensor 222 corresponds to a temperature sensor, the data from the second sensor 222 includes data relating to temperature measurements acquired and output by the second sensor 222 (temperature sensor).

[0050] The second controller 220 is connected to the first controller 210 so that data from the first controller 210 is transmitted to the second controller 220 in one direction, and the data from the first controller 210 includes data from the second sensor 222 (e.g., sensor data / measured values). In other words, the second controller 220 is connected to the first controller 210 so that data from the second sensor 222 is transmitted to the second controller 220 in one direction via the first controller 210.

[0051] In exemplary embodiments, the second controller 220 is configured to transmit data from the first controller 210 to the second controller 220 in one direction. For example, the second controller 220 is configured with an interface that allows data to be transmitted only in the direction from the first controller 210 to the second controller 220. In another example, the second controller 220 is configured with a protocol that allows data to be transmitted only in the direction from the first controller 210 to the second controller 220. In yet another example, the second controller 220 is physically configured with components, configurations, designs, and equivalents thereto that allow data to be transmitted only in the direction from the first controller 210 to the second controller 220. It should be understood that the use of the expression “only” above is just one example of limiting the direction in which data is transmitted and is not intended to otherwise limit the scope of the disclosure.

[0052] It is understood that the data from the first controller 210 may include any other types of data. For example, the data from the first controller 210 may include data from the first sensor 212, processing data required by the second controller 220, communication data, and equivalents thereof.

[0053] According to an exemplary embodiment, the second sensor 222 is not connected to the second controller 220 so that the second controller 220 receives data from the second sensor 222 via the first controller 210. In other words, the second controller 220 receives data from the second sensor 222 indirectly via the first controller 210, rather than directly from the second sensor 222.

[0054] According to an exemplary embodiment, the second sensor 222 may be connected to the second controller 220 so that the second controller 220 receives data indirectly from the second sensor 222 via the first controller 210 or directly from the second sensor 222.

[0055] Exemplary operations that can be performed by the first controller 210 and the second controller 220 to manage the sensors are described below with reference to Figure 3. Furthermore, several exemplary components included in the first controller 210 and the second controller 220 according to one or more exemplary embodiments are described below with reference to Figure 4.

[0056] Without departing from the scope of this disclosure, the system configuration may include more / fewer components than those shown and / or be configured in a different manner. For example, in some implementations, the system configuration may include more than two controllers and / or more than two sensors.

[0057] In this regard, according to an exemplary embodiment, all sensors in the system (vehicle) are connected to the first controller 210. For example, all sensors in the vehicle are connected to the first controller 210 in a manner similar to that of the second sensor 222, without being connected to a controller that primarily utilizes data from these sensors. Therefore, the first controller 210 is connected, either directly or indirectly via other controllers, in a manner similar to that of the second controller 220, to a controller that primarily utilizes data from such sensors.

[0058] From the above, it can be seen that the data flow from sensors to controllers can be performed unidirectionally throughout the entire vehicle. In this regard, since multiple sensors can be simply connected to one controller (i.e., the first controller 210), and such a controller can then be connected to other controllers, data can be transferred unidirectionally from multiple sensors to other controllers, the system configuration and design can be simplified.

[0059] Furthermore, since a single controller can act as a central point for receiving data from multiple sensors, such data can be easily transferred to any controller to which that single controller is connected without increasing the complexity of the design (e.g., by adding bidirectional communication). For example, the first controller 210 can utilize data from the second sensor 222 without having to incorporate bidirectional communication with the second controller 220 to obtain data from the second sensor 222.

[0060] Furthermore, if the same processing results from a sensor are required for two controllers, such processing is performed only once in one controller and then simply transferred to the other controller. For example, if the same recognition (processing) results from the same sensor data are required for two controllers, such recognition is processed by the AI ​​accelerator in one controller and then simply transferred to the other controller. This eliminates redundant processing operations, thereby reducing overall processing requirements, data transfer size between controllers, and power consumption, and improving efficiency.

[0061] Furthermore, it is understood that the first controller 210 and the second controller 220 are associated with various performance requirements. For example, the first controller 210 has high safety requirements, high real-time processing requirements, and low evolutionary rate requirements, while the second controller 220 has low safety requirements, low real-time processing requirements, and high evolutionary rate requirements. In this regard, data from the first sensor 212 / second sensor 222 can benefit from the requirements of the first controller 210. For example, since the first controller 210 has high real-time processing requirements, data from the second sensor 222 (which is utilized by the second controller 220, which has low real-time processing requirements) can benefit from the high real-time processing requirements of the first controller 210.

[0062] Based on the above, the exemplary embodiment allows for simplification of the vehicle system configuration, thereby improving the accuracy, reliability, and efficiency of the tests.

[0063] Figure 3 shows a flowchart of an exemplary method 300 for managing sensors according to one or more exemplary embodiments. One or more operations in method 300 are performed by at least one processor (processor 412) of the first controller and / or the second controller.

[0064] As shown in Figure 3, in operation 310, at least one processor is configured to receive data from the first sensor and data from the second sensor. The data is received by a first controller connected to the first and second sensors. According to an exemplary embodiment, the first controller is connected to the first and second sensors so that data from the first sensor and data from the second sensor are transmitted to the first controller in one direction.

[0065] According to an exemplary embodiment, the first controller includes a first system-on-a-chip (SoC). The first SoC includes a safety-critical SoC. Furthermore, the first sensor includes a safety-related sensor, and the second sensor includes a non-safety-related sensor.

[0066] According to an exemplary embodiment, all sensors in the vehicle system are connected to a first controller. The method then proceeds to operation S320.

[0067] In operation S320, at least one processor is configured to perform the first operation using data from the first sensor. The data is then used by the first controller. The method then proceeds to operation S330.

[0068] In operation S330, at least one processor is configured to receive data from the first controller. The data is received by a second controller connected to the first controller. According to an exemplary embodiment, the data from the first controller includes data from a second sensor. According to an exemplary embodiment, the second controller is connected to the first controller so that data from the first controller is transmitted to the second controller in one direction.

[0069] According to an exemplary embodiment, the second controller includes a second system-on-a-chip (SoC) separated from the first SoC. The second SoC includes a non-safety-critical SoC.

[0070] It is understood that the first controller is configured to send data, including data from the second sensor, to the second controller before operation S330. The method then proceeds to operation S340.

[0071] In operation S340, at least one processor is configured to perform a second operation using data from a second sensor included in data from a first controller. The data is used by the second controller.

[0072] When operation S340 is performed, method 300 is terminated or terminated. Alternatively, method 300 may return to operation 310 so that at least one processor is configured to repeatedly perform, for at least a predetermined amount of time, receiving data from the first sensor and the second sensor (in operation S310), utilizing data from the first sensor (in operation S320), receiving data from the first controller (in operation S330), and / or utilizing data from the second sensor (in operation S340).

[0073] Figure 4 shows a block diagram of exemplary components in system 410 according to one or more exemplary embodiments. System 410 corresponds to the first and / or second controller described in relation to Figure 2, and therefore the features associated with the first controller, the second controller and system 410 are similarly applicable to each other unless otherwise explicitly stated.

[0074] As shown in Figure 4, the system 410 includes at least one bus 411, at least one processor 412, at least one memory 413, at least one storage component 414, at least one input component 415, at least one output component 416, and at least one communication interface 417.

[0075] System 410 is intended to include more or fewer components than those shown in Figure 4, without departing from the scope of this disclosure. For example, in some embodiments, system 410 may include a plurality of storage components 414, input component 415 and output component 416 may be implemented as transceiver components, memory 413 and storage component 414 may be implemented as memory storage, and so on.

[0076] Bus 411 is configured to facilitate or enable communication between components of System 410. Specifically, Bus 411 connects components in a communicative manner and provides means for data transfer and control signal flow between components. Bus 411 includes one or more of the following suitable types of buses that may be implemented in System 410 to enable real-time (or near real-time) communication and cooperation between components within System 410: an internal bus, an address bus, a data bus, a control bus, a Controller Area Network (CAN) bus, an Ethernet bus, a Peripheral Component Interconnect Express (PCIe) bus, and other appropriate buses.

[0077] The processor 412 is implemented in hardware, firmware, or a combination of hardware and software and is configured to perform real-time (or near real-time) data processing and control of the system 410. The processor 412 includes one or more of the following: a central processing unit (CPU), a graphics processing unit (GPU), a neural processing unit (NPU), a tensor processing unit (TPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and / or other types of processing or computing components that may be implemented in the system 410. In some implementations, the processor 412 is programmable to perform one or more operations described herein. Furthermore, the processor 412 includes multiple processing units, each of which is specialized to perform a particular operation.

[0078] Memory 413 includes one or more media for storing temporary data, runtime variables, program instructions, and buffers necessary for the operation of the control system 410. Memory 413 includes one or more of the following: flash memory, read-only memory (ROM), random access memory (RAM), dynamic or static storage devices (e.g., flash memory, magnetic memory, and / or optical memory), and other suitable types of memory that may be implemented in the system 410 for storing information and / or instructions used by the processor 412.

[0079] The storage component 414 is configured to store non-volatile data such as firmware, configuration settings, calibration data, information, and / or software related to the operation and use of the system 410. For example, the storage component 414 includes hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, and / or solid-state disks), compact discs (CDs), digital multipurpose discs (DVDs), floppy disks, cartridges, magnetic tapes, and / or other types of non-temporary computer-readable media, along with their corresponding drives.

[0080] According to an exemplary embodiment, the storage component 414 is configured to store computer-readable or computer-executable instructions for implementing one or more operations of the system 410. The storage component 414 provides the stored information to the memory 413 for execution by the processor 412.

[0081] The input component 415 includes one or more input components (e.g., a touchscreen display, keyboard, keypad, mouse, buttons, switches, and / or microphone) that enable the system 410 to receive information, for example, via user input. The output component 416 includes one or more output components (e.g., a display, speaker, navigation device, one or more light-emitting diodes (LEDs), etc.) that provide output information from the system 410. According to exemplary embodiments, the input component 415 and / or output component 416 are optional and may be excluded from the system 410.

[0082] At least one communication interface 417 includes a transceiver-like component (e.g., a transceiver and / or separate receivers and transmitters) that enables the system 410 to communicate with other components (e.g., ECUs, user devices, etc.) via, for example, a wired connection, a wireless connection, or a combination of wired and wireless connections. For example, the communication interface 417 includes a Controller Area Network (CAN) bus interface, an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a Universal Serial Bus (USB) interface, a Wi-Fi interface, a cellular network interface, or equivalents thereof.

[0083] According to one or more exemplary embodiments, the communication interface 417 includes at least one input / output (I / O) interface, at least one network interface, at least one storage interface, or equivalents thereof, enabling components 412-416 to communicate with other components. Furthermore, the communication interface 417 may include one or more application programming interfaces (APIs) that enable system 410 (or one or more components included in system 410) to communicate with one or more software applications (e.g., software applications deployed in the ECU).

[0084] Computer executable instructions (e.g., software instructions) are read into memory 413 and / or storage component 414 from another computer-readable medium or another device (e.g., a remote server, external storage, etc.) via, for example, a communication interface 417. When the computer executable instructions stored in memory 413 and / or storage component 414 are executed, they cause the processor 412 to execute one or more processes described herein. In addition or alternatively, hardwired circuits may be used instead of or in combination with software instructions to execute one or more processes described herein. For this reason, the implementations described herein are not limited to any particular combination of hardware circuits and software.

[0085] The features, advantages, and significance of the exemplary embodiments described herein are only a part of the disclosure and are not intended to be exhaustive or to limit the scope of the disclosure. Further descriptions of the features, components, configurations, operations, and implementations of the exemplary embodiments of the disclosure, as well as the related technical advantages and technical significance, are provided below.

[0086] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed herein is an example of an exemplary approach. It is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The claims of the appended methods present elements of various blocks in a sample order and are not intended to limit the user to the specific order or hierarchy presented.

[0087] Some embodiments relate to systems, methods, and / or computer-readable media in integration at any possible level of technical detail. Furthermore, as described herein, one or more of the above-described components may be implemented as instructions stored in a computer-readable medium and executable by at least one processor (and / or include at least one processor). The computer-readable medium includes a non-temporary computer-readable storage medium having computer-readable program instructions thereon for causing a processor (or more processors) to perform an operation.

[0088] A computer-readable storage medium is a tangible device capable of holding and storing instructions used by an instruction execution device. Computer-readable storage mediums include, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. A non-exhaustive list of more specific examples of computer-readable storage mediums includes, namely, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital multipurpose disks (DVDs), memory sticks, floppy disks, mechanically encoded devices such as punch cards or grooved raised structures on which instructions are stored, and any suitable combination thereof. When used herein, a computer-readable storage medium should not be construed as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., an optical pulse passing through an optical fiber cable), or a transient signal itself, such as an electrical signal transmitted through a wire.

[0089] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network such as the Internet, a local area network, a wide area network, and / or a wireless network. The network includes copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer-readable program instructions from the network and transfers the computer-readable program instructions for storage in a computer-readable storage medium within each computing / processing device.

[0090] Computer-readable program code / instructions for performing an operation may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, configuration data for integrated circuits, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++ or equivalents, and procedural programming languages ​​such as the C programming language or similar programming languages. Computer-readable program instructions may be fully executed on the user's computer, partially executed on the user's computer as a standalone software package, partially executed on the user's computer and partially on a remote computer, or fully executed on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or wide area network (WAN), or the connection may be made to an external computer (for example, via the Internet using an Internet service provider). In some embodiments, for example, an electronic circuit including a programmable logic circuit, a field-programmable gate array (FPGA), or a programmable logic array (PLA) executes computer-readable program instructions by personalizing the electronic circuit using state information of computer-readable program instructions in order to perform an action or operation.

[0091] These computer-readable program instructions are provided to a processor of a SoC, general-purpose computer, special-purpose computer, or other programmable data processing device, so that the instructions, executed via the processor of a computer or other programmable data processing device, generate means for implementing functions / actions specified in blocks or blocks of a flowchart and / or block diagram. These computer-readable program instructions may be stored in a computer-readable storage medium that can instruct a computer, programmable data processing device, and / or other device to function in a particular manner so that the storage medium containing the instructions therein comprises a product containing instructions that implements modes of functions / actions specified in blocks or blocks of a flowchart and / or block diagram.

[0092] Computer-readable program instructions may be loaded into a computer, other programmable data processing device, or other device so that instructions executed on a computer, other programmable device, or other apparatus implement functions / actions specified in blocks or blocks of a flowchart and / or block diagram, thereby causing a series of operational steps on the computer, other programmable device, or other apparatus to generate a computer implementation process.

[0093] The flowcharts and block diagrams in the figures illustrate the architecture, functions, and operations of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in a flowchart or block diagram represents a module, segment, or portion of instructions, comprising one or more executable instructions for implementing a specified logical function. Methods, computer systems, and computer-readable media may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than those depicted in the figures. In some alternative embodiments, the functions described in the blocks may occur outside the order shown in the figures. For example, two consecutively shown blocks may actually be executed simultaneously or nearly simultaneously, and blocks may sometimes be executed in reverse order depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, may be implemented by a special-purpose hardware-based system that performs a specified function or action or a combination of special-purpose hardware and computer instructions.

[0094] It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware, firmware, or combinations of hardware and software. The specific control hardware or software code used to implement these systems and / or methods is not limiting to the implementation. For this reason, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It will be understood that software and hardware may be designed to implement the systems and / or methods based on the descriptions herein.

Claims

1. It is a vehicle system, First sensor and The second sensor and A first controller connected to the first sensor and the second sensor, A second controller connected to the first controller and Equipped with, The first controller is configured to perform a first operation using data from the first sensor. The second controller is configured to perform a second operation using data from the second sensor via the first controller. A vehicle system in which the second sensor is not connected to the second controller so that the second controller receives data from the second sensor via the first controller.

2. The vehicle system according to claim 1, wherein the first controller is connected to the first sensor and the second sensor so as to transmit data from the first sensor and data from the second sensor to the first controller in one direction.

3. The vehicle system according to claim 2, wherein the second controller is connected to the first controller so that data from the first controller is transmitted to the second controller in one direction, and the data from the first controller includes data from the second sensor.

4. The vehicle system according to any one of claims 1 to 3, wherein the first controller includes a first system-on-a-chip (SoC), and the second controller includes a second SoC separated from the first SoC.

5. The vehicle system according to claim 4, wherein the first SoC includes a safety-critical SoC, and the second SoC includes a non-safety-critical SoC.

6. The vehicle system according to any one of claims 1 to 3, wherein the first sensor includes a safety-related sensor and the second sensor includes a non-safety-related sensor.

7. The vehicle system according to any one of claims 1 to 3, wherein all sensors in the vehicle system are connected to the first controller.

8. The first controller connected to the first and second sensors receives data from the first sensor and data from the second sensor, The first controller performs a first operation using data from the first sensor, A step of receiving data from the first controller by a second controller connected to the first controller, wherein the data from the first controller includes data from the second sensor, The second controller performs a second operation using data from the second sensor included in the data from the first controller. Methods that include...

9. The method according to claim 8, wherein the first controller is connected to the first sensor and the second sensor so as to transmit data from the first sensor and data from the second sensor to the first controller in one direction.

10. The method according to claim 9, wherein the second controller is connected to the first controller so that data from the first controller is transmitted to the second controller in one direction.

11. The method according to any one of claims 8 to 10, wherein the first controller includes a first system-on-a-chip (SoC), and the second controller includes a second SoC separated from the first SoC.

12. The method according to claim 11, wherein the first SoC includes a safety-critical SoC, and the second SoC includes a non-safety-critical SoC.

13. The method according to any one of claims 8 to 10, wherein the first sensor includes a safety-related sensor and the second sensor includes a non-safety-related sensor.

14. The method according to any one of claims 8 to 10, wherein all sensors in the vehicle system are connected to the first controller.

15. A computer program comprising instructions that can be executed by at least one processor, The instruction is given to at least one processor, The first controller connected to the first and second sensors receives data from the first sensor and data from the second sensor, The first controller performs a first operation using data from the first sensor, A step of receiving data from the first controller by a second controller connected to the first controller, wherein the data from the first controller includes data from the second sensor, The second controller performs a second operation using data from the second sensor included in the data from the first controller. A computer program that causes a computer to perform a method that includes such a method.

16. The computer program according to claim 15, wherein the first controller is connected to the first sensor and the second sensor so that data from the first sensor and data from the second sensor are transmitted to the first controller in one direction.

17. The computer program according to claim 16, wherein the second controller is connected to the first controller so that data from the first controller is transmitted to the second controller in one direction.

18. The computer program according to any one of claims 15 to 17, wherein the first controller includes a first system-on-a-chip (SoC), and the second controller includes a second SoC separated from the first SoC.

19. The computer program according to claim 18, wherein the first SoC includes a safety-critical SoC, and the second SoC includes a non-safety-critical SoC.

20. The computer program according to any one of claims 15 to 17, wherein the first sensor includes a safety-related sensor and the second sensor includes a non-safety-related sensor.

Images