Signal processing device and vehicle display apparatus including the same

Abstract

The invention relates to a signal processing device and a vehicle display apparatus having the same. A signal processing device according to one embodiment of the present invention comprises: an interface for exchanging data with a second signal processing device connected to a first device; a virtual device driver emulating to receive data from the first device; and a display driver that outputs image data on a vehicle display on the basis of the data from the virtual device driver. As a result, it is possible to efficiently perform data transfer between the plurality of signal processing devices in the vehicle.

Description

Technical Field

[0001] The present invention relates to a signal processing device and a vehicle display device having the signal processing device, and more particularly, to a signal processing device capable of efficiently performing data transfer between a plurality of signal processing devices in a vehicle and a vehicle display device having the signal processing device. Background Art

[0002] A vehicle is a device that moves in a direction desired by a user who rides in it. For example, an automobile can be cited as a representative.

[0003] On the other hand, a vehicle display device is mounted inside the vehicle to facilitate use by the user of the vehicle.

[0004] As software functions become important, vehicle display devices require high-performance computing systems.

[0005] Among them, a high-performance integrated vehicle display device has a plurality of signal processing devices.

[0006] For example, a plurality of signal processing devices can be directly connected to a high-speed data bus, for example, a PCI Express (Peripheral Component Interconnect Express) bus.

[0007] In such a case, it is necessary to define and implement a suitable protocol and an Application Programming Interface (API) between the plurality of signal processing devices.

[0008] In this case, it is necessary to individually define the protocol and the application programming interface according to the function or service, which has problems such as increasing the complexity of system design and implementation. Summary of the Invention

[0009] Problems to be Solved by the Invention

[0010] An object of the present invention is to provide a signal processing device capable of efficiently performing data transfer between a plurality of signal processing devices in a vehicle and a vehicle display device having the signal processing device.

[0011] On the other hand, another object of the present invention is to provide a signal processing device capable of abstracting data in the kernel space when transferring data between a plurality of signal processing devices in a vehicle and a vehicle display device having the signal processing device.

[0012] On the other hand, another object of the present invention is to provide a signal processing device that can omit the addition of a communication protocol when transmitting data between a plurality of signal processing devices in a vehicle, and a vehicle display device having the signal processing device.

[0013] On the other hand, another object of the present invention is to provide a signal processing device that can transmit data from a plurality of devices between a plurality of signal processing devices in a vehicle, and a vehicle display device having the signal processing device.

[0014] Technical solutions for solving the problems

[0015] To achieve the above object, a signal processing device according to an embodiment of the present invention and a vehicle display device having the signal processing device include: an interface that exchanges data with a second signal processing device connected to a first device; a virtual device driver that emulates to receive data from the first device; and a display driver that outputs image data on a vehicle display based on the data from the virtual device driver.

[0016] On the other hand, the interface may include a high-speed bus driver that exchanges data through a high-speed data bus channel.

[0017] On the other hand, the interface may receive data through a device driver, a device renderer, and a second interface in the second signal processing device.

[0018] On the other hand, the interface may receive data abstracted in the kernel space.

[0019] On the other hand, the interface and the virtual device driver may operate based on the kernel space.

[0020] On the other hand, the virtual device driver may perform register control, data buffer control, and interrupt reception.

[0021] On the other hand, the signal processing device may further include a device multiplexer that multiplexes each data from a plurality of devices, and the interface may transmit the multiplexed data to the second signal processing device.

[0022] On the other hand, the virtual device driver may include a device multiplexer.

[0023] On the other hand, the device multiplexer may process data from a plurality of devices based on a priority order.

[0024] On the other hand, the multiplexed data output from the device multiplexer may include a header and a payload. The header includes ID (identifier) information of a plurality of devices, and the payload includes a part of the respective data of the plurality of devices.

[0025] On the other hand, the signal processing device may further include a demultiplexer that demultiplexes the multiplexed data from the second signal processing device, and the display driver outputs image data on the vehicle display based on the data from the demultiplexer.

[0026] On the other hand, the signal processing device may further include a service manager that performs communication with the second signal processing device based on an interface and an additional communication channel. The service manager may control to end the communication with the device renderer in the second signal processing device and end the communication with the interface based on an unload event of the first device.

[0027] On the other hand, based on a load event of a second device connected to the second signal processing device, the service manager controls to perform communication with a second device renderer corresponding to the second device in the second signal processing device and communication with the interface.

[0028] On the other hand, the first device may include a camera, a lidar, a radar, or a sensor device.

[0029] To achieve the above object, a signal processing device and a vehicle display device having the signal processing device according to another embodiment of the present invention include: an interface that exchanges data with a second signal processing device connected to a camera device; a virtual device driver that emulates to receive data from the camera device; a display driver that outputs image data on the vehicle display based on the data from the virtual device driver; and a graphics renderer that renders the data of the display. The interface transmits the data from the graphics renderer to the second signal processing device.

[0030] On the other hand, the signal processing device may further include an input device renderer that renders data from an input device, and the interface may also transmit the data from the input device renderer to the second signal processing device.

[0031] On the other hand, the signal processing device may further include: an audio output renderer that renders data from an audio output device; and an audio input renderer that renders data from an audio input device. The interface may transmit the data from the audio output renderer or the data from the audio input renderer to the second signal processing device.

[0032] On the other hand, the signal processing device may further include a second virtual driver, which emulates in order to receive data from a storage device connected to the second signal processing device.

[0033] Advantages of the Invention

[0034] The signal processing device according to an embodiment of the present invention and a vehicle display device having the same include: an interface for exchanging data with a second signal processing device connected to a first device; a virtual device driver for emulating in order to receive data from the first device; and a display driver for outputting image data on a vehicle display based on data from the virtual device driver. Accordingly, data transfer between a plurality of signal processing devices in a vehicle can be efficiently performed. In addition, when transferring data between a plurality of signal processing devices in a vehicle, addition of a communication protocol can be omitted.

[0035] On the other hand, the interface may include a high-speed bus driver for exchanging data through a high-speed data bus channel. Accordingly, data transfer between a plurality of signal processing devices in a vehicle can be efficiently performed.

[0036] On the other hand, the interface may receive data through a device driver, a device renderer, and a second interface in the second signal processing device. Accordingly, data transfer between a plurality of signal processing devices in a vehicle can be efficiently performed.

[0037] On the other hand, the interface may receive data abstracted in the kernel space. Accordingly, when transferring data between a plurality of signal processing devices in a vehicle, data can be abstracted in the kernel space without modifying the data in middleware or a framework. In addition, when transferring data between a plurality of signal processing devices in a vehicle, addition of a communication protocol can be omitted.

[0038] On the other hand, the interface and the virtual device driver operate based on the kernel space. Accordingly, when transferring data between a plurality of signal processing devices in a vehicle, data can be abstracted in the kernel space without modifying the data in middleware or a framework. In addition, when transferring data between a plurality of signal processing devices in a vehicle, addition of a communication protocol can be omitted.

[0039] On the other hand, the virtual device driver may perform register control, data buffer control, and interrupt reception. Accordingly, data transfer between a plurality of signal processing devices in a vehicle can be efficiently performed.

[0040] On the other hand, the signal processing device may further include a device multiplexer that multiplexes respective data from a plurality of devices, and an interface that transmits the multiplexed data to a second signal processing device. Thereby, it is possible to transmit data from a plurality of devices among a plurality of signal processing devices in a vehicle.

[0041] On the other hand, the virtual device driver may include a device multiplexer. Thereby, it is possible to transmit data from a plurality of devices among a plurality of signal processing devices in a vehicle.

[0042] On the other hand, the device multiplexer may process data from a plurality of devices based on a priority order. Thereby, it is possible to transmit data from a plurality of devices among a plurality of signal processing devices in a vehicle.

[0043] On the other hand, the multiplexed data output from the device multiplexer includes a header and a payload. The header includes ID information of a plurality of devices, and the payload includes a part of the respective data of a plurality of devices. Thereby, it is possible to transmit data from a plurality of devices among a plurality of signal processing devices in a vehicle.

[0044] On the other hand, the signal processing device may further include a demultiplexer that demultiplexes the multiplexed data from the second signal processing device, and a display driver that can output image data on a vehicle display based on the data from the demultiplexer. Thereby, it is possible to transmit data from a plurality of devices among a plurality of signal processing devices in a vehicle.

[0045] On the other hand, the signal processing device may further include a service manager that performs communication with the second signal processing device based on the interface and an additional communication channel. The service manager controls to end the communication with the device renderer in the second signal processing device and end the communication with the interface based on an unload event of the first device. Thereby, it is possible to transmit data from a plurality of devices among a plurality of signal processing devices in a vehicle.

[0046] On the other hand, the service manager may control to perform communication with a second device renderer corresponding to the second device in the second signal processing device and communication with the interface based on a load event of the second device connected to the second signal processing device.

[0047] On the other hand, the first device may include a camera or a lidar or a radar or a sensor device. Thereby, it is possible to transmit data from various devices among a plurality of signal processing devices in a vehicle.

[0048] On the other hand, a signal processing device according to another embodiment of the present invention and a vehicle display device having the signal processing device include: an interface that exchanges data with a second signal processing device connected to a camera device; a virtual device driver that performs emulation in order to receive data from the camera device; a display driver that outputs image data on a vehicle display based on data from the virtual device driver; and a graphics renderer that renders data for the display; the interface transmits data from the graphics renderer to the second signal processing device. Thus, data transmission between a plurality of signal processing devices in a vehicle can be efficiently performed. In addition, when transmitting data between a plurality of signal processing devices in a vehicle, addition of a communication protocol can be omitted.

[0049] On the other hand, the signal processing device may further include an input device renderer that renders data from an input device, and the interface may also transmit data from the input device renderer to the second signal processing device. Thus, data from various devices can be transmitted between a plurality of signal processing devices in a vehicle.

[0050] On the other hand, the signal processing device may further include: an audio output renderer that renders data from an audio output device; and an audio input renderer that renders data from an audio input device; the interface may also transmit data from the audio output renderer or data from the audio input renderer to the second signal processing device. Thus, data from various devices can be transmitted between a plurality of signal processing devices in a vehicle.

[0051] On the other hand, the signal processing device may further include a second virtual driver that performs emulation in order to receive data from a storage device connected to the second signal processing device. Thus, data from various devices can be transmitted between a plurality of signal processing devices in a vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1a is a diagram showing an example of the exterior and interior of a vehicle.

[0053] Figure 1b is a diagram showing another example of the interior of a vehicle.

[0054] Figure 2 is a diagram showing the appearance of a vehicle display device according to an embodiment of the present invention.

[0055] Figure 3 Illustrates Figure 2 an example of the internal block diagram of a vehicle display device.

[0056] Figure 4 is a diagram showing a system driven in a signal processing device related to the present invention.

[0057] Figure 5 This is a diagram showing an example of a system driven in a signal processing device according to an embodiment of the present invention.

[0058] Figure 6 This is a diagram for explaining the operation of a system driven in a signal processing device according to an embodiment of the present invention.

[0059] Figure 7 This is a diagram showing a plurality of signal processing devices in a vehicle display device according to an embodiment of the present invention.

[0060] Figure 8a and Figure 8b These are various examples showing data transfer between a plurality of signal processing devices related to the present invention.

[0061] Figure 9 This is a reference diagram showing data transfer between a plurality of signal processing devices related to the present invention.

[0062] Figure 10 This is a diagram illustrating data transfer between a plurality of signal processing devices according to an embodiment of the present invention.

[0063] Figures 11 to 22 This is Figure 10 a reference diagram for the description of.

[0064] Figure 23 This is a diagram showing an example of a signal processing system including a plurality of signal processing devices according to an embodiment of the present invention. Detailed Description of the Invention

[0065] Hereinafter, the present invention will be described in more detail with reference to the accompanying drawings.

[0066] In the following description, the suffixes “module” and “section” for components are given only for the convenience of writing the specification, and they do not have any particularly important meaning or function in themselves. Therefore, the “module” and “section” can also be used interchangeably with each other.

[0067] Figure 1a This is a diagram showing an example of the outside and inside of a vehicle.

[0068] Referring to the accompanying drawings, the vehicle 200 operates through a plurality of wheels 103FR, 103FL, 103RL... and a steering wheel 150. The plurality of wheels 103FR, 103FL, 103RL... rotate by a power source, and the steering wheel 150 is used to adjust the traveling direction of the vehicle 200.

[0069] On the other hand, the vehicle 200 may also have a camera 195 or the like for acquiring an image in front of the vehicle.

[0070] On the other hand, inside the vehicle 200, there may be a plurality of displays 180a and 180b for displaying images, information, etc.

[0071] In Figure 1a , as the plurality of displays 180a and 180b, an instrument cluster display 180a and an AVN (AudioVideo Navigation) display 180b are exemplified. In addition, there may be a HUD (Head UpDisplay), etc.

[0072] On the other hand, the AVN (Audio Video Navigation) display 180b may also be named as a Center Information Dislpay.

[0073] An embodiment of the present invention proposes a solution for sharing data processing in a vehicle display device 100 having a plurality of displays 180a and 180b.

[0074] On the other hand, the vehicle 200 described in this specification may be a concept that encompasses vehicles having an engine as a power source, hybrid vehicles having an engine and an electric motor as power sources, electric vehicles having an electric motor as a power source, and the like.

[0075] Figure 1b It is a diagram showing another example of the interior of a vehicle.

[0076] Referring to the drawings, an instrument cluster display 180a, an AVN (Audio VideoNavigation) display 180b, rear seat entertainment (Rear Seat Entertainment) displays 180c and 180d, a rearview mirror display (not shown), etc. may be installed inside the vehicle.

[0077] Figure 2 It is a diagram showing the appearance of a vehicle display device according to an embodiment of the present invention.

[0078] The vehicle display device 100 according to an embodiment of the present invention may include: a plurality of displays 180a to 180b; a signal processing device 170 that performs signal processing for displaying images, information, etc. on the plurality of displays 180a to 180b; at least one display 180c to 180d; and a second signal processing device 170b that performs signal processing for displaying images, information, etc. on at least one display 180c to 180d.

[0079] The signal processing device 170 and the second signal processing device 170b may be arranged separately from each other.

[0080] On the other hand, the second signal processing device 170b can be driven according to an operating system (OS) different from that of the signal processing device 170.

[0081] Among the plurality of displays 180a to 180b, the first display 180a can be a cluster display 180a for displaying driving status, operation information, etc., and the second display 180b can be an AVN (Audio Video Navigation) display 180b for displaying vehicle execution information, navigation maps, various entertainment information, or images.

[0082] Among at least one of the displays 180c to 180d, the third display 180c can be a display for rear-seat entertainment on the right side of the vehicle, and the fourth display 180d can be a display for rear-seat entertainment on the left side of the vehicle.

[0083] At least one of the displays 180c to 180d can display driving status information, simple navigation information, various entertainment information, or images.

[0084] A processor 175 is provided inside the signal processing device 170, and the signal processing device 170 can implement a server virtual machine, a first guest virtual machine to a second guest virtual machine 520 to 540 on a hypervisor 505 within the processor 175.

[0085] The server virtual machine 520 can correspond to a server virtual machine, and the first guest virtual machine to the second guest virtual machine can correspond to guest virtual machines.

[0086] Thus, data communication can be performed between the server virtual machine 520 and the second or second guest virtual machines 530, 50 according to a server interface and a client interface.

[0087] The first guest virtual machine 530 can operate for the first display 180a, and the second guest virtual machine 540 can operate for the second display 180b.

[0088] On the other hand, for data sharing processing, the server virtual machine 520 within the processor 175 can share at least a part of the data with the first guest virtual machine 530 and the second guest virtual machine 540.

[0089] On the other hand, after receiving and processing the wheel speed sensor data of the vehicle, the server virtual machine 520 within the processor 175 can transmit the processed wheel speed sensor data to at least one of the first guest virtual machine 530 or the second guest virtual machine 540 or the second signal processing device 170b. Thus, it is possible to share the wheel speed sensor data of the vehicle with at least one virtual machine or the second signal processing device or the like.

[0090] On the other hand, the server virtual machine 520 within the processor 175 records in the first shared memory 508a to transfer a part of the data to the first guest virtual machine 530, and records in the first shared memory 508a to transfer another part of the data to the second guest virtual machine. The first guest virtual machine 530 and the second guest virtual machine 540 can be controlled to process the received data respectively, and record the processed data in a second shared memory (not shown). Thus, it is possible to efficiently execute the data processing of a plurality of signal processing devices within the vehicle.

[0091] On the other hand, in order to transmit the same data to the first guest virtual machine 530 and the second guest virtual machine 540, the server virtual machine 520 within the processor 175 can be controlled to set the shared memory 508 based on the hypervisor 505. Thus, the same information or the same image can be synchronously displayed on the first display 180a and the second display 180b within the vehicle.

[0092] The signal processing device 170 can be internally provided with a processor 175, and the server virtual machine, the first guest virtual machine to the second guest virtual machine 520 to 540 can be executed on the hypervisor 505 within the processor 175.

[0093] The server virtual machine 520 can correspond to a server virtual machine, and the first guest virtual machine to the second guest virtual machine can correspond to guest virtual machines.

[0094] Thus, data communication can be performed between the server virtual machine 520 and the second or the second guest virtual machines 530, 50 according to the server interface and the client interface.

[0095] On the other hand, the second signal processing device 170b can be internally provided with a second processor 175b, and the server virtual machine (Server virtual maschine) VIMc, the guest virtual machine (guest virtual maschine) VIMd, etc. can be executed on the hypervisor 505 within the second processor 175b.

[0096] On the other hand, a part of the plurality of displays 180a to 180d can operate based on the Linux operating system (Linux OS), and another part can operate based on the web operating system (Web OS).

[0097] The signal processing device 170 and the second signal processing device 170b according to the embodiments of the present invention can also process by sharing data among the displays 180a to 180d that can operate under various operating systems (OS).

[0098] The signal processing device 170 and the second signal processing device 170b according to the embodiments of the present invention can be controlled to synchronously display the same information or the same image even among the displays 180a to 180c that operate under various operating systems (OS).

[0099] On the other hand, for data sharing and processing, the signal processing device 170 and the second signal processing device 170b according to the embodiments of the present invention can share at least a part of the data. Thereby, data can be shared and processed among the plurality of signal processing devices 170 and 170b for the plurality of displays in the vehicle. In addition, resources can be efficiently managed among the plurality of signal processing devices 170 and 170b.

[0100] Figure 3 An example of the internal block diagram of the vehicle display device according to the embodiments of the present invention is illustrated.

[0101] Referring to the drawings, the vehicle display device 100 according to the embodiments of the present invention can include an input unit 110, a communication unit 120, an interface 130, a second interface 130b, a signal processing device 170, a second signal processing device 170b, a plurality of displays 180a to 180d, an audio output unit 185, and a power supply unit 190.

[0102] The input unit 110 can include physical keys for key input, touch input, etc., a pad, etc.

[0103] On the other hand, the input unit 110 can include a microphone (not shown) for voice input of the user.

[0104] The communication unit 120 can exchange data with the mobile terminal 800 or the server 900 in a wireless manner.

[0105] In particular, the communication unit 120 may exchange data with the mobile terminal of the vehicle driver in a wireless manner. As the wireless data communication method, various data communication methods such as Bluetooth, WiFi (Wireless-Fidelity), WiFi Direct, and APiX may be adopted.

[0106] The communication unit 120 may receive weather information and traffic condition information of the road from the mobile terminal 800 or the server 900. For example, it may receive TPEG (Transport Protocol Expert Group) information. To this end, the communication unit 120 may have a mobile communication module (not shown).

[0107] The interface 130 may receive sensor information, etc. from the ECU (electronic control unit) 770 or the sensor device 760, and transmit the received information to the signal processing device 170.

[0108] The second interface 130b may receive sensor information, etc. from the ECU 770 or the sensor device 760, and transmit the received information to the second signal processing device 170b.

[0109] Here, the sensor information may include at least one of vehicle direction information, vehicle position information (GPS information), vehicle angle information, vehicle speed information, vehicle acceleration information, vehicle inclination information, vehicle forward / backward information, battery information, fuel information, tire information, headlight information, in-vehicle temperature information, and in-vehicle humidity information.

[0110] Such sensor information may be obtained from a heading sensor, a yaw sensor, a gyro sensor, a position module, a vehicle forward / backward sensor, a wheel sensor, a vehicle speed sensor, a vehicle body inclination sensing sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor based on the rotation of the steering wheel, an in-vehicle temperature sensor, an in-vehicle humidity sensor, etc. On the other hand, the position module may include a GPS module for receiving GPS (Global Positioning System) information.

[0111] On the other hand, the interface 130 may receive vehicle front image data, vehicle side image data, vehicle rear image data, vehicle surrounding obstacle distance information, etc. from the camera 195 or the lidar (not shown), etc., and transmit the received information to the signal processing device 170.

[0112] The memory 140 can store various data for the entire operation of the vehicle display device 100, such as programs for the processing or control of the signal processing device 170.

[0113] For example, the memory 140 can store data regarding a hypervisor, a server virtual machine, and first to second guest virtual machines to be executed within the processor 175.

[0114] On the other hand, as shown in the figure, the memory 140 can be provided within the signal processing device 170, but is not limited thereto, and the memory 140 can also be configured outside the signal processing device 170.

[0115] The audio output unit 185 converts an electrical signal from the signal processing device 170 into an audio signal and outputs it. For this purpose, it can include a speaker or the like.

[0116] The power supply unit 190 can supply power required for the operation of each component under the control of the signal processing device 170. In particular, the power supply unit 190 can receive power from a battery or the like inside the vehicle.

[0117] The signal processing device 170 controls the entire operation of each unit within the vehicle display device 100.

[0118] For example, the signal processing device 170 can include a processor 175 that performs signal processing for at least one of the first display 180a or the second display 180b and a memory 140.

[0119] The processor 175 can execute a server virtual machine, first to second guest virtual machines 520 - 540 on a hypervisor ( Figure 5 505) within the processor 175.

[0120] Among the server virtual machine, first to second guest virtual machines ( Figure 5 520 - 540), the server virtual machine 520 can be named as a Server Virtual Machine, and the first to second guest virtual machines 530 - 540 can be named as Guest Virtual Machines.

[0121] At this time, the first guest virtual machine 530 can operate for the first display 180a, and the second guest virtual machine 540 can operate for the second display 180b.

[0122] For example, the server virtual machine 520 within the processor 175 may receive vehicle sensor data, location information data, camera image data, audio data, or touch input data, and output the data after processing or machining. By differentiating the data processed only by a legacy virtual machine and the data processed by the server virtual machine 520, data processing can be effectively performed. In particular, by executing most of the data processing in the server virtual machine 520, 1:N data sharing can be achieved.

[0123] As another example, the server virtual machine 520 may directly receive and process CAN (Controller Area Network) communication data, audio data, broadcast data, USB (Universal Serial Bus) data, and wireless communication data for the first to second client virtual machines 530-540.

[0124] Moreover, the server virtual machine 520 may transmit the processed data to the first to second client virtual machines 530-540.

[0125] Thus, among the server virtual machine, the first to second client virtual machines 520-540, only the server virtual machine 520 receives communication data and external input data and performs signal processing, thereby reducing the signal processing burden on other virtual machines, enabling 1:N data communication, and further enabling synchronization during data sharing.

[0126] On the other hand, the server virtual machine 520 records in the first shared memory 508a to transfer a part of the data to the first client virtual machine 530 and records in the first shared memory 508a to transfer another part of the data to the second client virtual machine. The first client virtual machine 530 and the second client virtual machine 540 process the respectively received data and are controlled to record the processed data in a second shared memory (not shown). Thereby, data processing can be efficiently performed among a plurality of signal processing devices in the vehicle.

[0127] The data at this time may be any one of image data, audio data, navigation data, and voice recognition data.

[0128] On the other hand, the server virtual machine 520 processes another part of the data and may be controlled to record the processed data in a second shared memory (not shown). That is, in addition to the first client virtual machine 530 and the second client virtual machine, the server virtual machine 520 may additionally execute data processing.

[0129] On the other hand, the server virtual machine 520 can generate respective instruction queues for distributed processing of data in the first to second client virtual machines 530, 540. Thereby, processing of data can be shared among a plurality of virtual machines.

[0130] On the other hand, in the case where the first to second client virtual machines 530, 540 share the same data, the server virtual machine 520 in the processor 175 can generate one identical instruction queue. Thereby, the same data can be synchronized and shared.

[0131] On the other hand, the server virtual machine 520 can generate instruction queues corresponding to the number of virtual machines for distributed processing of data.

[0132] On the other hand, for distributed processing of data, the server virtual machine 520 can be controlled to transfer at least a part of the data to at least one of the first client virtual machine 530 or the second client virtual machine 540 or the second signal processing device 170b.

[0133] For example, the server virtual machine 520 can be the first shared memory 508a for transferring at least a part of the data to at least one of the first client virtual machine 530 or the second client virtual machine 540 or the second signal processing device 170b, and the image data processed in the first client virtual machine 530 or the second client virtual machine 540 can be recorded in a second shared memory (not shown).

[0134] On the other hand, the server virtual machine 520 can be controlled to record the data in the shared memory 508 and share the same data with the first client virtual machine 530 and the second client virtual machine 540.

[0135] For example, the server virtual machine 520 can be controlled to record broadcast data or wireless communication data in the shared memory 508 and share the same data with the first client virtual machine 530 and the second client virtual machine 540. Thereby, 1:N type data sharing can be achieved.

[0136] As a result, by executing most of the data processing in the server virtual machine 520, 1:N type data sharing can be achieved.

[0137] On the other hand, the server virtual machine 520 in the processor 175 can be controlled to set the shared memory 508 based on the hypervisor 505 for transferring the same data to the first client virtual machine 530 and the second client virtual machine 540.

[0138] That is, the server virtual machine 520 within the processor 175 can utilize the shared memory 508 based on the hypervisor 505 to synchronize the same data and transmit it to the first guest virtual machine 530 and the second guest virtual machine 540. Accordingly, the same image can be synchronously displayed on the plurality of in-vehicle displays 180a to 180b.

[0139] On the other hand, the signal processing device 170 can process various signals such as audio signals, image signals, and data signals. For this purpose, the signal processing device 170 can be implemented in the form of a system on chip (SOC).

[0140] The second signal processing device 170b can perform signal processing for the vehicle displays 180c and 180d. For this purpose, the second signal processing device 170b can include a second processor 175b and a second memory 140b.

[0141] The second processor 175b can execute a plurality of virtual machines (520b, 530b, 540b in FIG. 8) on the hypervisor (505 in FIG. 8) within the second processor 175b.

[0142] On the other hand, the second processor 175b can also execute a server virtual machine and guest virtual machines on the hypervisor within the second processor 175b.

[0143] For example, the server virtual machine within the second processor 175b can receive vehicle sensor data, location information data, camera image data, audio data, or touch input data from the server virtual machine 520 within the processor 175 in the signal processing device 170, and output the data after processing or processing it.

[0144] As another example, the server virtual machine within the second processor 175b can receive CAN communication data, audio data, broadcast data, USB data, and wireless communication data from the server virtual machine 520 within the processor 175 in the signal processing device 170 for the guest virtual machines and process the data.

[0145] In addition, the server virtual machine within the second processor 175b can transmit the processed data to the guest virtual machines.

[0146] Accordingly, by having only the server virtual machine among the server virtual machine and guest virtual machines within the second processor 175b receive communication data and external input data to perform signal processing, the signal processing burden on the guest virtual machines is reduced, 1:N data communication can be achieved, and synchronization during data sharing can be achieved.

[0147] On the other hand, in order to transfer the same data to the customer virtual machine, the server virtual machine in the second processor 175b can be controlled to set the shared memory (508b in FIG. 8) based on the hypervisor 505.

[0148] That is, the server virtual machine in the second processor 175b can use the shared memory 508b based on the hypervisor 505 to synchronize and transfer the same data to the customer virtual machine. Thus, the same image can be synchronously displayed on a plurality of displays 180c to 180d in the vehicle.

[0149] On the other hand, the second signal processing device 170b can process various signals such as audio signals, image signals, and data signals. For this purpose, the second signal processing device 170b can be implemented in the form of a system on chip (SOC).

[0150] Figure 4 FIG. is a diagram showing a system driven in a signal processing device related to the present invention.

[0151] Referring to the accompanying drawings, Figure 4 FIG. is an example diagram showing the use of virtual machines for the cluster display 180a and the AVN display 180b, respectively.

[0152] Figure 4 The system 400 driven in the signal processing device of FIG. illustrates a case where the cluster virtual machine 430 and the AVN virtual machine 440 are executed on the hypervisor 405 in the processor 175 within the signal processing device 170.

[0153] On the other hand, Figure 4 The system 400 driven in the signal processing device of FIG. illustrates a case where a legacy virtual machine 410 is also executed on the hypervisor 405 in the processor 175.

[0154] The legacy virtual machine 410 has an interface 412 for data communication with the memory 140 and an interface 413 for Ethernet communication.

[0155] On the other hand, the cluster virtual machine 430 can have an interface 431 for CAN communication, an interface 432 for communication between the interface 412 of the legacy virtual machine 410, and an interface 433 for communication between the interface 413 of the legacy virtual machine 410.

[0156] On the other hand, the AVN virtual machine 440 may have an interface 441 for input / output of audio data, broadcast data, USB data, and wireless communication data, an interface 442 for communication between the interface 412 of the legacy virtual machine 410, and an interface 443 for communication between the interface 413 of the legacy virtual machine 410.

[0157] According to this system 400, CAN communication data is only input / output in the cluster virtual machine 430, so there is a disadvantage that CAN communication data cannot be used in the AVN virtual machine 440.

[0158] In addition, according to Figure 4 the system 400, audio data, broadcast data, USB data, and wireless communication data are only input / output in the AVN virtual machine 440, so there is a disadvantage that the above data cannot be used in the cluster virtual machine 430.

[0159] On the other hand, there is a disadvantage that the cluster virtual machine 430 and the cluster virtual machine 430 need to have separate interfaces 431, 432, 441, and 442 for memory data and Ethernet communication data for input / output in the legacy virtual machine 410, respectively.

[0160] Therefore, in the present invention, a solution for improving Figure 4 the system is proposed. That is, differently from Figure 4 , the virtual machines are divided into server virtual machines and client virtual machines. Various memory data, communication data, etc. are input / output in the server virtual machines, and not in the client virtual machines. For this, a description will be made with reference to Figure 5 the following figures.

[0161] Figure 5 FIG. is a diagram showing an example of a system driven in a signal processing device according to an embodiment of the present invention.

[0162] Referring to the accompanying drawings, Figure 5 an example of the system 500 shows a situation where a server virtual machine 520, a first client virtual machine 530, and a second client virtual machine 540 are executed on a hypervisor 505 in a processor 175 within a signal processing device 170.

[0163] The first client virtual machine 530 may be a virtual machine for the cluster display 180a, and the second client virtual machine 540 may be a virtual machine for the AVN display 180b.

[0164] That is, the first client virtual machine 530 and the second client virtual machine 540 may operate for image rendering of the cluster display 180a and the AVN display 180b, respectively.

[0165] On the other hand, in the system 500 driven by the signal processing device 170 of Figure 5 an example is shown in which a legacy virtual machine 510 is also executed on the hypervisor 505 within the processor 175.

[0166] The legacy virtual machine 510 has an interface 511 for data communication with the memory 140 and Ethernet communication.

[0167] On the other hand, the legacy virtual machine 510 may also have an interface (virtio-backend interface) 512 for data communication with the first to second guest virtual machines 530, 540.

[0168] The server virtual machine 520 may have: an interface 521 for input / output of audio data, broadcast data, USB data, and wireless communication data; and an input / output server interface 522 for data communication with the guest virtual machines.

[0169] That is, the server virtual machine 520 can provide non-virtualizable I / O to a plurality of guest virtual machines, such as the first to second guest virtual machines 530, 540, etc., through standard virtualization technology (VirtIO).

[0170] On the other hand, the server virtual machine 520 controls broadcast data, audio data, etc. at the supervisor level and provides them to a plurality of guest virtual machines, such as the first to second guest virtual machines 530, 540, etc.

[0171] On the other hand, the server virtual machine 520 can process vehicle data, sensor data, vehicle surrounding information, etc., and provide the processed data or information, etc. to a plurality of guest virtual machines, such as the first to second guest virtual machines 530, 540, etc.

[0172] On the other hand, the server virtual machine 520 can provide services (Supervisory Services) such as processing of vehicle data and management of audio routing.

[0173] Next, the first guest virtual machine 530 may have: an input / output client interface 532 for data communication with the server virtual machine 520; and APIs 533 for controlling the input / output client interface 532.

[0174] In addition, the first guest virtual machine 530 may have an interface (virtio-backend interface) for data communication with the legacy virtual machine 510.

[0175] The first guest virtual machine 530 may receive memory data based on communication with the memory 140 and Ethernet data based on Ethernet communication from the interface (virtio-backend interface) 512 of the legacy virtual machine 510 through the interface (virtio-backend interface).

[0176] Next, the second guest virtual machine 540 may have: an input / output client interface 542 for data communication with the server virtual machine 520; and APIs 543 for controlling the input / output client interface 542.

[0177] In addition, the second guest virtual machine 540 may have an interface (virtio-backend interface) for data communication with the legacy virtual machine 510.

[0178] The second guest virtual machine 540 may receive memory data based on communication with the memory 140 and Ethernet data based on Ethernet communication from the interface (virtio-backend interface) 512 of the legacy virtual machine 510 through the interface (virtio-backend interface).

[0179] On the other hand, Figure 5 Differently, a legacy virtual machine 510 may also be set within the server virtual machine 520.

[0180] According to such a system 500, although CAN communication data is only input / output in the server virtual machine 520, it can be provided to a plurality of guest virtual machines, such as the first guest virtual machine to the second guest virtual machines 530, 540, etc., through data processing performed in the server virtual machine 520. Therefore, 1:N data communication based on the processing of the server virtual machine 520 can be achieved.

[0181] In addition, according to Figure 5 the system 500, although audio data, broadcast data, USB data, and wireless communication data are only input / output in the server virtual machine 520, they can be provided to a plurality of guest virtual machines, such as the first guest virtual machine to the second guest virtual machines 530, 540, etc., through data processing performed in the server virtual machine 520. Therefore, 1:N data communication based on the processing of the server virtual machine 520 can be achieved.

[0182] On the other hand, inFigure 5 In the system 500, the first guest virtual machine to the second guest virtual machines 530 and 540 may operate based on different operating systems (OSs).

[0183] For example, the first guest virtual machine 540 may operate based on the Linux OS, and the second guest virtual machine 540 may operate based on the WebOS.

[0184] Even if the first guest virtual machine to the second guest virtual machines 530 and 540 operate based on different operating systems (OSs), for data sharing, the server virtual machine 520 may further set up a shared memory 508 based on the hypervisor 505. Thus, even if the first guest virtual machine to the second guest virtual machines 530 and 540 operate based on different operating systems (OSs), the same data or the same image may be synchronized and shared. Ultimately, the same data or the same image can be synchronously displayed on the plurality of displays 180a and 180b.

[0185] Figure 6 It is a reference diagram for explaining the operation of the system driven in the signal processing apparatus according to an embodiment of the present invention.

[0186] Referring to the accompanying drawings, a processor 175 within the signal processing apparatus 170 may execute the server virtual machine, the first guest virtual machine to the second guest virtual machines 520 to 540 on the hypervisor 505 within the processor 175. The server virtual machine 520 within the processor 175 is controlled to set up a shared memory 508 based on the hypervisor 505 to transfer the same data to the first guest virtual machine 530 and the second guest virtual machine 540.

[0187] For example, the same image data may be illustrated using the same data. Thus, the same image can be synchronously displayed on the plurality of displays 180a to 180b within the vehicle.

[0188] On the other hand, according to Figure 6 the system 500, the processor 175 within the signal processing apparatus 170 executes the server virtual machine 520, the first guest virtual machine to the second guest virtual machines 530 to 540 on the hypervisor 505 within the processor 175. The server virtual machine 520 within the processor 175 may use the shared memory 508 based on the hypervisor 505 to synchronously transfer the same data to the first guest virtual machine 530 and the second guest virtual machine 540.

[0189] For example, as the same data, CAN communication data, audio data, broadcast data, USB data, wireless communication data, location information data, or touch data, etc. are illustrated. Thus, the same data can be synchronously displayed on the plurality of displays 180a to 180b within the vehicle.

[0190] On the other hand, although not marked in Figure 6 , the traditional virtual machine 510 can utilize the shared memory 508 based on the hypervisor 505 to synchronously transfer the memory data from the memory 140 and the Ethernet data based on Ethernet communication to the first guest virtual machine 530 and the second guest virtual machine 540. That is, 1:N data communication of the memory data or the Ethernet data can be performed. Thus, the same data can be synchronously transferred.

[0191] Figure 7 FIG. is a diagram showing a vehicle display device according to an embodiment of the present invention.

[0192] Referring to the accompanying drawings, a vehicle display device 100 according to an embodiment of the present invention includes a signal processing device 170 and a second signal processing device 170b. The signal processing device 170 includes a processor 175 that performs signal processing, and the second signal processing device 170b includes a second processor 175b that performs signal processing.

[0193] The signal processing device 170 performs signal processing for at least one of the first display 180a or the second display 180b in the vehicle 200.

[0194] The second signal processing device 170b performs signal processing for at least one of the third display 180c or the fourth display 180d in the vehicle 200.

[0195] On the other hand, the processor 175 in the signal processing device 170 executes the server virtual machine 520 and at least one guest virtual machine 530, 540.

[0196] The accompanying drawings illustrate that the processor 175 in the signal processing device 170 executes the first guest virtual machine to the second guest virtual machine 530, 540.

[0197] On the other hand, the second processor 175b in the second signal processing device 170b executes at least one guest virtual machine 520b, 530b, 540b.

[0198] The accompanying drawings illustrate that the second processor 175b in the second signal processing device 170b executes the third guest virtual machine to the fifth guest virtual machine 520b, 530b, 540b, but is not limited thereto, and may also execute only the third guest virtual machine to the fourth guest virtual machine 520b, 530b.

[0199] On the other hand, the processor 175 in the signal processing device 170 within the vehicle display device 100 according to an embodiment of the present invention executes the server virtual machine 520 and at least one client virtual machine 530, 540, and the second processor 175b in the second signal processing device 170b executes at least one client virtual machine 520b, 530b, 540b without executing the server virtual machine.

[0200] Thus, the server virtual machine 520 in the signal processing device 170 can efficiently control at least one client virtual machine 530, 540 executed in the signal processing device 170 and at least one client virtual machine 520b, 530b, 540b executed in the second signal processing device 170b.

[0201] Therefore, it is possible to improve the transfer efficiency during data transfer between the plurality of signal processing devices 170, 170b within the vehicle 200. In addition, it is possible to efficiently manage resources in the plurality of signal processing devices 170 for the plurality of displays within the vehicle 200.

[0202] On the other hand, the server virtual machine 520 may have a resource manager for resource management and an input / output server interface 522 for data communication with the client virtual machines.

[0203] On the other hand, each of the first to fifth client virtual machines 530, 540, 520b, 530b, 540b may have a resource manager for resource management and input / output client interfaces 532, 542, 522b, 532b, 542b for data communication with the server virtual machine 520.

[0204] On the other hand, the signal processing device 170 may have a plurality of processor cores 175a1 to 175a4, caches, a plurality of memories 140a1 to 140a4, a position information driver GS for receiving or processing position information data, a touch driver TU for receiving or processing touch input data, and a camera driver CA for receiving or processing camera image data.

[0205] On the other hand, the signal processing device 170 may also have a neural network processor NPa for neural network processing, a graphics processor GPa for image processing, and a high-speed interface HSI for high-speed data transfer. The high-speed interface HSI at this time may support PCIe or CCIX or CXL, etc.

[0206] On the other hand, the second signal processing device 170b may have a plurality of processor cores 175b1 to 175b4, caches, and a plurality of memories 140b1 to 140b4.

[0207] On the other hand, the second signal processing device 170b may also have a neural network processor NPb for the neural network processing process, a graphics processor GPb for the image processing processor, and a high-speed interface HSIb for high-speed data transfer. The high-speed interface HSIb at this time may support PCIe or CCIX or CXL, etc.

[0208] On the other hand, the server virtual machine 520 may control the guest virtual machine 530 executed within the processor 175 and the guest virtual machines 520b, 530b, 540b executed within the second processor 175b. Thereby, resources can be efficiently managed in the plurality of signal processing devices 170 for the plurality of displays within the vehicle 200.

[0209] On the other hand, the server virtual machine 520 may receive and process the wheel speed sensor data or position information data or camera image data or touch input data of the vehicle 200, and may transmit the wheel speed sensor data or position information data or camera image data or touch input data of the vehicle 200 to the client interfaces 532, 542 within at least one of the guest virtual machines 530, 540 within the processor 175 through the server interface 522b. Thereby, the transfer efficiency during data transfer between the plurality of virtual machines 520, 530, 540 within the signal processing device 170 can be improved.

[0210] On the other hand, the signal processing device 170 and the second signal processing device 170b may execute the same management program. Thereby, resources can be efficiently managed in the plurality of signal processing devices 170 for the plurality of displays within the vehicle 200.

[0211] On the other hand, the server virtual machine 520 may be controlled to record the wheel speed sensor data or position information data or camera image data or touch input data of the vehicle 200 in the first shared memory 508 within the signal processing device 170, and the guest virtual machine 530 within the signal processing device 170 may read the wheel speed sensor data or position information data or camera image data or touch input data of the vehicle 200 recorded in the first shared memory 508. Thereby, the transfer efficiency during data transfer between the plurality of virtual machines 520, 530 within the signal processing device 170 can be improved.

[0212] On the other hand, the server virtual machine 520 can receive and process the wheel speed sensor data, position information data, camera image data, or touch input data of the vehicle 200, and can be controlled to transmit the wheel speed sensor data, position information data, camera image data, or touch input data of the vehicle 200 to at least one of the guest virtual machines 520b, 530b, 540b in the second signal processing device 170b through the high-speed interfaces HIS and HSIb between the signal processing device 170 and the second signal processing device 170b. Thus, the transmission efficiency during data transmission between multiple signal processing devices 170 and 170b in the vehicle 200 can be improved.

[0213] On the other hand, the server virtual machine 520 can be controlled to record the wheel speed sensor data, position information data, camera image data, or touch input data of the vehicle 200 in the second shared memory 508b in the second signal processing device 170b, and at least one of the guest virtual machines 520b, 530b, 540b in the second signal processing device 170b can read the wheel speed sensor data, position information data, camera image data, or touch input data of the vehicle 200 recorded in the second shared memory 508b. Thus, the transmission efficiency during data transmission between multiple signal processing devices 170 and 170b in the vehicle 200 can be improved.

[0214] On the other hand, the server virtual machine 520 can be controlled to record the wheel speed sensor data, position information data, camera image data, or touch input data of the vehicle 200 in the first shared memory 508 in the signal processing device 170. When the first shared memory 508 in the signal processing device 170 is combined with the second shared memory 508b in the second signal processing device 170b, the guest virtual machine 530 in the signal processing device 170 can read the wheel speed sensor data, position information data, camera image data, or touch input data of the vehicle 200 through the second shared memory 508b combined with the first shared memory 508.

[0215] That is, on the other hand, the signal processing device 170 and the second signal processing device 170b can use the combined shared memory 508 to transmit or receive data. Thus, the transmission efficiency during data transmission between multiple signal processing devices 170 and 170b in the vehicle 200 can be improved.

[0216] Figure 8a and Figure 8b Shows various examples of data transmission between multiple signal processing devices related to the present invention.

[0217] First, Figure 8aAn example of a vehicle display device 100x having a plurality of signal processing devices 170x and 170bx related to the present invention is illustrated.

[0218] Referring to the drawings, high-speed Ethernet communication is performed between the plurality of signal processing devices 170x and 170bx.

[0219] On the other hand, for data communication between the plurality of signal processing devices 170x and 170bx, respective Ethernet controllers ECa and ECb are required, and a network switch NSa between the Ethernet controllers ECa and ECb is required.

[0220] On the other hand, each of the signal processing devices 170x and 170bx includes an Ethernet device driver EDa, EDb, a socket application programming interface SOa, SOb, and middleware MAb, MAb.

[0221] According to Figure 8a , since the communication function is implemented using POSIX application programming interfaces APIs, only considering the communication function itself, it has high portability between different systems.

[0222] However, in order to send and use data for a specific purpose, it is necessary to significantly modify the middleware or framework. In addition, in order to implement a specific usage scenario, it is necessary to implement a dedicated protocol at the application level.

[0223] For example, in order to transfer frame data (frame-data) generated by a service or application of the signal processing device 170x to the second signal processing device 170bx and output it on a display device connected to the second signal processing device 170bx, a matching service is additionally required, or it is necessary to significantly modify the middleware or framework that processes graphic data.

[0224] In such a case, the efficiency is reduced. According to the functional change of the service or application that generates the screen data in the signal processing device 170x, it is necessary to correspondingly change the part that receives the screen and outputs it in the second signal processing device 170bx. Therefore, there is a disadvantage of reduced portability between different systems.

[0225] Then, Figure 8b Another example of a vehicle display device 100y having a plurality of signal processing devices 170x and 170bx related to the present invention is illustrated.

[0226] Referring to the drawings, communication is performed by directly connecting between the plurality of signal processing devices 170x and 170bx using a high-speed data bus.

[0227] On the other hand, for data communication between a plurality of signal processing devices 170x and 170bx, each signal processing device 170x, 170bx includes bus drivers BDa, BDb, communication drivers PCa, PCb, application program interfaces PAa, PAb, and middleware MAb, MAb.

[0228] According to Figure 8b , in order to control peripheral devices and acquire or transfer data, an algorithm for controlling peripheral devices in a manner matching the method of transmitting and receiving data needs to be implemented. At this time, the method of transmitting data can be implemented based on the bus drivers BDa, BDb provided by the kernel.

[0229] Therefore, the control algorithm cannot be implemented only by the bus drivers BDa, BDb themselves, making it impossible to achieve communication between a plurality of signal processing devices 170x, 170bx. Thus, autonomous communication drivers PCa, PCb need to be implemented based on the bus drivers BDa, BDb.

[0230] In this case, since the communication drivers PCa, PCb operate based on a dedicated communication protocol, communication cannot be performed when the manufacturers of the signal processing device 170 and the second signal processing device 170b are different.

[0231] In addition, since communication is constituted by the dedicated communication drivers PCa, PCb, for middleware or framework or application implementation, it is necessary to be based on the dedicated communication drivers PCa, PCb, resulting in the disadvantages of significant damage to efficiency and portability.

[0232] In addition, when transmitting and receiving data for a specific function, there is a disadvantage that most of the middleware or framework needs to be modified to implement the corresponding function.

[0233] For example, if it is necessary to transfer the screen data (frame - data) generated in the service or application of the signal processing device 170x to the second signal processing device 170bx and output it on the display device connected to the second signal processing device 170bx, it is necessary to significantly modify the middleware or framework to recognize and utilize the dedicated communication drivers PCa, PCb, and the services or applications implemented on the communication drivers PCa, PCb also need to be modified. Therefore, it cannot be transplanted to other systems.

[0234] Figure 9 It is a reference diagram for data transfer between a plurality of signal processing devices related to the present invention.

[0235] Referring to the accompanying drawings, a vehicle display device 100x having a plurality of signal processing devices 170x, 170bx related to the present invention can perform high-speed Ethernet communication between the plurality of signal processing devices 170x, 170bx.

[0236] On the other hand, for data communication between the plurality of signal processing devices 170x, 170bx, each device requires an Ethernet controller ECa, ECb and a network switch NSa between the Ethernet controllers ECa, ECb.

[0237] On the other hand, each signal processing device 170x, 170bx includes an Ethernet device driver EDa, EDb, a socket application interface SOa, SOb, middleware MAa, MAb.

[0238] When the camera device 195 is connected to the second signal processing device 170bx, the camera data from the camera device 195 is output via a camera driver 1912, a camera frame 1914, a camera data processing unit 1916, a stream transmission unit 1910, a socket application interface SOb, and an Ethernet device driver EDb in the second signal processing device 170bx.

[0239] In addition, the camera data output from the second signal processing device 170bx is input to the signal processing device 170x via the second Ethernet controller ECb and the first Ethernet controller ECa.

[0240] The camera data input to the signal processing device 170x is output to the display 180 via an Ethernet device driver EDa, a socket application interface SOa, a stream reception unit 1922, a graphics frame 1926, and a display driver 1928.

[0241] On the other hand, when an input signal is received from the input device 110, the input signal can be transmitted from an input interface 1924 in the signal processing device 170x to a graphics frame 1926 or the like.

[0242] Referring to Figure 9 the transmission path of the camera data, since the data passes through a large number of internal modules etc. between the plurality of signal processing devices 170x, 170bx, there are problems such as the transmission of the camera data becoming complicated and causing delays. In addition, there is also a problem that an additional communication protocol etc. is required to transmit other data besides the camera data.

[0243] Therefore, the present invention proposes a solution capable of efficiently performing data transmission between a plurality of signal processing devices in a vehicle.

[0244] Specifically, when communication is performed using a high-speed data bus among a plurality of signal processing devices 170m and 170mb, the present invention proposes a solution for constructing a driver that emulates a peripheral device, in place of using additional Ethernet controllers ECa, ECb, etc. as shown in Figure 9 and the like. This solution has the advantage of only requiring additional devices without modifying middleware, frameworks, or system service code. In this regard, refer to Figure 10 the following figures for description.

[0245] Figure 10 FIG. is a diagram illustrating data transfer between a plurality of signal processing devices according to an embodiment of the present invention.

[0246] Referring to the accompanying drawings, a vehicle display device 100m according to an embodiment of the present invention includes a plurality of signal processing devices 170m and 170mb.

[0247] A signal processing device 170m according to an embodiment of the present invention includes an interface BDa, a virtual device driver EMDa, and a display driver 1928. The interface BDa exchanges data with a second signal processing device 170mb connected to a first device. The virtual device driver EMDa emulates to receive data from the first device. The display driver 1928 outputs image data to a vehicle display based on the data sent from the virtual device driver EMDa. Thus, data transfer between a plurality of signal processing devices 170m and 170mb in a vehicle can be efficiently performed. In addition, an addition of a communication protocol can be omitted during data transfer between a plurality of signal processing devices 170m and 170mb in a vehicle.

[0248] On the other hand, the interface BDa may include a high-speed bus driver ( Figure 12 HBBCa of ) that exchanges data through a high-speed data bus channel. For example, the high-speed bus driver HBBCa may be a PCI Express bus driver. Thus, data transfer between a plurality of signal processing devices 170m and 170mb in a vehicle can be efficiently performed.

[0249] On the other hand, a second signal processing device 170mb according to an embodiment of the present invention includes: a device driver 2012 that is wired or wirelessly connected to a first device to receive data from the first device; a device renderer DRb that performs rendering based on the data from the device driver 2012; and a second interface BDb that performs communication with the interface BDa of the signal processing device 170m.

[0250] On the other hand, interface BDa can receive data through device driver 2012, device renderer DRb, and second interface BDb within second signal processing device 170mb. Thereby, data transfer between multiple signal processing devices 170m and 170mb in the vehicle can be efficiently executed.

[0251] On the other hand, interface BDa can receive data abstracted in the kernel space. Thereby, when transferring data between multiple signal processing devices 170m and 170mb in the vehicle, data can be abstracted in the kernel space without the need to modify the data in middleware or a framework. Additionally, when transferring data between multiple signal processing devices 170m and 170mb in the vehicle, adding a communication protocol can be omitted.

[0252] On the other hand, interface BDa and virtual device driver EMDa can operate based on the kernel space. Thereby, when transferring data between multiple signal processing devices 170m and 170mb in the vehicle, data can be abstracted in the kernel space without the need to modify the data in middleware or a framework. Additionally, when transferring data between multiple signal processing devices 170m and 170mb in the vehicle, adding a communication protocol can be omitted.

[0253] On the other hand, the first device can include camera 195, lidar, radar, or a sensor device. Thereby, data from various devices can be transferred between multiple signal processing devices 170m and 170mb in the vehicle.

[0254] Camera 195 is illustrated as an example of the first device in the drawings, and thus, the description will mainly focus on camera 195.

[0255] When camera device 195 is connected to second signal processing device 170mb, camera data from camera device 195 is output after passing through camera device driver 2012, camera device renderer DRb, and second interface BDb within second signal processing device 170mb.

[0256] In addition, the camera data output from second signal processing device 170mb is input to signal processing device 170m and output to display 180 via interface BDa, virtual device driver EMDa, camera framework 2022, image processing unit 2023, graphics framework 2026, and display driver 1928.

[0257] On the other hand, when receiving an input signal from input device 110, the input signal from input interface 2024 within signal processing device 170m can be transmitted to graphics framework 2026, etc.

[0258] ComparisonFigure 9 The transmission path of the camera data of Figure 10 and the transmission path of the camera data of omit an additional communication controller outside the plurality of signal processing devices 170m and 170mb, shorten the path between the plurality of signal processing devices 170m and 170mb, and thus have the advantages of making the transmission of camera data fast and simple. In addition, when transmitting other data in addition to camera data, it is also based on a predetermined communication protocol, so there is an advantage of not requiring an additional communication protocol.

[0259] In addition, according to Figure 10 the transmission path of the camera data of , under the action of the virtual device driver EMDa, the image stream data transmitted from the second signal processing device 170mb is abstracted as a virtual camera device at the kernel level. Therefore, no additional protocol definition is required, and there is no need to modify the camera framework 2022, the image processing unit 2023, the graphics framework 2026, and the display driver 1928 of the middleware for processing the transmitted image stream at all.

[0260] On the other hand, for load distribution during data processing, the image processing processor of the camera data executed in the image processing unit 2023 can also be processed in the image processing unit 2016 within the second signal processing device 170mb instead of inside the signal processing device 170m. Thus, when designing the overall system, an opportunity to appropriately distribute the load can be provided.

[0261] Figures 11 to 22 is Figure 10 a reference diagram for the description of

[0262] Figure 11 is an example of the operation description between the signal processing device 170m and the second signal processing device 170mb.

[0263] Referring to the attached drawings, the signal processing device 170m may have or execute an interface BDa, a virtual device driver EMDa for simulating data reception, POSIX (Portable Operating System Interface) APIs PSa, and middleware Maa.

[0264] The second signal processing device 170mb may have or execute a second interface BDb, a device renderer DRb, POSIX application programming interfaces (APIs) PSb, and middleware Mab.

[0265] When a plurality of signal processing devices 170m and 170mb are connected by a high-speed data bus, data communication can be performed using the device renderer DRb of the second signal processing device 170mb and the emulated virtual device driver EMDa of the signal processing device 170m, without modifying the code of the framework or system service.

[0266] For example, if an application executed on the second signal processing device 170mb generates a graphics interface screen and outputs it to the display 180 connected to the signal processing device 170m, the second signal processing device 170mb can treat the signal processing device 170m as a graphics output device.

[0267] On the other hand, if a communication driver for emulating communication with the second signal processing device 170mb is implemented on the signal processing device 170m, it is equivalent to adding a graphics input device to the graphics framework operating on the signal processing device 170m.

[0268] This can be achieved by adding an emulated graphics input device to the configuration file, without modifying the code of the graphics framework.

[0269] On the other hand, the second signal processing device 170mb can generate code to be able to output the graphics data from the signal processing device 170m to the device connected to the second signal processing device 170mb.

[0270] In the case of the second signal processing device 170mb that needs to output graphics data to the display 180, the received data can be directly communicated with the virtual device driver EMDa in the kernel space, so there is no need to modify the code of the above-mentioned middleware or framework.

[0271] In this way, by abstracting data at the kernel level into peripheral devices adapted to the form and purpose of use of the data, it is possible to easily achieve this purpose without modifying the code of middleware, framework, service, application, etc. operating in the user space, and high system portability can be obtained. Further, there is no need to write an additional protocol for communication between the signal processing devices 170m in the code of the user space.

[0272] Figure 12 This is another example of the operation description between the signal processing device 170m and the second signal processing device 170mb.

[0273] Referring to the accompanying drawings, the signal processing device 170m may have or execute a high-speed bus driver HBB Ca, a bus buffer memory BBMa, a bus interrupt BIa, a virtual device driver EMDa emulating for receiving data, POSIX APIs PSa, and middleware Maa, which are examples of an interface BDa.

[0274] The high-speed bus driver HBB Ca, the bus buffer memory BBMa, the bus interrupt BIa, the virtual device driver EMDa, and the POSIX APIs PSa may operate or execute in the kernel space, while the middleware Maa may operate or execute in the user space.

[0275] The second signal processing device 170mb may have or execute a high-speed bus driver HBB Cb, a bus buffer memory BBMb, a bus interrupt BIb, a device renderer DRb, and a device driver DDDa that receives data from a first device PRDa which is a real physical device, which are examples of a second interface BDb.

[0276] The bus driver HBB Cb, the bus buffer memory BBMb, the bus interrupt BIb, the device renderer DRb, and the device driver DDDa may operate or execute in the kernel space.

[0277] Under the action of the emulated virtual device driver EMDa, the middleware or application or service of the signal processing device 170m assumes that a virtual peripheral device emulated by the second signal processing device 170mb is connected and executes functions.

[0278] On the other hand, the middleware Maa of the signal processing device 170m may access the emulated virtual device driver EMDa through the POSIX application interface PSa.

[0279] On the other hand, the emulated virtual device driver EMDa may exchange data with the second signal processing device 170mb based on the buffering and interruption of the high-speed data bus.

[0280] On the other hand, the physical function of the emulated device may be implemented in code form by the device renderer DRb implemented in the second signal processing device 170mb.

[0281] Thus, even when the first device PRDa which is a real physical device does not exist in the signal processing device 170mb, the virtual device can still be emulated as the signal processing device 170m.

[0282] If the signal processing device 170m uses the function of the first device PRDa, which is a real physical device connected to the second signal processing device 170mb, the device renderer DRb executes the requested function through the virtual device driver EMDa of the connected device, and transmits the result and data to the signal processing device 170m, thereby assuming that the first device PRDa is connected to the signal processing device 170m and performs actions.

[0283] On the other hand, the virtual device driver EMDa can perform register control, data buffer control, and interrupt reception. Hereinafter, with reference to Figure 13 the following figures, this will be described.

[0284] Figure 13 is Figure 12 an example of the internal block diagram of the virtual device driver EMDa and the internal block diagram of the device renderer DRb.

[0285] Referring to the accompanying drawings, the signal processing device 170m may have or execute a high-speed bus driver HBB Ca, a bus buffer memory BBMa, a bus interrupt BIa, a configuration space CFSa, and a virtual device driver EMDa.

[0286] The second signal processing device 170mb may have or execute a high-speed bus driver HBB Cb, a bus buffer memory BBMb, a bus interrupt BIb, a configuration space CFSb, and a device renderer DRb.

[0287] The virtual device driver EMDa may have or execute a part GRa1 corresponding to the configuration space CFSa, a part GRab corresponding to the bus buffer memory BBMa, and a part GRcc corresponding to the bus interrupt BIa.

[0288] The part GRa1 corresponding to the configuration space CFSa may have a register emulator 1106, a GPIO emulator 1108, a register controller 1102, and a GPIO controller 1104.

[0289] The part GRab corresponding to the bus buffer memory BBMa may have a read emulator 1106, a write emulator 1118, a read handler 1112, and a write handler 1114.

[0290] The part GRcc corresponding to the bus interrupt BIa may have an interrupt emulator 1124 and an interrupt handler 1122.

[0291] The device renderer DRb may have or execute a partial GRba corresponding to the configuration space CFSb, a partial GRbb corresponding to the bus buffer memory BBMb, a partial GRbc corresponding to the bus interrupt BIb, and the system interface 1152.

[0292] The partial GRba corresponding to the configuration space CFSb may have a register renderer 1162 and a GPIO renderer 1168.

[0293] The partial GRbb corresponding to the bus buffer memory BBMb may have a read emulator 1176, a write emulator 1174, a read data processor 1172, and a write data processor 1174.

[0294] The partial GRbc corresponding to the bus interrupt BIb may have an interrupt generator 1182.

[0295] On the other hand, in order to simulate a virtual device based on the signal processing device 170m, it is necessary to implement and operate a virtual device driver EDa of the virtual device simulated on the signal processing device 170m, and the device renderer DRb that implements the actual functions needs to be deployed on the second signal processing device 170mb actually connected to the first device.

[0296] Through this, the second signal processing device 170mb replaces the first device, and the middleware and services on the signal processing device 170m can operate on the premise of assuming the existence of the required peripheral devices.

[0297] The virtual device driver EMDa for the real peripheral device can be divided into three parts, namely, a part GRa1 that controls the registers of the peripheral device controller, a part GRab that reads or writes data generated by the peripheral device through the data buffer FIFO of the peripheral device controller, and a part GRcc that receives interrupts generated by the peripheral device controller to notify events or state changes occurring from the peripheral device.

[0298] As a part of the virtual device driver EMDa that operates on the signal processing device 170m, the part GRa1 that controls the registers of the peripheral device controller is the part that reads or sets the register values of the real first device.

[0299] In addition, this part GRa1 includes a part that performs power control and reset of the first device of the physical device based on the GPIO of the signal processing device 170m.

[0300] When the second signal processing device 170mb emulates the first device, the corresponding part transmits a control instruction to the second signal processing device 170mb, which needs to be emulated by the second signal processing device 170mb and the result is transmitted to the signal processing device 170m.

[0301] In the part GRa1 of the virtual device driver EMDa that emulates the operation of the signal processing device 170m, the operation of reading and writing the register value is emulated as transmitting a value to or reading a value from the configuration space CFSa part of the high-speed bus controller of the signal processing device 170m.

[0302] In the part GRba where the second signal processing device 170mb operates, it appropriately processes the register value transmitted from the virtual device driver EMDa that emulates the signal processing device 170m, sets the register value according to its content and execution result, and transmits the result to the signal processing device 170m. The part that appropriately processes the register value and operation content is called the register renderer 1162, and the part that appropriately processes the content of the GPIO and transmits the result is called the GPIO renderer 1168.

[0303] On the other hand, the data processed or generated by the existing first device connected to the high-speed data bus is stored in the FIFO memory area of the first device and transmitted to the signal processing device 170m through the high-speed data bus.

[0304] When the second signal processing device 170mb directly connected to the high-speed data bus emulates the first device, the emulation data is transmitted by the second signal processing device 170mb to the buffer memory of the high-speed data bus.

[0305] The virtual device driver EMDa emulates the actual device by treating the data as the FIFO of the first device.

[0306] That is, the read or write of the virtual device driver EMDa can be emulated by the read emulator 1106 or the write emulator 1118 as being close to the buffer of the high-speed data bus, and the actual data can be processed and emulated by the read data processor 1172 and the write data processor 1174 driven by the second signal processing device 170mb.

[0307] The read data processor 1172 and the write data processor 1174 can, when necessary for the simulation of the first device, drive the real first device connected to the second signal processing device 170mb through the system interface 1152 to obtain its results, or can also simulate functions through libraries or services operating in the kernel space or user space of the second signal processing device 170mb.

[0308] On the other hand, when preparing the data of the FIFO or when an event that needs to notify the signal processing device 170m occurs, the first device generates an interruption through the physically connected wire, and the signal processing device 170m determines the content of the generated interruption by reading the value of a specific register.

[0309] In addition, the virtual device driver EMDa simulates it based on the interruption or event transfer structure of the high-speed data bus.

[0310] The content of the real interruption or event can be processed by the interruption generator 1182 operating on the second signal processing device 170mb. The interruption generator 1182 communicates appropriately with the read data processor 1172, the write data processor 1174, or the library or service when necessary, generates an interruption or event that matches the functions of the peripheral devices, and transfers it.

[0311] On the other hand, the respective data from a plurality of input devices can be transmitted between a plurality of signal processing devices 170m and 170mb. Refer to Figure 14 for an explanation of this.

[0312] Figure 14 is a diagram showing the multiplexer in the signal processing device and the demultiplexer in the second signal processing device.

[0313] Referring to the attached drawings, the signal processing device 170m can have or execute a high-speed bus driver HBB Ca, a bus buffer memory BBMa, a bus interruption BIa, a configuration space CFSa, and a device multiplexer DMXa.

[0314] The device multiplexer DMXa can multiplex the respective data from a plurality of simulated devices EDa1 to EDan, and the high-speed bus driver HBB Ca in the interface BDa can transmit the multiplexed data to the second signal processing device 170mb. Thus, it is possible to transmit the data from a plurality of simulated devices EDa1 to EDan between a plurality of signal processing devices 170m and 170mb in the vehicle.

[0315] On the other hand, the device multiplexer DMXa can be included in the virtual device driver EMDa within the signal processing device 170m.

[0316] On the other hand, the device multiplexer DMXa can process data from a plurality of simulated devices EDa1 to EDan based on a priority order. Thereby, it is possible to transfer data from a plurality of devices between a plurality of signal processing devices 170m and 170mb in the vehicle.

[0317] On the other hand, the multiplexed data output from the device multiplexer DMXa can be transferred in the form of a data packet, the data packet including a header and a payload, the header including ID information of a plurality of simulated devices EDa1 to EDan, and the payload including a part of the data of each of the plurality of devices. Thereby, it is possible to transfer data from a plurality of devices EDa1 to EDan between a plurality of signal processing devices 170m and 170mb in the vehicle.

[0318] The accompanying drawings illustrate that the device multiplexer DMXa has a device mapping table 1210, a data packet scheduler 1212, a bus payload multiplexer 1214, and an interrupt identifier 1222.

[0319] The second signal processing device 170mb may have or execute a high-speed bus driver HBBCb, a bus buffer memory BBMb, a bus interrupt BIb, a configuration space CFSb, and a device demultiplexer DMXb.

[0320] The device demultiplexer DMXb can demultiplex the multiplexed data received from the signal processing device 170m and then match it with a plurality of device renderers EDb1 to EDbn.

[0321] On the other hand, the device demultiplexer DMXb can multiplex (mux) the data from each of the plurality of device renderers EDb1 to EDbn, and the second high-speed bus driver HBBCb in the interface BDb can transfer the multiplexed data to the signal processing device 170m. Thereby, it is possible to transfer data from a plurality of device renderers EDb1 to EDbn between a plurality of signal processing devices 170m and 170mb in the vehicle.

[0322] On the other hand, the device multiplexer DMXa can demultiplex the multiplexed data received from the second signal processing device 170mb.

[0323] On the other hand, the signal processing device 170m may further include a demultiplexer DMXb that demultiplexes the multiplexed data from the second signal processing device 170mb. Additionally, the display driver 1928 may output image data to the vehicle display 180 based on the data from the demultiplexer DMXb within the signal processing device 170m. Thus, it is possible to transfer data from a plurality of devices between the plurality of signal processing devices 170m and 170mb within the vehicle.

[0324] The accompanying drawings illustrate that the device demultiplexer DMXb includes a device mapping table 1230, a data packet scheduler 1232, a bus payload demultiplexer 1234, an interrupt scheduler 1242, and an interrupt multiplexer 1244.

[0325] A plurality of simulated devices EDa1 to EDan operating simultaneously on one signal processing device 170m may divide and transfer simulation data to the second signal processing device 170mb through one bus channel.

[0326] Therefore, even if the plurality of signal processing devices 170m and 170mb are physically connected by one high-speed data bus channel, it is still possible to simultaneously simulate the plurality of simulated devices EDa1 to EDan through this channel.

[0327] For this purpose, when data from the plurality of simulated devices EDa1 to EDan is transferred to the second signal processing device 170mb, it has a data form in the form of data packets, and each data packet may be composed of a header and a payload.

[0328] The data from the plurality of simulated devices EDa1 to EDan organized in the form of data packets may be mixed and transferred under the action of the device multiplexer DMXa, and may be distinguished individually under the action of the device demultiplexer DMXb within the second signal processing device 170mb.

[0329] The plurality of simulated devices EDa1 to EDan preferably have fixed ID information for distinction. This ID information is defined as the header of the packet data in the standardized data packet form.

[0330] The device mapping table 1210 may record and store the ID information of each of the plurality of simulated devices EDa1 to EDan and the necessary information according thereto in pairs.

[0331] The device mapping table 1210 needs to exist in both the signal processing device 170m and the second signal processing device 170mb, and preferably has the same ID information for each device.

[0332] That is, the ID information referred to by a plurality of simulation devices EDa1 to EDan and a plurality of device renderers DRb used therefor is the same, preferably a unique value within the entire system.

[0333] In order to simulate the registers and GPIOs of the plurality of simulation devices EDa1 to EDan respectively, a setting area for each of the plurality of simulation devices EDa1 to EDan is specified in the system memory area. This area can be divided by the device mapping table 1210.

[0334] If the register values of the plurality of simulation devices EDa1 to EDan are changed, then under the action of the device mapping table 1210, the values in the corresponding memory area are changed, and this change is transmitted to the connected second signal processing device 170mb under the action of the mechanism for transmitting the set area values of the high-speed data bus.

[0335] The plurality of device renderers EDb1 to EDbn can detect that the value has been changed by using the set value change mechanism of the high-speed data bus, and perform a predefined action by reading this value. At this time, the plurality of device renderers EDb1 to EDbn to be actuated can be divided by the device mapping table 1230.

[0336] In order to mix the data of the plurality of simulation devices EDa1 to EDan operating simultaneously and send it to one physical channel, it is preferable to determine the priority order according to the plurality of simulation devices EDa1 to EDan and the settings, so that processing can be carried out sequentially in a short time.

[0337] The priority order of each of the plurality of simulation devices EDa1 to EDan is recorded in the scheduler 1212, and when mixing data, the mixing order can be determined according to the priority order.

[0338] In the case of receiving a request to transmit data from a simulation device with a high priority order, the scheduler 1212 can mix the data earlier than the data with a low priority order, and thus transmit it to the connected signal processing device 170m first.

[0339] Since the data has been mixed according to the priority order during transmission, the second signal processing device 170mb on the receiving side can process the data sequentially according to the received order. That is, the priority order is only considered in the write operation, and sequential processing is performed in the read operation.

[0340] In order to transmit the dml data of the plurality of simulation devices EDa1 to Edan simultaneously through one high-speed data bus, it is necessary to mix the data in the form of a standardized data packet according to the transmission specifications of the high-speed data bus.

[0341] Continuous data can be divided into a header and a payload, and fixed ID information and necessary information of each device are stored in the header.

[0342] The second signal processing device 170mb on the receiving side can distinguish and depacketize it, and can distinguish each of the plurality of simulated devices EDa1 to EDan according to the information recorded in the header.

[0343] Various interrupts generated from the plurality of device renderers EDb1 to EDbn can have their priorities adjusted by an interrupt scheduler 1242 and be mixed so as to be transmitted to one physical high-speed data bus by an interrupt muxer (interrupt multiplexer) 1244.

[0344] The signal processing device 170m can sequentially distinguish the mixed interrupts according to the priorities and then transmit them to the plurality of simulated devices EDa1 to EDan.

[0345] Figure 15 It is a diagram showing that through an additional communication channel between a plurality of signal processing devices, the type and abstraction model of data transmitted through a high-speed data bus are flexibly changed and controlled according to the situation.

[0346] Referring to the drawings, the signal processing device 170m may have or execute a virtual device driver 1316, a second virtual device driver 1318, a service manager 1314, a system manager 1312, a high-speed bus driver HBBCa, and a virtual application 1310.

[0347] The second signal processing device 170mb may have or execute a device renderer 1336, a second device renderer 1338, a service manager 1334, a system manager 1332, and a high-speed bus driver HBBCb.

[0348] The service manager 1314 can be controlled to communicate with the second signal processing device 170mb through the high-speed bus driver HBBCa as an interface BDa and an additional communication channel. The additional communication channel at this time may be an Ethernet channel.

[0349] In the case where it is necessary to change the functions and types of the simulated virtual devices, the service manager 1314 can change the top-level management service (Supervisory Service) of the simulated virtual devices.

[0350] For this purpose, the service manager 1314 can communicate with the service manager 1332 of the second signal processing device 170mb through an additional channel.

[0351] The service manager 1314 may receive an uninstall event for a first device from the service manager 1314 or the like.

[0352] The service manager 1314 may be controlled to end the communication with the device renderer 1336 within the second signal processing device 170mb and end the communication with the high-speed bus driver HBBCa serving as the interface BDa based on the uninstall event of the first device.

[0353] On the other hand, the service manager 1314 may be controlled to perform communication with the second device renderer 1338 corresponding to the second device within the second signal processing device 170mb and the high-speed bus driver HBBCb based on the load event of the second device connected to the second signal processing device 170mb. Thereby, data communication corresponding to the device change can be achieved.

[0354] Figure 16 It is a flowchart showing the initialization between the signal processing device and the second signal processing device.

[0355] Referring to the drawings, the system service manager KSSa within the signal processing device 170m transmits system startup information to the virtual device driver EMDa (S1410).

[0356] Thereby, the virtual device driver EMDa transmits a bus enable instruction to the interface BDa (S1412).

[0357] Correspondingly, the interface BDa transmits start information to the second interface BDb (S1414).

[0358] The second interface BDb transmits a preparation instruction to the device renderer DRb, and the device renderer DRb prepares the device function (S1418).

[0359] In addition, the device renderer DRb requests system resources from the system service manager KSSb within the second signal processing device 170mb and initializes the system function (S1425).

[0360] On the other hand, after transmitting the preparation instruction, the second interface BDb transmits a reply instruction to the interface BDa. The interface BDa may perform internal processing (S1420) and transmit processing completion information to the virtual device driver EMDa (S1424).

[0361] On the other hand, the virtual device driver EMDa transmits a communication connection request to the device renderer DRb (S1430), and the device renderer DRb performs a communication connection based on the communication connection request (S1432) and transmits communication channel information to the virtual device driver EMDa (S14334).

[0362] Thereby, the virtual device driver EMDa can transmit device login information to the system service manager KSSa (S1436).

[0363] Figure 17 It is a flowchart showing an example of the operation between the signal processing device and the second signal processing device.

[0364] Referring to the drawings, the system service manager KSSa within the signal processing device 170m transmits an open device instruction to the virtual device driver EMDa (S1510).

[0365] Thereby, the virtual device driver EMDa transmits a status check instruction to the device renderer DRb (S1512).

[0366] Correspondingly, the device renderer DRb transmits status information to the virtual device driver EMDa (S1514).

[0367] In addition, the virtual device driver EMDa transmits success information or failure information to the system service manager KSSa (S1516).

[0368] Then, the system service manager KSSa transmits an operation request to the virtual device driver EMDa (S1518).

[0369] Correspondingly, the virtual device driver EMDa transmits an operation instruction to the device renderer DRb (S1520).

[0370] The device renderer DRb executes a function emulator based on the operation instruction (S1522) and processes data (S1524).

[0371] In addition, the device renderer DRb transmits data to the second interface BDb (S1528), and the second interface BDb transmits data to the interface BDa (S1530).

[0372] The interface BDa transmits an interrupt to the system service manager KSSa (S1532), and the system service manager KSSa transmits a read instruction to the virtual device driver EMDa (S1534).

[0373] Accordingly, the virtual device driver EMDa performs a read from the buffer (S1536), the interface BDa transmits the read completion information to the virtual device driver EMDa (S1538), and the virtual device driver EMDa sends the read-completed data to the system service manager KSSa (S1540).

[0374] Accordingly, the signal processing device 170m can receive data from the second signal processing device 170mb connected to the first device and process it.

[0375] Figure 18 It is a flowchart showing another example of the operation between the signal processing device and the second signal processing device.

[0376] Referring to the drawings, the system service manager KSSa in the signal processing device 170m transmits a data write instruction to the virtual device driver EMDa (S1610).

[0377] Accordingly, the virtual device driver EMDa records data through the interface BDa (S1612).

[0378] In addition, the interface BDa transmits data to the second interface BDb (S1614).

[0379] The second interface BDb transmits an interrupt to the system service manager KSSb, and the system service manager KSSb reads the interrupt from the device renderer DRb (S1618).

[0380] In addition, the device renderer DRb performs a read from the second interface BDb (S1526) and transmits the second interface BDb data to the device renderer DRb (S1624).

[0381] The device renderer DRb executes the function emulator (S1626) and processes the data (S1628).

[0382] In addition, the device renderer DRb generates an event (S16430) and transmits the event to the second interface BDb (S1632).

[0383] The second interface BDb transmits the event to the interface BDa (S1634).

[0384] The interface BDa transmits an interrupt to the system service manager KSSa, and the system service manager KSSa transmits a read instruction to the virtual device driver EMDa (S1638).

[0385] Accordingly, the virtual device driver EMDa performs a read from the buffer (S1640), the interface BDa transmits the read completion information to the virtual device driver EMDa (S1642), the virtual device driver EMDa processes the read completion event (S1644) and sends it to the system service manager KSSa (S1646).

[0386] Accordingly, the signal processing device 170m can receive an event from the second signal processing device 170mb connected to the first device and process it.

[0387] Figure 19 It is a flowchart showing the end of communication between the signal processing device and the second signal processing device.

[0388] Referring to the drawings, the system service manager KSSa within the signal processing device 170m transmits an equipment end instruction to the virtual device driver EMDa (S1710).

[0389] Accordingly, the virtual device driver EMDa transmits a communication channel end instruction to the device renderer DRb (S1712).

[0390] Accordingly, the device renderer DRb ends the operation of the renderer (S1714) and returns resources to the system service manager KSSb (S1716).

[0391] The device renderer DRb transmits end completion information to the virtual device driver EMDa (S1718), the virtual device driver EMDa processes the end completion information (S1720), and transmits bus end information to the interface BDa (S1722).

[0392] Accordingly, the interface BDa transmits an equipment removal instruction to the second interface BDb (S1724).

[0393] The second interface BDb performs equipment removal (S1726) and transmits removal completion information to the interface BDa (S1728).

[0394] Accordingly, the interface BDa transmits removal completion information to the virtual device driver EMDa (S1730), and the virtual device driver EMDa returns resources (S1732).

[0395] In addition, the virtual device driver EMDa transmits completion information to the system service manager KSSa (S1734).

[0396] Figure 20 It is an example of an internal block diagram of the vehicle display device 100mb according to another embodiment of the present invention.

[0397] Referring to the accompanying drawings, a signal processing device 170n according to another embodiment of the present invention includes an interface IFa, a virtual device driver 1820, a graphics driver 1816, and a graphics renderer 1822. The interface IFa exchanges data with a second signal processing device 170nb connected to a camera device 195. The virtual device driver 1820 performs emulation to receive data from the camera device 195. The graphics driver 1816 outputs image data to a vehicle display based on the data from the virtual device driver 1820. The graphics renderer 1822 renders the data of the display 180.

[0398] The interface IFa transmits the data from the graphics renderer 1822 to the second signal processing device 170nb. Thus, data transmission between a plurality of signal processing devices 170n, 170nb in the vehicle can be efficiently performed. In addition, when transmitting data between a plurality of signal processing devices 170n, 170nb in the vehicle, the addition of a communication protocol can be omitted.

[0399] On the other hand, the signal processing device 170n may further include an input device renderer 1824 that renders the data from the input device 110.

[0400] The interface IFa may also transmit the data from the input device renderer 1824 to the second signal processing device 170nb.

[0401] In particular, since the data of the input device renderer 1824 is transmitted to the second signal processing device 170nb through the interface IFa, and the user input data connected to the first signal processing device 170n is transmitted to the second signal processing device 170nb, the second signal processing device 170nb without a user input device can also receive user input.

[0402] Thus, data from various devices can be transmitted between a plurality of signal processing devices 170n, 170nb in the vehicle.

[0403] On the other hand, the signal processing device 170n may further include an application 1810, a camera interface 1812, a graphics framework 1814, and an input device driver 1818 that process the input signals from the input device 110.

[0404] On the other hand, the signal processing device 170n may further include an audio output renderer 1826 that renders the data from the audio output device 185a and an audio input renderer 1828 that renders the data from the audio input device 185b.

[0405] At this time, the interface IFa can transmit data from the audio output renderer 1826 or the audio input renderer 1828 to the second signal processing device 170nb. Thus, it is possible to transmit data from various devices between a plurality of signal processing devices 170n, 170nb in the vehicle.

[0406] On the other hand, the signal processing device 170n may further include an audio framework 1840, an audio output driver 1832, an audio input driver 1834, a file system manager 1836, and a data recorder 1842.

[0407] On the other hand, the signal processing device 170n may further include an emulated storage driver 1830 that emulates to receive data from a storage device SSD connected to the second signal processing device 170nb. Thus, it is possible to transmit data from various devices between a plurality of signal processing devices 170n, 170nb in the vehicle.

[0408] On the other hand, the second signal processing device 170nb may have a camera renderer 1866 and a second interface IFb.

[0409] On the other hand, the second signal processing device 170nb may further have a camera driver 1862, an application 1860 that processes input signals, a graphics framework 1864, an emulated graphics driver 1868, a virtual input device driver 1870, an emulated audio output driver 1872, an emulated audio input driver 1874, a storage device renderer 1876, a storage device driver 1884, an audio framework 1878, an audio player 1880, a voice processor 1882, and a file system manager 1866.

[0410] A plurality of signal processing devices 170n, 170nb are directly connected using a PCI Express (serial) bus. According to the PCI Express bus definition, one side acts as an RC and the other side acts as an EP.

[0411] On the other hand, the number of lanes can be defined according to the required bandwidth. For example, in the case where a bandwidth of 16 Gbps is required, two third-generation PCI Express (PCI Express Gen3) lanes may be required.

[0412] Within interfaces IFa and IFb, each multiplexer and demultiplexer can be implemented in the kernel space to simulate a plurality of devices based on the control code of the PCI Express Host controller (serial host controller) of each signal processing device 170n, 170nb and the PCI Express framework of the Linux kernel.

[0413] The multiplexer can bind the data generated from a plurality of devices into a PCI Express transmission data packet and transmit it externally.

[0414] After the demultiplexer separates the received PCI Express transmission data packet for each device, it generates an event to transmit to the corresponding device.

[0415] On the other hand, according to the user scenario, the user graphical interface operating on the signal processing device 170n or the user graphical interface operating on the second signal processing device 170nb can be selectively output on the display 180. Or, the two screens can be appropriately split / mixed and output simultaneously on one screen.

[0416] The user input entered using the touch screen or physical button device can be input to the signal processing device 170n. In this case, it is preferably to transfer the user input event information transmitted to the signal processing device 170n to the second signal processing device 170nb, and the application operating on the second signal processing device 170nb appropriately processes the user input event information to change the screen or control the action.

[0417] For this purpose, the virtual input device driver 1870 is implemented in the second signal processing device 170nb, and the input device renderer 1824 is implemented in the signal processing device 170n to be able to transfer the user input information received from the real input device 110 to the virtual input device driver 1870 of the second signal processing device 170nb.

[0418] The camera device 195 is connected to the second signal processing device 170nb.

[0419] In order to process the image stream data input from the camera device 195 in the signal processing device 170n, it is necessary to simulate the camera device 195 in the signal processing device 170n.

[0420] For this purpose, the simulated camera driver 1820 is implemented in the signal processing device 170n, and receives the image stream data from the camera renderer 1866 implemented in the second signal processing device 170nb.

[0421] The camera renderer 1866 of the second signal processing device 170nb can cooperate with the camera device 195 driver to obtain an image stream and transfer it to the PCI Express bus so as to be able to transfer it to the signal processing device 170n.

[0422] The audio output device 185a is connected to the signal processing device 170n.

[0423] In order to play the audio output stream generated by the application of the second signal processing device 170nb by the audio output device 185a connected to the signal processing device 170n, it is necessary to implement an emulated audio output driver 1872 in the second signal processing device 170nb.

[0424] The audio data output from the emulated audio output driver 1872 is transferred to the signal processing device 170n through the PCI Express bus, and the audio output renderer 1826 receives this audio data. The audio output renderer 1826 uses the function of the emulated audio output driver 1872 to transfer the playback stream to the real audio output device 185a and play the audio.

[0425] The audio input device 185b is connected to the signal processing device 170n.

[0426] When the application operating in the second signal processing device 170nb requires audio input, it is necessary to implement an emulated audio input driver 1874 in the second signal processing device 170nb.

[0427] The audio framework 1878 of the second signal processing device 170nb emulates the imaging through the emulated audio input driver 1874 as if there is a real audio input device 185b.

[0428] The voice stream input from the audio input device 185b connected to the signal processing device 170n is received by the audio input renderer 1828 implemented in the signal processing device 170n, and the audio input renderer 1828 transfers this voice stream to the emulated audio input driver 1874 of the second signal processing device 170nb.

[0429] In addition, the application of the second signal processing device 170nb processes and controls the voice stream through the audio framework 1878 of the second signal processing device 170nb.

[0430] The storage device SSD is connected to the second signal processing device 170nb.

[0431] In order for the data storage program of the signal processing device 170n to directly store data in this device, it is necessary to emulate as if there is a storage device in the signal processing device 170n.

[0432] To this end, the file system manager 1836 of the signal processing device 170n emulates a storage drive 1830 through simulation so that it is like there is a storage device. The data storage program of the signal processing device 170n reads and writes file objects based on the standard application programming interface provided by the file system manager 1836.

[0433] The control instructions and data transferred from the file system manager 1836 of the signal processing device 170n are transferred to the second signal processing device 170nb through the emulated storage drive 1830. The transferred control instructions and data are transferred to the storage device SSD based on the storage device renderer 1876.

[0434] Figure 21 This is an example of transferring the camera image stream received through the MIPI-CSI input to another signal processing device through a high-speed data bus.

[0435] Referring to the accompanying drawings, the signal processing device 170r in the vehicle display device 100mc may have or execute a kernel 2105, a virtual device driver 2110, a high-speed bus driver HBBCa, a bus buffer memory BBMa, a bus interrupt BIa, and a configuration space CFSa.

[0436] The emulated virtual device driver 2110 may have a video device controller 2112, a frame data injector 2114, and an interrupt receiver 2116.

[0437] The second signal processing device 170rb may have or execute a high-speed bus driver HBBCb, a bus buffer memory BBMb, a bus interrupt BIb, a configuration space CFSb, a device renderer 2120, a video input device 2130, and a camera serial interface CSI.

[0438] The second signal processing device 170rb has a normal CSI (Camera Serial Interface) for camera data input and uses a SERDES (Serial-Deserial) driver 193 to convert the input of a low-voltage vehicle lamp signal into CSI. The control of the SERDES driver 193 is configured through an I2C bus, and the interrupt from the SERDES driver 193 is input through GPIO.

[0439] The camera data input through CSI undergoes basic processing processes such as hue adjustment, image format conversion, and scaler (scaling) in the lower system (Image Sub-system) for image processing inside the second signal processing device 170rb, and then is placed in the system memory.

[0440] The frame control related module of the system enables the camera data located in the system memory to be accessed by the graphics output device and finally output to the display 180.

[0441] At this time, the kernel regards the camera device 195 as the video input device 2130, and the graphics and camera data processing related framework controls and processes a series of processes through the virtual device driver 2110.

[0442] In order to simulate the camera device 195 through the high-speed data bus between the plurality of signal processing devices 170r and 170rb, the device renderer 2120 of the second signal processing device 170rb may include a control instruction receiving unit 2124, a control instruction parsing and conversion unit 2122, a camera data sending unit 2126, an interrupt and event sending unit 2128, etc.

[0443] In order to simulate the camera device 195 with the signal processing device 170r, the simulated virtual device driver 2110 may include a video device controller 2112, a video device controller 2112 for placing the received camera data on the system memory, and an interrupt receiver 2116 for receiving generated events or interrupts from the device.

[0444] Since the real camera device 195 is represented and functionally implemented through the virtual device driver 2110 of the kernel of the second signal processing device 170rb, the virtual device driver 2110 for simulating image input can provide functions so that the real camera device 195 is physically connected in the kernel of the signal processing device 170r.

[0445] According to the control instruction of the image input device of the system on the signal processing device 170r, it is transmitted to the second signal processing device 170rb by using the video device controller 2112. The transfer mechanism of the control instruction data using the high-speed data bus between the signal processing devices 170r and 170rb depends on the transfer mechanism of the used high-speed data bus, and uses the set space (config space) of the high-speed data bus for transfer to be able to transfer a small amount of data efficiently.

[0446] The control instruction transmitted to the second signal processing device 170rb is appropriately converted in the second signal processing device 170rb to match the implemented camera driver. Since the camera driver implemented in the second signal processing device 170rb is highly dependent on the used camera and the manufacturer (vendor, supplier) of the second signal processing device 170rb, the control instruction analysis and conversion unit can minimize the change items of the device renderer 2120 by absorbing such change items.

[0447] The instructions appropriately processed by the controlled instruction analysis and conversion unit are transmitted to the video input device driver in the standard control instruction format (POSIX application interface) of the kernel and are used according to the content for the SERDES control via I2C or the setting and control of the Image Sub-system.

[0448] As described above, the camera data transmitted from the camera device 195 is transmitted to the system via the low-voltage vehicle lamp signal, converted into the CSI form via SERDES, and then transmitted to the second signal processing device 170rb.

[0449] For preprocessing, the transmitted camera data is transmitted to the ISP inside the second signal processing device 170rb, and the processed camera data is placed in the buffer memory area managed by the virtual device driver 2110.

[0450] If the camera data is ready, a callback notification is initiated to the module that opens the virtual device driver 2110, and the device renderer 2120 prepares to send to the signal processing device 170r.

[0451] The device renderer 2120 accesses the data buffer memory and transmits the camera data to the signal processing device 170r via the high-speed data bus.

[0452] The received camera data is located in a specific memory area by using the virtual device driver 2110, and the system module that opens the virtual device driver 2110 is notified of the reception.

[0453] After the error or status of the image stream of the continuous camera data transmitted to the system via the low-voltage vehicle lamp signal is detected by SERDES, it is transmitted to the signal processing device 170r via the GPIO connected to SERDES.

[0454] If an interrupt occurs via GPIO, the events that need to be processed when an interrupt occurs via the ISR (Interrupt Service Routine) are executed, and the details of the interrupt or event can be confirmed via I2C.

[0455] The interrupts or events processed by the second signal processing device 170rb can be transmitted to the signal processing device 170r via the device renderer 2120.

[0456] If an interrupt occurrence is detected by using the second signal processing device 170rb and its details are confirmed, the device renderer 2120 can detect the content by using the basic functions provided by the kernel. The detected content can be transmitted to the signal processing device 170r via the device renderer 2120.

[0457] At this time, an interruption or event transfer scheme between the signal processing devices 170r and 170rb is used.

[0458] The interruptions or events received by the virtual device driver 2110 of the signal processing device 170r can be transferred through the kernel to the services or frameworks that use the virtual device driver 2110.

[0459] Figure 22 This is an example of transferring the camera image input through Ethernet to other signal processing devices via the high-speed data bus.

[0460] Referring to the attached drawings, the signal processing device 170s within the vehicle display device 100md may have or execute a virtual device driver 2110, a high-speed bus driver HBBCa, a bus buffer memory BBMa, a bus interruption BIa, and a configuration space CFSa.

[0461] The emulated virtual device driver 2110 may have a video device controller 2112, a frame data injector 2114, and an interrupt receiver 2116.

[0462] The second signal processing device 170sb may have or execute a high-speed bus driver HBBCb, a bus buffer memory BBMb, a bus interruption BIb, a configuration space CFSb, a device renderer 2220, a kernel 2215, a network interface controller (NIC) 2240, a camera input service 2230, a kernel 2239, and an interface service 2225.

[0463] Although the camera device 195 transfers images to the central processing system through a low-voltage vehicle lamp signal which is a type of serial bus, it can also transfer camera data in the form of packets via Ethernet as shown according to the type.

[0464] In this case, the camera data transferred from the camera or a dedicated ECU that processes a part of the camera data in the middle is transferred to the central processing system via Ethernet, the data is packed into the form of packets, and relevant modules of the central processing system kernel are used for the processing of the packets.

[0465] In addition, the camera device 195 can perform a simple preprocessing process on the camera data collected from the image sensor. For this purpose, an Image Signal Processor (ISP) may be included inside the device.

[0466] The camera data transmitted through the Network Interface Controller (NIC) 2240 is unpacked by the Ethernet packet-related module 2238 provided by the kernel 2239 and then located in a specific memory of the system. Such a series of processes can be controlled and managed by the camera input service 2230 operating in the user space.

[0467] In order to transfer the camera data transmitted to the second signal processing device 170sb via Ethernet to the signal processing device 170s, an interface service 2225 for connecting the camera input service 2230 and the device renderer 2220 is required in the user space.

[0468] The interface service 2225 serves as an intermediary to enable the functions dependent on the signal processing device 170sb and the camera device 195 to be connected to the functions of the device renderer 2220, so that various events or interruptions occurring in the device can be transmitted to the device renderer 2220 capable of operating in the kernel space.

[0469] The control instructions transmitted to the virtual device driver 2210 can be transmitted to the device renderer 2220 through the config space of the high-speed data bus.

[0470] To control the camera device 195 or the camera input service connected to the second signal processing device 170sb, this instruction needs to transmit an event to the user space. This event is transmitted from the SIG Handler of the device renderer 2220 to the interface service 2225 operating in the user space and then transmitted to the camera input service 2230 through the communication method between the processors of the system.

[0471] The camera data transmitted via Ethernet is packet-processed as described and then placed in a specific memory of the system.

[0472] The camera input service 2230 manages this data and transmits it to the interface service 2225 that utilizes the camera input service 2230. The interface service 2225 receives notifications regarding the camera data through the communication method between the processors of the system and accesses the memory storing the camera data. The interface service 2225 notifies this situation to the device renderer 2220 and transmits the camera data to the virtual device driver 2210 through the high-speed data bus.

[0473] The camera input service 2230 can monitor the status of the camera device 195 and transfer event occurrences to the connected services. The interface service 2225 receives it, causes the device renderer 2220 to generate an interruption, and then sends the interruption to the virtual device driver 2210.

[0474] Figure 23 FIG. is an example of a signal processing system including a plurality of signal processing devices according to an embodiment of the present invention.

[0475] Referring to the drawings, a signal processing system 300 according to an embodiment of the present invention may include a plurality of signal processing devices 170, 170Z1 to 170Z4.

[0476] The plurality of signal processing devices 170, 170Z1 to 170Z4 include regional signal processing devices 170Z1 to 170Z4 each disposed in each of a plurality of regions of the vehicle 200 and a signal processing device 170 including a gateway that performs data communication based on a first communication method.

[0477] The gateway in the signal processing device 170 in the drawings may be a central gateway.

[0478] On the other hand, the plurality of regional signal processing devices Z1 to Z4, 170z1 to 170z4 may be connected to a plurality of electronic control devices.

[0479] The drawings illustrate that each of the four regional signal processing devices Z1 to Z4, 170z1 to 170z4 is connected to two electronic control devices EMC1a to EMC4b.

[0480] On the other hand, the plurality of electronic control devices EMC1a to EMC4b may receive signals from a plurality of sensor devices SNa1 to SNd6 disposed in each region, and may transmit at least a part of the received signals to the signal processing device 170 through the regional signal processing devices Z1 to Z4, 170z1 to 170z4.

[0481] On the other hand, the first area signal processing device 170Z1 among the plurality of area signal processing devices 170Z1 to 170Z4 can receive sensing signals from the plurality of sensor devices SNa1 to SNa6 arranged in the first area of the vehicle 200, and transmit the sensing signals to the signal processing device 170. The second area signal processing device 170Z2 can receive sensing signals from the plurality of sensor devices SNb1 to SNb6 arranged in the second area of the vehicle 200, and transmit the sensing signals to the signal processing device 170. The third area signal processing device 170Z3 can receive sensing signals from the plurality of sensor devices SNc1 to SNc6 arranged in the third area of the vehicle 200, and transmit the sensing signals to the signal processing device 170. The fourth area signal processing device 170Z4 can receive sensing signals from the plurality of sensor devices SNd1 to SNd6 arranged in the fourth area of the vehicle 200 and transmit the sensing signals to the signal processing device 170.

[0482] On the other hand, the first area signal processing device 170Z1 arranged in the right front inside the vehicle can perform data communication with the signal processing device 170 based on the first communication method through the wiring harness HNm1. The second area signal processing device 170Z2 arranged in the left front inside the vehicle can perform data communication with the signal processing device 170 based on the first communication method through the wiring harness HNm2. The third area signal processing device 170Z3 arranged in the left rear inside the vehicle can perform data communication with the signal processing device 170 based on the first communication method through the wiring harness HNm3. The fourth area signal processing device 170Z4 arranged in the right rear inside the vehicle can perform data communication with the signal processing device 170 based on the first communication method through the wiring harness HNm4.

[0483] Since the signal processing system 300 according to Figure 23 divides the plurality of sensor devices SNa1 to SNd6 inside the vehicle into areas or zones, each of the plurality of areas or zones is respectively provided with the signal processing devices Z1 to Z4, and wiring harnesses are arranged between the respective signal processing devices Z1 to Z4 and the signal processing device, compared with Figure 2 a, the number of wiring harnesses can be reduced and the wiring length can be shortened.

[0484] That is, the wiring harness between the plurality of sensor devices SNa1 to SNd6 and the signal processing device 170 can be simply realized. In addition, data communication can be performed efficiently and stably.

[0485] On the other hand, the plurality of sensor devices SNa1 to SNd6 may include a camera, lidar, radar, or a position sensor. Thereby, signals from various sensor devices can be efficiently and stably transmitted to the signal processing device 170.

[0486] On the other hand, each of the signal processing devices 170Z1 to 170Z4 may output vehicle control signals including door control and seat control during the running of the vehicle 200. Thereby, vehicle control can be performed using each of the signal processing devices 170Z1 to 170Z4.

[0487] On the other hand, each of the signal processing devices 170Z1 to 170Z4 may transmit signals from the sensor devices SNa1 to SNd6 disposed in respective plural regions of the vehicle 200 to the signal processing device 170. Thereby, data communication can be efficiently and stably performed.

[0488] On the other hand, Figures 10 to 22 the data communication method between the plurality of signal processing devices described in Figure 23 can be applied to the plurality of signal processing devices 170, 170Z1 to 170Z4.

[0489] For example, Figures 10 to 22 the data communication method between the plurality of signal processing devices described in

[0490] On the other hand, Figures 10 to 22 can also be applied to between the regional signal processing devices 170Z1 to 170Z4.

[0491] On the other hand, the preferred embodiments of the present invention have been described above with reference to the drawings, but the present invention is not limited to the specific embodiments described above. Within the scope not departing from the technical idea of the present invention claimed in the claims, those of ordinary skill in the technical field to which the present invention pertains can perform various modifications, and such modifications should not be understood separately without departing from the technical idea or prospect of the present invention.

Claims

1. A signal processing device, which is a signal processing device for outputting an image on a vehicle display, wherein, Comprising: An interface for exchanging data with a second signal processing device connected to a first device; A virtual device driver for emulating to receive data from the first device; And A display driver for outputting image data on a vehicle display based on data from the virtual device driver.

2. The signal processing device according to claim 1, wherein The interface includes a high-speed bus driver for exchanging the data through a high-speed data bus channel.

3. The signal processing device according to claim 1, wherein The interface receives the data through a device driver, a device renderer, and a second interface within the second signal processing device.

4. The signal processing device according to claim 1, wherein The interface receives the data abstracted in kernel space.

5. The signal processing device according to claim 1, wherein The interface and the virtual device driver operate based on kernel space.

6. The signal processing device according to claim 1, wherein The virtual device driver performs register control, data buffer control, and interrupt reception.

7. The signal processing device according to claim 1, wherein It further includes a device multiplexer for multiplexing respective data from a plurality of devices, And the interface transmits the multiplexed data to the second signal processing device.

8. The signal processing device according to claim 7, wherein The virtual device driver includes the device multiplexer.

9. The signal processing device according to claim 7, wherein The device multiplexer processes data from a plurality of the devices based on a priority order.

10. The signal processing device according to claim 7, wherein The multiplexed data output from the device multiplexer includes a header and a payload, the header includes ID information of a plurality of the devices, and the payload includes a part of respective data of a plurality of the devices.

11. The signal processing device according to claim 1, wherein It further includes a demultiplexer for demultiplexing the multiplexed data from the second signal processing device, And the display driver outputs image data on the vehicle display based on data from the demultiplexer.

12. The signal processing device according to claim 1, wherein It further includes a service manager for performing communication with the second signal processing device based on the interface and an additional communication channel, And the service manager controls to end communication with a device renderer within the second signal processing device and end communication with the interface based on an unloading event of the first device.

13. The signal processing device according to claim 12, wherein The service manager controls to perform communication with a second device renderer corresponding to the second device within the second signal processing device and communication with the interface based on a loading event of a second device connected to the second signal processing device.

14. The signal processing device according to claim 1, wherein The first device includes a camera, a lidar, a radar, or a sensor device.

15. A signal processing device, which is a signal processing device for outputting an image on a vehicle display, wherein, Comprising: An interface for exchanging data with a second signal processing device connected to the camera device; A virtual device driver for simulating to receive data from the camera device; A display driver for outputting image data on the vehicle display based on data from the virtual device driver; And A graphics renderer for rendering the data of the display; The interface transmits the data from the graphics renderer to the second signal processing device.

16. The signal processing device according to claim 15, wherein It further includes an input device renderer for rendering data from an input device, The interface also transmits the data from the input device renderer to the second signal processing device.

17. The signal processing device according to claim 15, wherein, It further includes: An audio output renderer for rendering data from an audio output device; and An audio input renderer for rendering data from an audio input device; The interface transmits the data from the audio output renderer or the data from the audio input renderer to the second signal processing device.

18. The signal processing device according to claim 15, wherein It further includes a second virtual driver for simulating to receive data from a storage device connected to the second signal processing device.

19. A vehicle display device, wherein The vehicle display device has the signal processing device according to any one of claims 1 to 18.

Images