Cabin domain controller and vehicle

Abstract

The application provides a cabin domain controller and a vehicle, which can be used for automatic driving operation vehicles, such as unmanned taxis Robotaxi, wherein the cabin domain controller comprises a deserializing chip, a system on chip (SOC) chip, a first memory and a second memory; the second memory is used for storing system files of the SOC chip; the deserializing chip is used for receiving sensor data from a vehicle-mounted sensor, converting the sensor data from a serial signal into a parallel signal and transmitting the parallel signal to the SOC chip; the SOC chip is used for decoding and packaging the sensor data, generating a data file and transmitting the data file to the first memory; and the first memory is used for storing the data file.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and more particularly to a cockpit domain controller and vehicle that can be used in autonomous driving operation vehicles, such as driverless taxis (Robotaxi). Background Technology

[0002] Vehicles have become an integral part of people's lives. With the development of artificial intelligence technology, various types of sensors are widely installed on vehicles to achieve functions such as environmental perception, driving assistance, occupant monitoring, safety warning, and intelligent interaction. These functions are realized based on the data collected by the on-board sensors.

[0003] In related technologies, video data collected by vehicle cameras and system files of the cockpit domain system are usually stored in the same memory. Frequent erasure and rewriting of video data can affect system files. This is especially true for vehicles that operate continuously, where the amount of video data generated is large, leading to frequent erasure and rewriting, which affects the safety and stability of the cockpit domain system and makes it difficult to meet the safety requirements of vehicles that operate continuously. Utility Model Content

[0004] This application provides a cockpit domain controller and a vehicle. The specific solution is as follows: One embodiment of this application proposes a cockpit domain controller, including: a deserialization chip, a system-on-a-chip (SoC) chip, a first memory, and a second memory; wherein the second memory is used to store the system files of the SoC chip; The deserialization chip is used to receive sensor data from the vehicle-mounted sensor, convert the sensor data from a serial signal to a parallel signal, and transmit it to the SOC chip. The SOC chip is used to decode and encapsulate the sensor data, generate a data file, and transmit the data file to the first memory. The first memory is used to store the data file.

[0005] Another embodiment of this application proposes a vehicle including: the cockpit domain controller proposed in the above-mentioned embodiment.

[0006] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

[0007] The accompanying drawings are provided for a better understanding of this solution and do not constitute a limitation of this application. Wherein: Figure 1 This is a schematic diagram of the structure of a cockpit domain controller provided in one embodiment of this application; Figure 2 A schematic diagram of the structure of a cockpit domain controller provided in another embodiment of this application; Figure 3 This is a schematic diagram of the structure of a vehicle provided in one embodiment of this application. Detailed Implementation

[0008] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0009] It should be noted that the acquisition, storage, use, and processing of data in this application comply with the relevant provisions of national laws and regulations and do not violate public order and good morals.

[0010] The cockpit domain controller and vehicle of embodiments of this application are described below with reference to the accompanying drawings.

[0011] Figure 1 This is a schematic diagram of the structure of a cockpit domain controller provided in one embodiment of this application.

[0012] like Figure 1 As shown, the cockpit domain controller 100 of this application embodiment includes: a deserialization chip 110, a SOC (System on Chip) chip 120, a first memory 130, a second memory 140, etc.

[0013] The deserialization chip 110 is connected to both the vehicle-mounted sensor and the SOC chip 120. The SOC chip 120 is connected to both the first memory 130 and the second memory 140. The deserialization chip 110 can be used to convert received data from serial signals to parallel signals.

[0014] Since sensor data is erased and written frequently, in order to avoid the frequent erasure and writing of sensor data from affecting the system files of the SOC chip, the first memory 130 and the second memory 140 are different memories in this application. The first memory 130 can be used to store the data collected by the vehicle sensor, and the second memory 140 can be used to store the system files of the SOC chip 120, thereby storing the sensor data and the system files of the SOC chip separately.

[0015] For example, the first memory 130 may include, but is not limited to, a USB flash drive, an SD card, etc., and this application does not limit it.

[0016] For example, the second storage device 140 may include, but is not limited to, NVMe SSDs (non-volatile memory high-speed solid-state drives), automotive OPAL SSDs, etc., and this application does not limit it in this regard. OPAL is a set of self-encrypting drive (SED) security standards developed by the Trusted Computing Group (TCG).

[0017] In some embodiments, the vehicle may include a cockpit domain controller 100, on-board sensors, etc. The deserialization chip 110 is connected to the on-board sensors in the vehicle. The sensor data collected by the on-board sensors is transmitted to the deserialization chip 110 as a serial signal. In order to improve the transmission speed, the deserialization chip 110 converts the sensor data received from the on-board sensors from the serial signal into a parallel signal and transmits it to the SOC chip 120. Then, the SOC chip 120 decodes and encapsulates the sensor data to generate a data file and transmits the data file to the first memory 130, where the first memory 130 stores the data file.

[0018] For example, vehicle sensors may include, but are not limited to, cameras and radar, and sensor data may include video data collected by cameras, data collected by radar, etc.

[0019] For example, the vehicle-mounted sensor can transmit the collected sensor data to the deserialization chip 110 via the GMSL (Gigabit Multimedia Serial Link) bus.

[0020] For example, the vehicle-mounted sensor can also transmit the sensor data of the vehicle-mounted sensor to the deserialization chip 110 through the GMSL2 (Gigabit Multimedia Serial Link 2) bus. That is, the deserialization chip 110 can receive the sensor data transmitted by the vehicle-mounted sensor through the GMSL2 bus.

[0021] Because the GMSL2 bus has high bandwidth transmission capability and supports long-distance transmission, transmitting sensor data through the GMSL2 bus can improve data transmission efficiency and storage efficiency, and has a wide range of applications.

[0022] For example, the deserialization chip 110 can be connected to the SOC chip 120 through the MIPI (Mobile Industry Processor Interface) interface, so the deserialization chip 110 can transmit sensor data to the SOC chip 120 as parallel signals through the MIPI interface.

[0023] Because the MIPI interface supports multi-channel parallel transmission, transmitting sensor data via the MIPI interface can improve data transmission efficiency. Furthermore, the MIPI interface supports multiple data formats, thus allowing for flexible adaptation to different types of sensors and application requirements.

[0024] For example, the deserialization chip 110 can also transmit sensor data to the SOC chip 120 via the MIPI CSI-2 (Camera Serial Interface 2) interface.

[0025] It should be noted that the deserialization chip 110 can also transmit sensor data to the SOC chip 120 through other parallel interfaces, and this application does not limit this.

[0026] For example, the SOC chip 120 can decode the compressed sensor data into raw data using a hardware decoder, add information such as timestamps and metadata, and then encapsulate it into a data file in a preset format.

[0027] Taking sensor data, including data collected by a camera, as an example, the SOC chip 120 can convert the compressed video stream into raw video frames through a hardware decoder, add information such as timestamps and metadata, encapsulate the raw video frames into a standard format video file, and then transmit the video file to the first memory 130 for storage.

[0028] As one application scenario, the aforementioned cockpit domain controller 100 can be applied to autonomous vehicles. The cockpit domain controller 100 can store onboard sensor data and system files of the autonomous vehicle through different memory.

[0029] In this embodiment, the cockpit domain controller uses a deserialization chip to convert serial sensor data into parallel data and transmits it to the SOC chip. The SOC chip decodes and encapsulates the data to generate a data file, which is then transmitted to a first memory for storage. A second memory is used to store the SOC chip's system files. Thus, the cockpit domain controller uses different memory locations to store sensor data and system files, separating them. By adopting an independent storage architecture, the cockpit domain controller places sensor data and system files in different memory locations, physically isolating them. This ensures that frequent erasure and rewriting of sensor data will not affect the system files, avoiding interference with system stability caused by frequent data erasure and rewriting. This improves the safety and stability of the cockpit domain system, extends the system's service life, and meets the safety requirements of vehicles, especially those operating continuously.

[0030] For vehicles operating continuously, such as driverless taxis, related technologies use USB flash drives or SD cards to store video data collected by onboard cameras. This storage method suffers from poor stability and data leakage. Furthermore, vehicle vibration, dust, high temperature, and high humidity conditions can all affect the stability of the video data stored on the disk. Additionally, USB flash drives and SD cards are not automotive-grade products, and their lifespan and reliability do not meet the requirements for long-term vehicle operation. Therefore, in some embodiments of this application, the first memory 130 may include an eMMC (Embedded MultiMedia Card) memory. Using eMMC memory to store sensor data, the eMMC memory conforms to automotive standards and can pass all DV (Design Verification) tests, including vibration durability, high / low temperature, and high humidity tests. Data storage is reliable and secure, and its space reliability and available size do not decrease with usage time. Its stability and reliability meet the requirements for long-term vehicle operation, making it suitable for driverless vehicles.

[0031] For example, the driver of the SDIO (Secure Digital Input / Output) interface of the SOC chip 120 can be modified to enable the SOC chip 120 to support eMMC memory. Thus, the SOC chip 120 can connect to the eMMC memory through the SDIO interface and transfer data files to the eMMC memory for storage through the SDIO interface.

[0032] For example, the SOC chip 120 can decode and encapsulate sensor data to generate a data file, and then transmit the data file to the eMMC memory via the SDIO interface, where the eMMC memory stores the data file.

[0033] In order to improve the efficiency of reading system files, in some embodiments of this application, the second memory 140 may include a UFS (Universal Flash Storage) memory, and the SOC chip 120 is connected to the UFS memory through a UFS interface.

[0034] For example, the SOC chip 120 can read system files from UFS memory via the UFS interface.

[0035] Because UFS memory uses a full-duplex serial interface, supports simultaneous reading and writing, has a large bandwidth, and has high random read performance, the SOC chip 120 connects to the UFS memory through the UFS interface. By storing system files through the UFS memory, the read and write speed of system files can be improved, enabling fast system startup and improving system smoothness.

[0036] In one embodiment of this application, Figure 1 In this process, the vehicle-mounted sensor can transmit its sensor data as a serial signal to the deserialization chip 110 via the GMSL2 bus. In other words, the deserialization chip 110 can receive the sensor data transmitted by the vehicle-mounted sensor via the GMSL2 (Gigabit Multimedia Serial Link 2) bus.

[0037] Because the GMSL2 bus has high bandwidth transmission capability and supports long-distance transmission, transmitting sensor data through the GMSL2 bus can improve data transmission efficiency and storage efficiency, and has a wide range of applications.

[0038] Figure 2 A schematic diagram of the structure of a cockpit domain controller provided in another embodiment of this application.

[0039] like Figure 2 As shown, the SOC chip 120 may include a coprocessor 121.

[0040] For example, an image recognition algorithm is loaded in the coprocessor 121, which can be used to recognize and process video data in the sensor data.

[0041] For example, the number of coprocessors 121 can be one or more, and this application does not limit this.

[0042] For example, such as Figure 2 As shown, the SOC chip 120 may also include a CPU (Central Processing Unit) 122, which can act as the main processor and the coprocessor 121 can assist the CPU 122 in processing image recognition tasks.

[0043] As an example, the coprocessor 121 may include a CDSP (Compute Digital Signal Processor) to load image recognition algorithms.

[0044] It should be noted that the coprocessor 121 including CDSP is only an example, and may also include other types of processors, such as neural network processors, graphics processors, etc., which are not limited in this application.

[0045] Since autonomous vehicles have a high probability of leaving objects behind after passengers get off, the entire system needs to be able to identify whether there are any physical objects left behind in a timely manner, and also needs to distinguish between garbage and useful items. Therefore, the image recognition algorithm in the coprocessor 121 can identify and process the video data in the sensor data, which can process the data in parallel, has a fast calculation speed, can reduce the consumption of the system CPU, and make the entire system operate efficiently.

[0046] In some embodiments of this application, such as Figure 2 As shown, the cockpit domain controller 100 may also include a third memory 150.

[0047] The third memory 150 can be used to store the program instructions and temporary data currently being executed by the SOC chip 120.

[0048] For example, the SOC chip 120 can be connected to the third memory 150 through the EBI (External Bus Interface) interface, and the SOC chip 120 can store the currently executing program instructions and temporary data in the third memory 150 through the EBI interface.

[0049] As an example, the third memory may include LPDDR (Low Power Double Data Rate SDRAM), with the SOC chip 120 connected to the LPDDR via an EBI interface. The LPDDR is used to store the program instructions and temporary data currently being executed by the SOC chip 120.

[0050] Therefore, the EBI interface of the SOC chip allows the system to exchange data with external memory, and the EBI interface supports parallel data transmission, thereby improving data transmission speed.

[0051] It should be noted that the third memory is LPDDR only as an example. The third memory can also be other types of memory, such as DDR, etc. This application does not limit it.

[0052] In this embodiment, storing the program instructions and temporary data currently being executed by the SOC chip in the third memory of the cockpit domain controller can improve the program loading speed and execution efficiency, and enable multi-task concurrent processing.

[0053] In one embodiment of this application, the SOC chip 120 can read sensor data from the first memory 130 and upload it to the cloud server via the RGMII (Reduced Gigabit Media Independent Interface) interface.

[0054] For example, such as Figure 2 As shown, the SOC chip 120 can transmit the read sensor data to the Ethernet of the cockpit domain controller 100, then to the vehicle's gateway via the Ethernet in the cockpit domain controller 100, then to the in-vehicle intelligent terminal via the gateway, and finally to the cloud server via the in-vehicle intelligent terminal. The vehicle intelligent terminal is an intelligent terminal device that integrates vehicle network and wireless communication technologies.

[0055] Therefore, uploading data collected by vehicle sensors to a cloud server via the RGMII interface of the SOC chip can improve data transmission rate.

[0056] Based on the above embodiments, this application also proposes a vehicle. Figure 3 This is a schematic diagram of the structure of a vehicle provided in one embodiment of this application.

[0057] like Figure 3 As shown, the vehicle includes a cockpit domain controller 100, on-board sensors 200, etc., and the structure of the cockpit domain controller 100 is as described above. Figure 1 or Figure 2 As shown.

[0058] The sensor data collected by the vehicle sensor 200 can be converted into parallel signals by the deserialization chip in the cockpit domain controller 100 and transmitted to the SOC chip in the cockpit domain controller 100. The SOC chip decodes and encapsulates the sensor data to generate a data file and transmits it to the first memory in the cockpit domain controller 100. The first memory stores the data file, and the second memory in the cockpit domain controller 100 stores the system file of the SOC chip.

[0059] It should be noted that the explanation of the structure of the cockpit domain controller 100 can be found in the above embodiments, and therefore will not be repeated here.

[0060] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to a specific feature, structure, material, or characteristic described in connection with that embodiment or example, which is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example.

[0061] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0062] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the utility models disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the appended claims.

[0063] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A cockpit domain controller, comprising: The system comprises a deserialization chip, a system-on-a-chip (SoC) chip, a first memory, and a second memory; wherein the second memory is used to store the system files of the SoC chip. The deserialization chip is used to receive sensor data from the vehicle-mounted sensor, convert the sensor data from a serial signal to a parallel signal, and transmit it to the SOC chip. The SOC chip is used to decode and encapsulate the sensor data, generate a data file, and transmit the data file to the first memory. The first memory is used to store the data file.

2. The cockpit domain controller according to claim 1, wherein, The first memory includes an embedded multimedia card eMMC memory, and the SOC chip is connected to the eMMC memory via a Secure Digital Input / Output (SDIO) interface.

3. The cockpit domain controller according to claim 1, wherein, The second memory includes a general-purpose flash memory (UFS), and the SOC chip is connected to the UFS memory via a UFS interface.

4. The cockpit domain controller according to claim 1, wherein, The sensor data includes video data, and the SOC chip includes a coprocessor loaded with an image recognition algorithm, which is used to recognize and process the video data.

5. The cockpit domain controller according to claim 1, wherein, The SOC chip reads the sensor data from the first memory and uploads it to the cloud server via the simplified Gigabit Media Independent Interface (RGMII).

6. The cockpit domain controller according to claim 1, wherein, The deserialization chip transmits the sensor data to the SOC chip as a parallel signal through the Mobile Industrial Processor Interface (MIPI).

7. The cockpit domain controller according to claim 1, wherein, The deserialization chip is used to receive the sensor data transmitted by the vehicle-mounted sensor via the GMSL2 bus.

8. The cockpit domain controller according to claim 1, wherein, The cockpit domain controller also includes a third memory for storing program instructions and temporary data currently being executed by the SOC chip.

9. The cockpit domain controller according to claim 8, wherein, The SOC chip is connected to the third memory via the external bus interface EBI interface.

10. A vehicle comprising: The cockpit domain controller as described in any one of claims 1-9.

Images