Cabin area control system and vehicle

Abstract

The utility model relates to a cockpit domain control system and a vehicle. The cockpit domain control system comprises at least two domain controllers; each domain controller comprises a system-on-chip and a control chip, and the system-on-chip and the control chip in the same domain controller are connected; all the system-on-chips in different domain controllers are connected with one another; and the control chips in the different domain controllers are connected with one another. According to the method, a hardware structure does not need to be redesigned, the computing power requirements of different vehicle types can be met by adjusting the number of the domain controllers, and the research and development time and cost can be reduced.

Description

Technical Field

[0001] The present disclosure relates to the technical field of vehicles, and in particular, to a cockpit domain control system and a vehicle. Background Art

[0002] With the rapid development of vehicle technology, the functions on vehicles are also developing towards integration and intelligence. The core controller of an intelligent cockpit is the in-vehicle infotainment host, and its performance and scalability directly affect the usage scenarios and application spaces of the intelligent cockpit.

[0003] Moreover, the intelligent levels of different vehicle models are different, and the requirements for the capabilities of the new in-vehicle entertainment host are also different. For example, high-end vehicles have more screen requirements and may need to light up the head-up display, instrument panel, center console screen, co-pilot screen, rear overhead screen, streaming media rearview mirror, other convenient control screens, etc. simultaneously. Therefore, the requirements for the capabilities of the cockpit in-vehicle infotainment host are relatively high, and a single chip may not be able to meet the computing power requirements of this host. However, there are also some vehicle models with relatively low requirements for the capabilities of the new cockpit in-vehicle entertainment host, and a single chip can meet their computing power requirements. Therefore, in the prior art, for vehicles with relatively high computing power requirements, usually two chips are set in the host, while for vehicles with relatively low computing power requirements, one chip is set in the host. This results in the hosts of different vehicle models being composed of different hardware structures and software programs, and the hardware structure and software program need to be reset. The same set of hardware structure cannot be compatible with the resource requirements of different vehicle models, leading to a relatively high overall cost and a long R & D time. Summary of the Utility Model

[0004] To solve the above technical problems, the present disclosure provides a cockpit domain control system and a vehicle.

[0005] In a first aspect, the present disclosure provides a cockpit domain control system, including: at least two domain controllers;

[0006] The domain controller includes a system-on-chip and a control chip, and the system-on-chip and the control chip in the same domain controller are connected;

[0007] The system-on-chips in different domain controllers are connected to each other; the control chips in different domain controllers are connected to each other.

[0008] In some embodiments, the system-on-chips in different domain controllers are connected through an audio bus and / or Ethernet; the control chips in different domain controllers are connected through a CAN bus.

[0009] In some embodiments, the domain controller includes an Ethernet gateway and an Ethernet interface chip; the system-on-chip and the Ethernet gateway in the same domain controller are both connected to the Ethernet interface chip.

[0010] In some embodiments, the control chip in the same domain controller is connected to the Ethernet gateway.

[0011] In some embodiments, it further includes: an antenna module, a driving module, and an on-vehicle diagnostic module;

[0012] At least a partial number of the system-on-chips are connected to the antenna module, the driving module, and the on-vehicle diagnostic module.

[0013] In some embodiments, different domain controllers are connected to cockpit devices in different regions of the cockpit.

[0014] In some embodiments, the domain controller includes a first domain controller and a second domain controller;

[0015] The first domain controller is connected to cockpit devices in the front row of the cockpit; the second domain controller is connected to cockpit devices in the rear row of the cockpit.

[0016] In some embodiments, it further includes: the cockpit devices in the front row of the cockpit include a first image acquisition device and an alarm prompt device, and the cockpit devices in the rear row of the cockpit include a second image acquisition device and a rear-row cockpit display device;

[0017] The first domain controller is configured to control the alarm prompt device based on driver information collected by the first image acquisition device; the second domain controller is configured to control the rear-row cockpit display device based on passenger information collected by the second image acquisition device.

[0018] In some embodiments, it further includes: an image acquisition module, a sound processing module, a head-up display module, and an intelligent monitoring module; the domain controller includes a third domain controller and a fourth domain controller;

[0019] The third domain controller is respectively connected to the image acquisition module and the sound processing module; the fourth domain controller is respectively connected to the head-up display module and the intelligent monitoring module.

[0020] In a second aspect, the present disclosure further provides a vehicle, including the cockpit domain control system provided in any one of the first aspect.

[0021] The technical solution provided by the present disclosure has the following advantages compared with the prior art:

[0022] The cockpit domain control system provided by the present disclosure includes: at least two domain controllers; each domain controller includes a system-on-chip and a control chip, and the system-on-chip and the control chip in the same domain controller are connected; the system-on-chips in different domain controllers are connected to each other; and the control chips in different domain controllers are connected to each other. Thus, the present disclosure provides at least two domain controllers. Each domain controller includes a system-on-chip and a control chip, and each domain controller has an independent structure and the same hardware structure. When the computing power requirement is high, there is no need to redesign the hardware structure. By adjusting the number of domain controllers, it is possible to be compatible with the computing power requirements of different vehicle models, and the R & D time and cost can also be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings are incorporated herein and form a part of this specification, showing embodiments consistent with the present disclosure and, together with the specification, are used to explain the principles of the present disclosure.

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or in the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0025] Figure 1 It is a schematic structural diagram of a cockpit domain control system provided by an embodiment of the present disclosure;

[0026] Figure 2 It is a schematic structural diagram of another cockpit domain control system provided by an embodiment of the present disclosure;

[0027] Figure 3 It is a schematic structural diagram of another cockpit domain control system provided by an embodiment of the present disclosure;

[0028] Figure 4 It is a schematic structural diagram of another cockpit domain control system provided by an embodiment of the present disclosure;

[0029] Figure 5 It is a schematic structural diagram of another cockpit domain control system provided by an embodiment of the present disclosure;

[0030] Figure 6 It is a schematic structural diagram of another cockpit domain control system provided by an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0031] In order to be able to more clearly understand the above objects, features, and advantages of the present disclosure, the following will further describe the solutions of the present disclosure. It should be noted that, without conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other.

[0032] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced in other ways different from those described herein; obviously, the embodiments in the specification are only a part of the embodiments of the present disclosure, rather than all of the embodiments.

[0033] An embodiment of the present disclosure provides a cockpit domain control system. Figure 1 For a cockpit domain control system provided by an embodiment of the present disclosure, refer to Figure 1 , the cockpit domain control system includes: at least two domain controllers 1.

[0034] The domain controller 1 includes a system-on-chip 10 and a control chip 20. The system-on-chip 10 and the control chip 20 in the same domain controller 1 are connected; the system-on-chips 10 in different domain controllers 1 are connected; the control chips 20 in different domain controllers 1 are connected.

[0035] Exemplarily, Figure 1 two domain controllers 1 are provided. Each domain controller 1 includes a system-on-chip 10 and a control chip 20. The system-on-chip 10 may refer to an SOC (System on Chip), which is an integrated circuit that integrates a computing processor and other electronic systems into a single chip and can process digital signals, analog signals, mixed signals, and even radio frequency signals, etc. The control chip 20 may refer to an MCU (Microcontroller Unit), which integrates basic functions such as a processor core, memory, peripheral interfaces, and timers. For example, select the 8295 chip. In the cockpit domain control system, the system-on-chip 10 mainly undertakes most of the computing power and processes big data, such as the processing of unstructured data such as images, videos, and audios. The control chip 20 is used to wake up the CAN / LIN bus, perform power management and status monitoring on the system-on-chip 10, and the information interaction between the cockpit domain control system and the body, power, and other domain control chips is also completed by the control chip 20.

[0036] Each domain controller 1 has the same independent structure and can also operate independently. At the same time, for models with high computing power requirements for the cockpit domain control system, the embodiments of the present disclosure provide at least two domain controllers 1 to jointly provide computing power for the cockpit domain control system. Among them, the system-level chip 10 and the control chip 20 in the same domain controller 1 are connected, and the system-level chip 10 and the control chip 20 in the same domain controller 1 can perform information interaction and data transmission; the system-level chips 10 in different domain controllers 1 are connected, and each system-level chip can also perform information interaction to complete some data transmission and processing; the control chips 20 in different domain controllers 1 are connected, and each control chip 20 can also perform information interaction and data transmission. This greatly increases the computing power of the cockpit domain control system, and there is no need to re-develop and design the hardware. The same type of domain controller 1 can be used, and the number of domain controllers can be adjusted according to the computing power requirements. The hardware structures are the same, and the same set of software programs can also be applied. In the actual application process, the functions executed by each domain controller 1 can also be divided, but they can all be written into the same set of software programs.

[0037] The embodiments of the present disclosure provide at least two domain controllers. Each domain controller includes a system-level chip and a control chip. Each domain controller has an independent structure and the same hardware structure. When the computing power requirement is high, there is no need to re-design the hardware structure. By adjusting the number of domain controllers, the computing power requirements of different models can be compatible, and the R & D time and cost can also be reduced.

[0038] In some embodiments, Figure 2 is a schematic structural diagram of another cockpit domain control system provided by the embodiments of the present disclosure. Refer to Figure 2 , the system-level chips 10 in different domain controllers 1 are connected through an audio bus A2B and / or an Ethernet ETH; the control chips 20 in different domain controllers 1 are connected through a CAN bus.

[0039] Exemplarily, Figure 2Still taking two domain controllers 1 as an example, the system-on-chips 10 in different domain controllers 1 are connected through the Audio Bus A2B. Two Audio Buses A2B are shown in the figure, namely A2B1 and A2B2 respectively. The Audio Bus A2B is mainly used to transmit audio data. After the system-on-chips 10 in different domain controllers 1 are connected, they can interact audio data. Among them, the same domain controller 1 also includes an A2B transceiver (not shown in the figure). The system-on-chips 10 within the same domain controller 1 are connected to the A2B transceiver, and the corresponding A2B transceivers between different domain controllers 1 are connected, so that the system-on-chips 10 in different domain controllers 1 are connected through the Audio Bus A2B. For example, the cockpit domain control system further includes a power amplifier module 101, an in-vehicle microphone 102, and an out-of-vehicle microphone 103. The in-vehicle microphone 102 is connected to the power amplifier module 101, and the power amplifier module 101 is connected to the Audio Bus A2B1. And the different system-on-chips 10 are also connected through A2B1. Therefore, both of the two system-on-chips 10 can receive the audio information transmitted by the in-vehicle microphone 102, and can also perform data interaction with the power amplifier module 101 or the out-of-vehicle microphone 103. And two connection methods for the out-of-vehicle microphone 103 are provided. One is also connected to each system-on-chip 10 through the Audio Bus A2B1, and the other is connected to each system-on-chip 10 through the Audio Bus A2B2. The embodiments of the present disclosure do not limit this, and it is only an optional implementation manner. Both of the two system-on-chips can process audio information, greatly improving the computing power of the cockpit domain control system.

[0040] The system-on-chips 10 in different domain controllers 1 are connected through the Ethernet ETH. Each system-on-chip 10 can interact and obtain body information or other data information, and interact with other domain control systems of the vehicle. For example, if the system-on-chip 10 of a certain domain controller 1 obtains image information but does not have enough computing power for calculation, it can transmit the image information to the system-on-chip 10 of another domain controller 1 connected to it through the Ethernet ETH for calculation and processing.

[0041] In some optional implementation manners, the system-on-chips 10 in different domain controllers 1 are connected through the Audio Bus A2B and the Ethernet ETH. Therefore, the types of data that each system-on-chip 10 can interact are more abundant, and the computing capabilities of different domain controllers 1 can be better utilized.

[0042] Each control chip 20 in different domain controllers 1 is connected through a CAN bus. The CAN bus has strong reliability, can support communication between multiple nodes, and can provide high-speed and real-time data transmission, enabling each control chip 20 to communicate with each other and coordinate work to achieve efficient control and monitoring of the vehicle. In some other embodiments, a CAN-FD bus can also be selected. There are differences in the transmission rate, data length, frame format, and ID length between the CAN-FD bus and the CAN bus, and specific selection can be made according to actual needs. The embodiments of the present disclosure do not limit this.

[0043] In some embodiments, continuing to refer to Figure 2 , the domain controller 1 includes an Ethernet gateway 30 and an Ethernet interface chip 40; the system-on-chip 10 and the Ethernet gateway 30 in the same domain controller 1 are both connected to the Ethernet interface chip 40.

[0044] Exemplarily, the domain controller 1 includes an Ethernet gateway 30 and an Ethernet interface chip 40 for realizing the connection of the system-on-chips 10 in different domain controllers 1. For example, the system-on-chip 10 in the domain controller 1 is connected to the Ethernet gateway 30, and the Ethernet gateway 30 is connected to the Ethernet interface chip 40. An Ethernet interface chip 40 directly connected to the system-on-chip 10 is also provided in the domain controller 1. Taking two domain controllers 1 in the figure as an example, if the Ethernet gateway 30 in one domain controller 1 is used, then after connecting the Ethernet gateway 30 and the Ethernet interface chip 40 in this domain controller 1, it is then connected to the Ethernet interface chip 40 directly connected to the system-on-chip 10 in another domain controller 1, so as to realize the connection of the system-on-chips 10 in different domain controllers 1 through Ethernet ETH. When there is too much data and the system-on-chip 10 of one domain controller 1 cannot process it, it can be transmitted through Ethernet ETH to the system-on-chip 10 of another domain controller 1 for processing by this system-on-chip 10. Or the system-on-chips 10 in different domain controllers 1 receive different data information, process their respective corresponding data parts, and perform interactive integration after processing, thereby improving vehicle intelligence.

[0045] In some embodiments, continuing to refer to Figure 2 , the control chip 20 in the same domain controller 1 is connected to the Ethernet gateway 30.

[0046] Exemplarily, the control chip 20 in the same domain controller 1 is also connected to the Ethernet gateway 30, and data interaction can also be performed between the Ethernet gateway 30 and the control chip 20. For example, the control chip 20 and the Ethernet gateway 30 can be connected through an SPI serial peripheral interface or an SGMII gigabit Ethernet independent interface. When the Ethernet gateway 30 receives some data information required by the control chip 20, it can transmit it to the control chip 20 to achieve information interaction.

[0047] In some embodiments, continuing to refer to Figure 2 , the cockpit domain control system further includes: an antenna module 104, a driving module 105, and a vehicle diagnostic module 106.

[0048] At least a partial number of system-on-chips 10 are connected to the antenna module 104, the driving module 105, and the vehicle diagnostic module 106.

[0049] Exemplarily, the cockpit domain control system includes an antenna module 104, such as a TCAM module (in-vehicle information system connection antenna module), which is mainly applied in the field of vehicle networking, such as being responsible for network, positioning, WIFI, and keyless entry, etc., to improve the intelligent level of the vehicle. It also includes a driving module 105, such as an ADCU module (automatic driving module), which is mainly applied in fields such as automatic driving and assisted driving. It also includes a vehicle diagnostic module 106, such as including OBD (On Board Diagnostics), from which it is possible to obtain whether the vehicle exhaust exceeds the standard through the OBD interface.

[0050] Figure 2 Two domain controllers 1 are provided. The system-on-chip 10 of one domain controller 1 is connected to the antenna module 104, the driving module 105, and the vehicle diagnostic module 106. The antenna module 104 performs network information interaction with the system-on-chip 10 within this domain controller 1, and can also transmit network information to the system-on-chip 10 of another domain controller 1 via Ethernet ETH through this domain controller 1 for processing by this other domain controller 1. The driving module 105 also performs information interaction with the directly connected system-on-chip 10, such as transmitting various sensor information of the vehicle to enter the intelligent driving mode, and the other domain controller 1 can also perform information interaction with the driving module 105. Similarly, the vehicle diagnostic module 106 is mostly used for exhaust gas detection. After being connected to the system-on-chip 10 of one domain controller 1, the system-on-chips 10 of different domain controllers 1 can also perform information interaction. Among them, the domain controller 1 further includes a reserved port 108, which can be accessed when other modules have communication requirements, or can be used to replace a certain port in case of a port failure.

[0051] In some other embodiments, the two domain controllers may also have partially different structures. Figure 3 This is a schematic structural diagram of another cockpit domain control system provided by the embodiments of the present disclosure. Refer to Figure 3, two domain controllers 1 are provided in the figure, and one of the domain controllers 1 is not provided with an Ethernet gateway 30. Among them, the system-on-chip 10 in the two domain controllers 1 realizes information interaction between different system-on-chips 10 through the audio bus A2B based on the audio interface TDM. Two audio buses A2B1 and A2B2 are shown in the figure, and standby audio buses can also be set. The embodiments of the present disclosure do not limit the number of audio buses A2B. The system-on-chip 10 in different domain controllers 1 also realizes information interaction between different system-on-chips 10 through the Ethernet ETH based on the RGMII1 interface. The control chip 20 in different domain controllers 1 realizes CAN bus connection based on the CAN interface. The system-on-chip 10 and the control chip 20 in the same domain controller 1 are connected based on the GPIO interface, the SPI interface, and the Uart interface for information interaction. In the domain controller provided with the Ethernet gateway 30, the control chip 20 is connected to the Ethernet gateway 30 based on the SGMII interface and the SPI interface. When one Ethernet gateway 30 can meet the requirements of the cockpit domain control system, the structure of the domain controller 1 can also be appropriately adjusted as described in the embodiments of the present disclosure. The antenna module 104, the driving module 105, and the vehicle diagnostic module 106 are connected to the system-on-chip 10 through the Ethernet gateway 30, and a reserved port 108 is provided. It should be noted that the embodiments of the present disclosure only provide a feasible solution, and the specific structure can be set according to actual needs.

[0052] In some embodiments, different domain controllers are connected to cockpit devices in different areas of the cockpit.

[0053] The vehicle cockpit has a large space, and there are also differences in the cockpit devices set in different spaces. Based on this, the cockpit can be divided into areas, and the cockpit devices in different areas can be connected to different domain controllers. For example, there are displays in some areas of the vehicle, while there are no displays in other areas. Then, the cockpit devices in the area with displays can be connected to the same domain controller, and this domain controller mainly controls the display and the remaining functions of this area. The cockpit devices in the area without displays can be connected to other domain controllers. By dividing the areas, the functions in the cockpit can be dispersed, and when a device in a certain area fails, it can also be quickly detected to determine whether it is a device failure or the failure of the domain controller corresponding to the area.

[0054] In some embodiments, Figure 4 is a schematic structural diagram of another cockpit domain control system provided by the embodiments of the present disclosure. Refer to Figure 4 , the domain controller 1 includes a first domain controller 01 and a second domain controller 02.

[0055] The first domain controller 01 is connected to the cockpit device 110 in the front row of the cockpit; the second domain controller 02 is connected to the cockpit device 120 in the rear row of the cockpit.

[0056] Exemplarily, the domain controller 1 includes a first domain controller 01 and a second domain controller 02. The cockpit is divided according to space, for example, into the front row and the rear row of the cockpit. Among them, the cockpit devices 110 in the front row of the cockpit are connected to the first domain controller 01. The front row of the cockpit can refer to the area where the driver and the co-driver are located. For example, the cockpit devices 110 in the front row of the cockpit can include an instrument display screen, a head-up display screen, and so on. The cockpit devices 120 in the rear row of the cockpit are connected to the second domain controller 02. The rear row of the cockpit can refer to the area where other seats in the vehicle are located. For example, the cockpit devices 120 in the rear row of the cockpit can include a ceiling screen, an armrest screen, and so on. Or when there are two rows of seat spaces in the cockpit, the row where the driver is located is the front row of the cockpit, and the other row is the rear row of the cockpit; or when there are three rows of seat spaces in the cockpit, the row where the driver is located is the front row of the cockpit, and the other two rows are the rear row of the cockpit. The embodiments of the present disclosure do not limit the division of the front and rear rows, and can be selected according to actual needs. Dividing the area in the cockpit according to the spatial position can disperse the functions in the cockpit, avoid insufficient computing power of the domain controller, and when a device in a certain area fails, it can also be quickly detected to determine the fault location.

[0057] In some embodiments, Figure 5 is a schematic structural diagram of another cockpit domain control system provided by the embodiments of the present disclosure. Refer to Figure 5 , the cockpit domain control system further includes: The cockpit devices 110 in the front row of the cockpit include a first image acquisition device 201 and an alarm prompt device 202. The cockpit devices 120 in the rear row of the cockpit include a second image acquisition device 203 and a rear row cockpit display device 204.

[0058] The first domain controller 01 is used to control the alarm prompt device 202 based on the driver information collected by the first image acquisition device 201; the second domain controller 02 is used to control the rear row cockpit display device 204 based on the passenger information collected by the second image acquisition device 203.

[0059] Exemplarily, the driver's seat is located in the front row of the cockpit. The state of the driver is crucial during driving. Therefore, the cockpit devices 110 in the front row of the cockpit include a first image acquisition device 201 and an alarm and reminder device 202. The first image acquisition device 201 is used to acquire driver information, such as image information, and then transmit it to the first domain controller 01. The first domain controller 01 analyzes and processes the image to monitor the driver's physical state and driving state. If the driver's health state is abnormal or the driving state is abnormal, the first domain controller 01 will control the alarm and reminder device 202 based on the driver information acquired by the first image acquisition device 201 to remind the driver and passengers and avoid safety problems. Most passenger seats are located in the back row of the cockpit. The cockpit devices 120 in the back row of the cockpit include a second image acquisition device 203 and a rear cockpit display device 204. When passengers in the back row of the cockpit have entertainment needs, music or videos can be played through the rear cockpit display device 204, etc. The second image acquisition device 203 can acquire passenger information. For example, it can be composed of an RGBD image acquisition and a TOF module to acquire dynamic images of passengers, such as acquiring the action instructions of passengers. The second domain controller 02 can determine the control requirements of the passengers for the rear cockpit display device 204 based on the action instructions of the passengers, such as the need to turn on the device and activate different functions, etc.

[0060] It should be noted that the cockpit devices in the front row of the cockpit are not limited to the above devices. The above embodiments are only for illustrative purposes. Similarly, the cockpit devices in the back row of the cockpit are not limited to the above devices. The above embodiments are only for illustrative purposes and can be specifically set according to actual needs.

[0061] In some embodiments, Figure 6 is a schematic structural diagram of another cockpit domain control system provided by an embodiment of the present disclosure. Refer to Figure 6 , and further includes: an image acquisition module 205, a sound processing module 206, a head-up display module 207, and an intelligent monitoring module 208; the domain controller 1 includes a third domain controller 03 and a fourth domain controller 04.

[0062] The third domain controller 03 is respectively connected to the image acquisition module 205 and the sound processing module 206; the fourth domain controller 04 is respectively connected to the head-up display module 207 and the intelligent monitoring module 208.

[0063] Exemplarily, the cockpit domain control system can also be divided according to functions. For example, it includes an image acquisition module 205, a sound processing module 206, a head-up display module 207, and an intelligent monitoring module 208. The image acquisition module 205 is used for in-vehicle image information; the sound processing module 206 is used for collecting audio data; the head-up display module 207 can project information in front of the driver's line of sight, facilitating the driver to view data such as vehicle speed and navigation, improving safety and a sense of technology; the intelligent monitoring module 208 is used for monitoring driver and passenger information. Among them, the image acquisition module 205 and the sound processing module 206 are basic functions of the vehicle, so they are connected to the third domain controller 03. The third domain controller 03 is also connected to other vehicle basic function modules, such as basic functions that even low-equipped models have, which will not be elaborated one by one here. The head-up display module 207 and the intelligent monitoring module 208 are used to improve the intelligence of the vehicle and require relatively high computing power for the vehicle. Therefore, they are connected to the fourth domain controller 04. The fourth domain controller 04 is also connected to other vehicle intelligent modules, such as additional functions of high-equipped models, which will not be elaborated one by one here, so as to distribute the computing power required by different domain controllers in the cockpit domain control system.

[0064] It should be noted that the present disclosure embodiments do not make specific restrictions on the devices controlled by different domain controllers. The above embodiments only provide some optional implementation schemes, which can be specifically selected according to actual needs.

[0065] The present disclosure embodiments also provide a vehicle, including the cockpit domain control system described in any of the above embodiments. Since the present disclosure embodiments include the cockpit domain control system in any of the above embodiments, they have the same or corresponding beneficial effects as those of the cockpit domain control systems described in the above embodiments. It should be noted that the vehicle provided in the present disclosure embodiments may also include other circuits and devices for supporting its normal operation, and no special limitations are imposed on this in this embodiment.

[0066] It should be noted that in this text, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or also elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of additional identical elements in the process, method, article or device comprising the element.

[0067] The above are only specific embodiments of the present disclosure, enabling those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to these embodiments described herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A cockpit domain control system, characterized in that, Comprising: At least two domain controllers; The domain controller includes a system-on-chip and a control chip, and the system-on-chip and the control chip in the same domain controller are connected; The system-on-chips in different domain controllers are connected to each other; the control chips in different domain controllers are connected to each other.

2. The cockpit domain control system according to claim 1, wherein The system-on-chips in different domain controllers are connected via an audio bus and / or Ethernet; the control chips in different domain controllers are connected via a CAN bus.

3. The cockpit domain control system according to claim 2, characterized in that, The domain controller includes an Ethernet gateway and an Ethernet interface chip; the system-on-chip and the Ethernet gateway in the same domain controller are both connected to the Ethernet interface chip.

4. The cockpit domain control system according to claim 3, characterized in that, The control chip in the same domain controller is connected to the Ethernet gateway.

5. The cockpit domain control system according to claim 1, wherein Further comprising: An antenna module, a driving module, and an on-vehicle diagnostic module; At least a partial quantity of the system-on-chips are connected to the antenna module, the driving module, and the on-vehicle diagnostic module.

6. The cockpit domain control system according to claim 1, characterized in that Different domain controllers are connected to cockpit devices in different regions of the cockpit.

7. The cockpit domain control system according to claim 6, characterized in that, The domain controller includes a first domain controller and a second domain controller; The first domain controller is connected to cockpit devices in the front row of the cockpit; the second domain controller is connected to cockpit devices in the rear row of the cockpit.

8. The cockpit domain control system according to claim 7, characterized in that Further comprising: The cockpit devices in the front row of the cockpit include a first image acquisition device and an alarm prompt device, and the cockpit devices in the rear row of the cockpit include a second image acquisition device and a rear-row cockpit display device; The first domain controller is configured to control the alarm prompt device based on driver information collected by the first image acquisition device; The second domain controller is configured to control the rear-row cockpit display device based on passenger information collected by the second image acquisition device.

9. The cockpit domain control system according to claim 1, wherein Further comprising: An image acquisition module, a sound processing module, a head-up display module, and an intelligent monitoring module; the domain controller includes a third domain controller and a fourth domain controller; The third domain controller is respectively connected to the image acquisition module and the sound processing module; the fourth domain controller is respectively connected to the head-up display module and the intelligent monitoring module.

10. A vehicle, characterized in that, Comprising the cockpit domain control system according to any one of claims 1-9.

Images