Cabin-driving fusion domain controller, vehicle control method and vehicle

Abstract

The invention relates to a cabin-driving fusion domain controller, a vehicle control method and a vehicle, relates to the technical field of vehicles, and can intelligently decide and synchronously adjust the power supply states of two chips according to the overall state of a cabin-driving fusion domain. The cabin driving fusion domain controller comprises a controller, a first chip and a second chip, the first chip and the second chip are both connected with the controller, the first chip is used for intelligent driving, and the second chip is used for an intelligent cabin; the controller is used for controlling the states of the first chip and the second chip according to the first operation state of the cabin-driving fusion domain, and the states of the first chip and the second chip are switched in a linkage mode.

Description

Technical Field

[0001] This disclosure relates to the field of vehicle technology, specifically to a cockpit-driver fusion domain controller, a vehicle control method, and a vehicle. Background Technology

[0002] In related technologies, the intelligent driving ECU and intelligent cockpit ECU in the vehicle ECU (Electronic Control Unit) are independent ECUs. After the intelligent driving ECU and intelligent cockpit ECU are merged, it is not possible to control the intelligent driving and intelligent cockpit in conjunction with each other based solely on the operating status of the intelligent driving or intelligent cockpit. Furthermore, the merged ECU cannot take into account the operating requirements of both intelligent driving and intelligent cockpit. Summary of the Invention

[0003] To address the shortcomings of related technologies, this disclosure provides a cabin-driver fusion domain controller, a vehicle control method, and a vehicle.

[0004] To achieve the above objectives, in a first aspect, this disclosure provides a cockpit-riding fusion domain controller, comprising: The system includes a controller, a first chip, and a second chip. Both the first chip and the second chip are connected to the controller. The first chip is used for intelligent driving, and the second chip is used for intelligent cockpit. The controller is used to control the state of the first chip and the second chip according to the first operating state of the cabin-riding fusion domain, and the states of the first chip and the second chip are switched in conjunction.

[0005] Secondly, this disclosure provides a vehicle control method applied to the cockpit-driver fusion domain controller described in the first aspect, the method comprising: Based on the first operating state of the cockpit-driving fusion domain, the states of the first chip and the second chip are controlled, and the states of the first chip and the second chip are switched in conjunction. The first chip is used for intelligent driving, and the second chip is used for intelligent cockpit.

[0006] Thirdly, this disclosure provides a vehicle including the cockpit-driver fusion domain controller described in the first aspect.

[0007] Through the above technical solution, the cockpit-driving domain controller includes a controller, a first chip, and a second chip. The controller controls the states of the first chip and the second chip according to the first operating state of the cockpit-driving fusion domain, realizing the coordinated switching of the states of the first chip and the second chip. The controller can make intelligent decisions and synchronously adjust the states of the two chips according to the overall state of the cockpit-driving fusion domain. While being compatible with the operating requirements of intelligent driving and intelligent cockpit, it can achieve system-level cross-domain power consumption collaborative optimization, and ensure the timing and consistency of intelligent driving and intelligent cockpit when switching states in the cockpit-driving fusion domain, avoiding state mismatch between intelligent driving and intelligent cockpit.

[0008] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description

[0009] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the following detailed description to explain the present disclosure, but do not constitute a limitation thereof. In the drawings: Figure 1 This is a block diagram of a cabin-riding fusion domain controller according to an exemplary embodiment of the present disclosure.

[0010] Figure 2 This is a block diagram of another cabin-riding fusion domain controller illustrated according to an exemplary embodiment of this disclosure.

[0011] Figure 3 This is a schematic diagram of cabin-riding fusion domain state control of a cabin-riding fusion domain controller according to an exemplary embodiment of the present disclosure.

[0012] Figure 4 This is a cockpit-riding fusion domain state switching diagram of another cockpit-riding fusion domain controller according to an exemplary embodiment of the present disclosure.

[0013] Figure 5 This is a cabin-riding fusion domain state switching diagram of another cabin-riding fusion domain controller shown according to an exemplary embodiment of the present disclosure.

[0014] Figure 6 This is a flowchart illustrating a vehicle control method according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0015] The specific embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit this disclosure.

[0016] As mentioned in the background section, in related technologies, the intelligent driving ECU and the intelligent cockpit ECU are independent and separate ECUs. The state synchronization between the two ECUs is achieved through a network management mechanism via the CAN bus. After cockpit-driver fusion, the two ECUs are merged into a single fused ECU. Because the state switching conditions and operating states of intelligent driving and intelligent cockpit are different, the control logic of the original intelligent driving ECU or the original intelligent cockpit ECU cannot be used independently for the state control of the fused cockpit-driver ECU.

[0017] In view of this, this disclosure provides a cockpit-driver fusion domain controller, a vehicle control method, and a vehicle, which can make intelligent decisions and synchronously adjust the states of the two chips based on the overall state of the cockpit-driver fusion domain.

[0018] Appendix Figure 1 This is a block diagram of a cabin-riding fusion domain controller according to an exemplary embodiment of this disclosure. Figure 1 As shown, the cockpit fusion domain controller includes: The system includes a controller, a first chip, and a second chip. Both the first chip and the second chip are connected to the controller. The first chip is used for intelligent driving, and the second chip is used for the intelligent cockpit. The controller is used to control the state of the first chip and the second chip according to the first operating state of the cabin-driving fusion domain, and the states of the first chip and the second chip are switched in a coordinated manner.

[0019] It should be understood that the cockpit-driver fusion domain is a fusion domain obtained by combining the intelligent driving domain and the intelligent cockpit domain.

[0020] It is worth noting that the controller can be a microcontroller unit (MCU), and the chip can be a system-on-a-chip (SoC). Specifically, the first chip can be SoC A, and the second chip can be SoC B. This disclosure does not limit this. Controlling the state of the first and second chips includes, but is not limited to, controlling the power state of the first and second chips, and controlling the power state of the sub-control modules in the first and second chips. In the following embodiments, MCU refers to the controller, SoC A refers to the first chip, and SoC B refers to the second chip for illustrative purposes.

[0021] It should be understood that the coordinated switching of the power states of the first chip and the second chip can include the following three scenarios: Scenario 1: While the power state of the first chip switches to another state, the power state of the second chip remains in its current state; Scenario 2: The power states of both the first chip and the second chip switch to another state simultaneously; Scenario 3: The power state of the first chip remains in its current state, while the power state of the second chip switches to another state. The coordinated switching of power states mentioned in this disclosure includes at least one of the above three scenarios.

[0022] In the above technical solution, the controller in the cockpit-driving domain controller controls the states of the first and second chips in the cockpit-driving fusion domain according to the operating state of the cockpit-driving fusion domain, so that the states of the first and second chips switch in tandem, thereby switching the operating state of the cockpit-driving fusion domain. That is, a single controller can intelligently make decisions and synchronously adjust the states of the two chips based on the overall state of the cockpit-driving fusion domain. While meeting the operational requirements of intelligent driving and intelligent cockpit, it achieves system-level cross-domain power consumption collaborative optimization, and ensures the timing and consistency of intelligent driving and intelligent cockpit when switching states in the cockpit-driving fusion domain, avoiding state mismatch between intelligent driving and intelligent cockpit.

[0023] To facilitate a better understanding of the cabin-pilot fusion domain controller provided in this disclosure by those skilled in the art, the cabin-pilot fusion domain controller will be described in detail below.

[0024] In one feasible embodiment, the first operating state of the cockpit-driving fusion domain includes a second operating state of intelligent driving, or a third operating state of intelligent cockpit. It's worth noting that there are two methods for fusing the cockpit-driver integration domain. Method one: Based on the existing second operating state of intelligent driving, and according to the first mapping relationship, the third operating state of the intelligent cockpit is associated and fused with the second operating state of intelligent driving to construct the first operating state of the cockpit-driver integration domain. In this case, the first operating state of the cockpit-driver integration domain corresponds one-to-one with the second operating state of intelligent driving. Method two: Based on the existing third operating state of the intelligent cockpit, and according to the second mapping relationship, the third operating state of intelligent driving is associated and fused with the second operating state of the intelligent cockpit to construct the first operating state of the cockpit-driver integration domain.

[0025] For example, when the second operating state of intelligent driving includes Shutdown, Standalone, Working, Standby+, and Standby, and the third operating state of the intelligent cockpit includes STATE_SLEEP, STATE_PRE-STARTUP, STATE_STARTUP, STATE_NORMAL, and STATE_PRE-SLEEP, the first mapping relationship is shown in Table 1 below, and the second mapping relationship is shown in Table 2 below.

[0026] Table 1

[0027] Table 2

[0028] It should be understood that, since the state range of the second operating state of intelligent driving is relatively small and the state range of the third operating state of intelligent cockpit is relatively large, the variables involved in integrating the larger state range into the smaller state range are fewer than the variables involved in integrating the smaller state range into the larger state range. Therefore, the preferred method in this disclosure is to perform the fusion of the cockpit-driver fusion domain.

[0029] Therefore, when the cockpit-driver fusion domain is fused using the first method described above, the first operating state of the cockpit-driver fusion domain includes the second state of intelligent driving. In this case, the controller is used to control the state of the first chip and the second chip according to the second operating state. When the cockpit-driver fusion domain is fused using the second method described above, the first operating state of the cockpit-driver fusion domain includes the third state of the intelligent cockpit. In this case, the controller is used to control the state of the first chip and the second chip according to the third operating state.

[0030] In the above technical solution, the operating status of intelligent driving and intelligent cockpit is dynamically associated through mapping relationship. The computing power and system resources of the two chips can be accurately allocated and adjusted according to the operating status of cockpit-driving fusion domain, avoiding computing power and power consumption redundancy, realizing efficient use of resources, and also realizing fault isolation between intelligent driving and intelligent cockpit.

[0031] In one feasible embodiment, the controller is used to control the power state of at least one first sub-control module corresponding to the first chip, and / or control the power state of at least one second sub-control module corresponding to the second chip, based on the first operating state of the cockpit-riding fusion domain.

[0032] It is worth noting that the first sub-control module can be the power supply module of the first chip, or other modules corresponding to the first chip, including but not limited to CAN module (Controller Area Network Module), Switch module, IMU module (Inertial Measurement Unit Module), GNSS module (Global Navigation Satellite System Module), Surround View Camera Module, Panoramic View Camera Module, lidar module (Light Detection and Ranging Module), radar module (Radio Detection and Ranging Module), and uss module (Ultrasonic Sensor Module). The second sub-control module can be the power module of the second chip, or other modules corresponding to the second chip, including but not limited to a display module, an audio module, a BLE module (Bluetooth Low Energy), or a WIFI module (Wireless Fidelity Module).

[0033] Accordingly, when the first sub-controller is the power module of the first chip and the second sub-module is the power module of the second chip, the controller controls the power state of the first chip and the power state of the second chip according to the first operating state of the cockpit-rider fusion domain. When the first sub-controller is another module corresponding to the first chip and the second sub-module is another module corresponding to the second chip, the controller controls the power state of the other module corresponding to the first chip and the other module corresponding to the second chip according to the first operating state of the cockpit-rider fusion domain. This achieves the switching of the operating state of the cockpit-rider fusion domain.

[0034] In the above technical solution, the controller can penetrate deep into the chip and selectively control the power state of at least one first sub-control module and / or at least one second sub-control module according to the operating status of the cockpit-rider fusion domain, achieving more granular power consumption management. Furthermore, when a specific sub-module of a chip fails, the controller can isolate the faulty module and attempt to activate other backup or functionally similar sub-modules, achieving system-level functional redundancy and degradation, thus enhancing the flexibility and reliability of the cockpit-rider fusion domain controller configuration.

[0035] In one feasible embodiment, the controller is configured with a state machine, which controls the state of the first chip and the second chip according to a first operating state of the cockpit-riding fusion domain.

[0036] It is worth noting that, such as Figure 2 As shown, the controller is configured with a state machine. The state machine controls the state of the first chip and the second chip according to the operating state of the cockpit-driver fusion domain, ensuring that the state switching of the two chips is deterministic, unambiguous and traceable under any operating state of the cockpit-driver fusion domain, which greatly improves the reliability and behavioral consistency of the cockpit-driver fusion domain.

[0037] In one feasible embodiment, the controller is configured with a state machine that switches the power state of the controller according to a first operating state of the cockpit fusion domain.

[0038] It is worth noting that, considering the power consumption of the cockpit-rider fusion domain controller, the state machine in the controller controls the states of the first and second chips simultaneously based on the operating state of the cockpit-rider fusion domain, while also controlling the controller's power state. Compared to controlling only the first and second chips, the controller's synchronous control of the controller's power state, the state of the first chip, and the state of the second chip reduces the overall energy consumption of the cockpit-rider fusion domain controller during the switching of the cockpit-rider fusion domain's operating state.

[0039] In summary, this disclosure provides a preferred method for synchronously controlling the power state of the controller, the state of the first chip, and the state of the second chip.

[0040] In one feasible embodiment, the controller is used to control the first chip and / or the second chip to perform a state switch when a state switching condition of the cabin-riding fusion domain is detected, wherein the state switching condition indicates that the cabin-riding fusion domain switches from the current state to another state. It should be understood that the controller is used to control the first chip and / or the second chip to perform state switching when the state switching conditions of the cabin-riding fusion domain are detected. The state switching includes, but is not limited to, switching the power state of the first chip and / or the second chip itself, and switching the power state of the sub-control module corresponding to the first chip and / or the second chip.

[0041] It is worth noting that the state switching conditions are related to the fusion method of the cockpit-driver fusion domain. When the cockpit-driver fusion domain is fused through the above method one, the switching conditions between each third operating state of the intelligent cockpit and the switching conditions between each second operating state of the intelligent driving associated with it need to be fused based on the first mapping relationship shown in Table 1 above.

[0042] In one example, if the switching condition between standalone and working in the second running state is A, and the switching condition between STATE_PRE-STARTUP and STATE_NORMAL in the third running state is B, then the switching condition between standalone and working in the first running state is either A or B.

[0043] It is worth noting that when the cockpit-driver fusion domain is fused through the above-mentioned method two, it is necessary to fuse the switching conditions between the second operating states of intelligent driving and the switching conditions between the third operating states of the associated fused intelligent cockpit based on the second mapping relationship shown in Table 2 above.

[0044] In another example, when the switching condition between STATE_PRE-STARTUP and STATE_NORMAL in the third running state is C, the switching condition between standalone and working in the second running state is D, and the switching condition between STATE_PRE-STARTUP and STATE_NORMAL in the first running state is either C or D.

[0045] In the aforementioned technical solutions, since the state switching of the cockpit-driver fusion domain involves multi-chip collaboration, improper switching timing or strategy may lead to functional failure or interaction conflicts. In this disclosure, the controller monitors the state switching conditions of the cockpit-driver fusion domain in real time. When a switching requirement is detected, it actively controls the first chip and / or the second chip to switch states, avoiding functional failures or conflicts caused by state switching. Furthermore, the state switching conditions reflect the real-time needs of the cockpit-driver fusion domain. Based on the state switching conditions, the controller dynamically adjusts the states of the first chip and / or the second chip, achieving on-demand allocation of computing power and power consumption, thus avoiding resource waste.

[0046] The following section uses the operating states of the cabin-driver fusion domain, including Shutdown, Standalone, Working, Standby+, and Standby, as examples to illustrate how the controller controls the first chip and / or the second chip to switch states when it detects the state switching conditions of the cabin-driver fusion domain.

[0047] In one feasible embodiment, the power states of the first chip and the second chip are switched in a coordinated manner. The controller is used to control the first chip to remain in the OFF state and control the second chip to remain in the sleep state when a first switching condition is detected, or to control the first chip to remain in the OFF state and control the second chip to switch from the sleep state to the ON state. The first operating state is the power off state, and the first switching condition characterizes the switching condition for the cockpit-rider fusion domain to switch from the power off state to the transition start state. Alternatively, the controller is used to control the first chip to remain in the OFF state and control the second chip to remain in the sleep state when the second switching condition is detected, or to control the first chip to remain in the OFF state and control the second chip to switch from the ON state to the sleep state. The first operating state is a transitional start state, and the second switching condition characterizes the switching condition for the cabin-driving fusion domain to switch from the transitional start state to the power-off state. Alternatively, the controller may, upon detecting a third switching condition, control the first chip to switch from the OFF state to the ON state and control the second chip to remain in a dormant state, or control the first chip to switch from the OFF state to the ON state and control the second chip to switch from the dormant state to the ON state. The first operating state is a transitional start state, and the third switching condition characterizes the switching condition for the cabin-driver fusion domain to switch from the transitional start state to the full-function operating state.

[0048] The first switching condition T1 includes at least one of the following: a CAN wake-up signal, a remote wake-up signal, or an RTC (Real-Time Clock) timed wake-up signal. The second switching condition T2 includes either a CAN sleep signal or a SoC B sleep signal. The third switching condition T3 includes at least one of the following three signals: 1. An OTA (Over The Air) request signal with no high-voltage component being flashed; 2. Power is ON with no OTA request signal and no collision signal; 3. Power is ON with no high-voltage component being flashed and no collision signal.

[0049] For example, in the case where the controller only controls the first chip and the second chip, such as... Figure 3As shown, the first operating state of the cockpit-driver fusion domain is the Shutdown state. When the controller detects T1, it controls SoC A to remain in the OFF state and controls SoC B to remain in the sleep state, or it controls SoC A to remain in the OFF state and controls SoC B to switch from the sleep state to the ON state. There are two scenarios for T1: Scenario 1: T1 is a CAN wake-up signal. In this case, when the controller detects a CAN wake-up signal, it controls SoC A to remain in the OFF state and controls SoC B to remain in the sleep state. Scenario 2: When T1 is a remote wake-up signal or an RTC timed wake-up signal, it controls SoC A to remain in the OFF state and controls SoC B to switch from the sleep state to the ON state.

[0050] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4 As shown, the first operating state of the cockpit-driver fusion domain is the Shutdown state. When the controller detects T1, it controls the MCU to be in the ON state, controls SoC A to remain in the OFF state, and controls SoC B to remain in the sleep state; or, it controls the MCU to be in the ON state, controls SoC A to remain in the OFF state, and controls SoC B to switch from the sleep state to the ON state. There are two scenarios for T1: Scenario 1: T1 is a CAN wake-up. In this case, when the controller detects a CAN wake-up, it controls the MCU to be in the ON state, controls SoC A to remain in the OFF state, and controls SoC B to remain in the sleep state. Scenario 2: When T1 is a remote wake-up or an RTC timed wake-up, it controls the MCU to be in the ON state, controls SoC A to remain in the OFF state, and controls SoC B to switch from the sleep state to the ON state.

[0051] Another example is the case where the controller only controls the first and second chips, such as... Figure 3As shown, the first operating state of the cockpit-driver fusion domain is Standalone. When the controller detects T2, it controls SoC A to remain OFF and SoC B to remain in sleep state. At this time, it can also control the power state of at least one first sub-control module corresponding to SoC A and the power state of at least one second sub-control module corresponding to SoC B, or control SoC A to remain OFF and control SoC B to switch from ON to sleep state. There are two scenarios for T2: Scenario 1: T2 is a CAN sleep signal. In this case, when the controller detects a CAN sleep signal, it controls SoC A to remain OFF and SoC B to remain in sleep state. Scenario 2: When T2 is a SoC B sleep signal, it controls SoC A to remain OFF and controls SoC B to switch from ON to sleep state.

[0052] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4 As shown, the first operating state of the cockpit-driver fusion domain is Standalone. When the controller detects T2, it controls the MCU to switch from ON to OFF, controls SoC A to remain OFF, and controls SoC B to remain in sleep mode. At this time, it can also control the power state of at least one first sub-control module corresponding to SoC A and the power state of at least one second sub-control module corresponding to SoC B, or control the MCU to switch from ON to OFF, control SoC A to remain OFF, and control SoC B to switch from ON to sleep mode. There are two scenarios for T2: Scenario 1: T2 is CAN sleep mode. In this case, when the controller detects CAN sleep mode, it controls the MCU to switch from ON to OFF, controls SoC A to remain OFF, and controls SoC B to remain in sleep mode. Scenario 2: When T2 is SoC B sleep mode, it controls the MCU to switch from ON to OFF, controls SoC A to remain OFF, and controls SoC B to switch from ON to sleep mode.

[0053] Another example is the case where the controller only controls the first and second chips, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is the Standalone state. When the controller detects T3, it controls SoC A to switch from the OFF state to the ON state and controls SoC B to maintain the sleep state. Alternatively, it controls SoC A to switch from the OFF state to the ON state and controls SoC B to switch from the sleep state to the ON state.

[0054] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4 As shown, the first operating state of the cockpit-driver fusion domain is Standalone state. When the controller detects T3, it controls the MCU to be in ON state, controls SoC A to switch from OFF state to ON state and controls SoC B to maintain sleep state, or controls the MCU to be in ON state, controls SoC A to switch from OFF state to ON state and controls SoC B to switch from sleep state to ON state.

[0055] In one feasible embodiment, the power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to switch from the ON state to the OFF state and control the second chip to remain in the ON state when a fourth switching condition is detected, or to control the first chip to switch from the ON state to the OFF state and control the second chip to switch from the ON state to the sleep state. The first operating state is the full-function operating state, and the fourth switching condition characterizes the switching condition for the cabin-riding fusion domain to switch from the full-function operating state to the transition start state. Alternatively, the controller may, upon detecting a fifth switching condition, control the first chip to switch from the ON state to a deep sleep state and control the second chip to remain in the ON state, or control the first chip to switch from the ON state to a deep sleep state and control the second chip to switch from the ON state to a hibernation state. The first operating state is a full-function operating state, and the fifth switching condition characterizes the switching condition for the cockpit-driver fusion domain to switch from the full-function operating state to the pre-hibernation state.

[0056] The fourth switching condition T4 includes at least one of the following: 1. a collision signal; 2. an OTA request signal and flashing of high-voltage components; 3. an abnormal voltage signal or an abnormal temperature signal. The fifth switching condition T5 includes at least one of the following: 1. a power-off (OFF) signal and no OTA request signal; 2. a long-range request signal and no OTA request signal; 3. a smart driving sleep mode activation signal and no OTA request signal.

[0057] For example, in the case where the controller only controls the first chip and the second chip, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is the Working state. When the controller detects T4, it controls SoC A to switch from the ON state to the OFF state and controls SoC B to maintain the ON state, or controls SoC A to switch from the ON state to the OFF state and controls SoC B to switch from the ON state to the sleep state.

[0058] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4As shown, the first operating state of the cockpit-driver fusion domain is the Working state. When the controller detects T4, it controls the MCU to maintain the ON state, controls SoC A to switch from the ON state to the OFF state and controls SoC B to maintain the ON state, or controls the MCU to maintain the ON state, controls SoC A to switch from the ON state to the OFF state and controls SoC B to switch from the ON state to the sleep state.

[0059] Another example is the case where the controller only controls the first and second chips, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is the Working state. When the controller detects T5, it controls SoC A to switch from the ON state to the SC7 (deep sleep) state and controls SoC B to remain in the ON state. Alternatively, it controls SoC A to switch from the ON state to the SC7 (deep sleep) state and controls SoC B to switch from the ON state to the sleep state.

[0060] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4 As shown, the first operating state of the cockpit-driver fusion domain is the Working state. When the controller detects T5, it controls the MCU to maintain the ON state, controls SoC A to switch from the ON state to the SC7 (deep sleep) state, and controls SoC B to maintain the ON state. Alternatively, it controls the MCU to maintain the ON state, controls SoC A to switch from the ON state to the SC7 (deep sleep) state, and controls SoC B to switch from the ON state to the sleep state.

[0061] In one feasible embodiment, the power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to switch from a deep sleep state to an ON state and control the second chip to maintain an ON state when a sixth switching condition is detected, or to control the first chip to switch from a deep sleep state to an ON state and control the second chip to switch from a hibernation state to an ON state. The first operating state is a pre-hibernation state, and the sixth switching condition characterizes the switching condition for the cockpit-rider fusion domain to switch from a pre-hibernation state to a full-function operating state. Alternatively, the controller is used to control the first chip to maintain a deep sleep state and control the second chip to switch from the ON state to the hibernation state when the seventh switching condition is detected, or to control the first chip to maintain a deep sleep state and control the second chip to maintain the hibernation state, wherein the first operating state is a pre-hibernation state, and the seventh switching condition characterizes the switching condition for the cockpit-driving fusion domain to switch from the pre-hibernation state to the hibernation state. Alternatively, the controller is used to control the first chip to switch from a deep sleep state to an OFF state when the eighth switching condition is detected, and to control the second chip to maintain the current state. The first operating state is a pre-sleep state, and the eighth switching condition represents the switching condition for the cockpit-driver fusion domain to switch from the pre-sleep state to the transition start mode state.

[0062] The sixth switching condition T6 includes one of the following: 1. Power-on signal, no long-range signal, intelligent driving sleep mode off signal, and no collision signal; or 2. OTA request signal and no collision signal. The seventh switching condition T7 includes one of the following: CAN wake-up signal, remote wake-up signal, or RTC timed wake-up signal. The eighth switching condition T8 includes abnormal handling signals, such as voltage abnormality signal or SoC A switching SC7 failure signal.

[0063] For example, in the case where the controller only controls the first chip and the second chip, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is the Standby+ state. When the controller detects T6, it controls SoC A to switch from SC7 to ON state and controls SoC B to maintain ON state, or controls SoC A to switch from deep sleep state to ON state and controls SoC B to switch from sleep state to ON state.

[0064] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4 As shown, the first operating state of the cockpit-driver fusion domain is the Standby+ state. When the controller detects T6, it controls the MCU to maintain the ON state, controls SoC A to switch from SC7 to the ON state and controls SoC B to maintain the ON state, or controls the MCU to maintain the ON state, controls SoC A to switch from deep sleep state to the ON state and controls SoC B to switch from sleep state to the ON state.

[0065] Another example is the case where the controller only controls the first and second chips, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is the Standby+ state. When the controller detects T7, it controls SoC A to maintain the SC7 state and controls SoC B to switch from the ON state to the sleep state, or controls SoC A to maintain the SC7 state and controls SoC B to maintain the sleep state.

[0066] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4As shown, the first operating state of the cockpit-driver fusion domain is Standby+ state. When the controller detects T7, it controls the MCU to switch from ON state to Deepstop state, controls SoC A to maintain SC7 state, and controls SoC B to switch from ON state to sleep state. Alternatively, it controls SoC A to maintain SC7 state and controls SoC B to maintain sleep state.

[0067] Another example is the case where the controller only controls the first and second chips, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is the Standby+ state. When the controller detects T8, it controls SoC A to switch from the SC7 state to the OFF state and controls SoC B to maintain the current state.

[0068] In one feasible embodiment, the power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to switch from deep sleep state to OFF state and control the second chip to maintain hibernation state if no signal is detected for a preset time. The current state of the cockpit-driving fusion domain is hibernation state. Alternatively, the controller may, upon detecting the ninth switching condition, control the first chip to maintain a deep sleep state and control the second chip to switch from a hibernation state to an ON state, or control the first chip to maintain a deep sleep state and control the second chip to maintain a hibernation state, wherein the first operating state is a hibernation state, and the ninth switching condition characterizes the switching condition for the cabin-driving fusion domain to switch from a hibernation state to a pre-hibernation state.

[0069] The preset duration can be preset according to the actual operating status of the vehicle; in this embodiment, the preset duration is 17 hours. The ninth switching condition T9 includes either a CAN sleep signal or a SoC B sleep signal.

[0070] For example, in the case where the controller only controls the first chip and the second chip, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is the Standby state. If the controller does not detect any signal for 17 hours, it controls SoC A to switch from the SC7 state to the OFF state and controls SoC B to maintain the sleep state.

[0071] For situations where the controller switches its power state while simultaneously controlling the first and second chips, such as... Figure 4 As shown, the first operating state of the cockpit-driver fusion domain is the Standby state. If the controller does not detect any signal for 17 hours, it controls the MCU to switch from the Deepstop state to the non-OFF state, controls SoC A to switch from the SC7 state to the OFF state, and controls SoC B to maintain the sleep state.

[0072] Another example is the case where the controller only controls the first and second chips, such as... Figure 3 As shown, the first operating state of the cockpit-driver fusion domain is Standby. When the controller detects T9, it controls SoC A to maintain the SC7 state and controls SoC B to switch from the sleep state to the ON state; or, it controls SoC A to maintain the SC7 state and controls SoC B to maintain the sleep state. There are two scenarios for T9: Scenario 1: T9 is a CAN sleep signal. In this case, when the controller detects a CAN sleep signal, it controls SoC A to maintain the SC7 state and controls SoC B to switch from the sleep state to the ON state. Scenario 2: When T9 is a SoC B sleep signal, it controls SoC A to maintain the SC7 state and controls SoC B to maintain the sleep state.

[0073] The following section uses the operating states of the cabin-driver fusion domain, including STATE_SLEEP, STATE_PRE-STARTUP, STATE_STARTUP, STATE_NORMAL, and STATE_PRE-SLEEP, as examples to explain how the controller controls the first chip and / or the second chip to switch states when it detects the state switching conditions of the cabin-driver fusion domain.

[0074] In one feasible embodiment, the power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to maintain the OFF state and control the second chip to switch from the sleep state to the ON state when the tenth switching condition is detected, or to control the first chip to maintain the deep sleep state and control the second chip to switch from the sleep state to the ON state, or to control the first chip to switch from the ON state to the OFF state or the deep sleep state and control the second chip to switch from the sleep state to the ON state. The first operating state is the sleep state, and the tenth switching condition represents the cockpit-driving fusion domain switching from the sleep state to the pre-start state. or, The controller is used to control the first chip to remain in the OFF state and control the second chip to remain in the ON state when the eleventh switching condition is detected, or to control the first chip to remain in the deep sleep state and control the second chip to remain in the ON state. The first operating state is the pre-start state, and the eleventh switching condition represents the cockpit-driver fusion domain switching from the pre-start state to the start state. or, The controller is used to control the first chip to remain in the OFF state and control the second chip to switch from the ON state to the sleep state when the twelfth switching condition is detected, or to control the first chip to remain in the deep sleep state and control the second chip to switch from the ON state to the sleep state. The first running state is the pre-start state, and the twelfth switching condition characterizes the switching condition for the cockpit-driver fusion domain to switch from the pre-start state to the sleep state.

[0075] The tenth switching condition T10 includes at least one of the following: remote wake-up signal, RTC wake-up signal, smart access network wake-up signal, and energy network wake-up signal. The eleventh switching condition T11 includes an ON signal for ACC (Accessory power supply) or an ON signal for KL15 (Terminal 15 ignition switching power supply). The twelfth switching condition T12 includes SoC B meeting the sleep conditions and both the smart access network and energy network going into sleep mode.

[0076] For example, in the case where the controller only controls the first chip and the second chip, such as... Figure 5 As shown, the first operating state of the cockpit-driver fusion domain is the SLEEP state. When the controller detects T10, it controls SoC A to maintain the OFF state and controls SoC B to switch from the sleep state to the ON state, or controls SoC A to maintain the SC7 state and controls SoC B to switch from the sleep state to the ON state, or controls SoC A to switch from the ON state to the OFF state or the SC7 state and controls the second chip to switch from the sleep state to the ON state.

[0077] When the first operating state of the cockpit-driver fusion domain is PRE-START, if the controller detects T11, it controls SoC A to remain OFF and SoC B to remain ON, or controls SoC A to remain in SC7 state and controls SoC B to remain ON. If the controller detects T11, it controls SoC A to remain OFF and controls SoC B to switch from ON to sleep state, or controls SoC A to remain in SC7 state and controls SoC B to switch from ON to sleep state.

[0078] In a feasible embodiment, the power states of the first chip and the second chip are switched in a coordinated manner. The controller is used to control the first chip to switch from the OFF state to the ON state and control the second chip to maintain the ON state when the thirteenth switching condition is detected, or to control the first chip to switch from the deep sleep state to the ON state and control the second chip to maintain the ON state. The first running state is the startup state, and the thirteenth switching condition characterizes the switching condition for the cockpit-rider fusion domain to switch from the startup state to the normal running state. Alternatively, the controller may, upon detecting the fourteenth switching condition, control the first chip to remain in the ON state and control the second chip to remain in the OFF state, or control the first chip to remain in the ON state and control the second chip to remain in a deep sleep state, wherein the first operating state is the startup state, and the fourteenth switching condition characterizes the switching condition for the cabin-driving fusion domain to switch from the startup state to the pre-sleep state.

[0079] Among them, the thirteenth switching condition T13 includes the start process end signal. The fourteenth switching condition T14 includes the ACC OFF signal or the KL15 OFF signal.

[0080] For example, in the case where the controller only controls the first chip and the second chip, such as... Figure 5 As shown, the first operating state of the cockpit-driver fusion domain is the START state. If the controller detects T13, it controls SoC A to switch from the OFF state to the ON state and controls SoC B to remain in the ON state, or it controls SoC A to switch from the SC7 state to the ON state and controls SoC B to remain in the ON state. If the controller detects T14, it controls SoC A to remain in the ON state and controls SoC B to remain in the OFF state, or it controls SoC A to remain in the ON state and controls SoC B to remain in the SC7 state.

[0081] In one feasible embodiment, the power states of the first chip and the second chip are switched in tandem. The controller is used to control both the first chip and the second chip to remain in the ON state when the fifteenth switching condition is detected. The first operating state is the normal operating state, and the fifteenth switching condition characterizes the switching condition for the cabin-riding fusion domain to switch from the normal operating state to the pre-sleep state. Alternatively, the controller may, upon detecting the sixteenth switching condition, control the first chip to remain in the OFF state and control the second chip to remain in the ON state, or control the first chip to remain in the deep sleep state and control the second chip to remain in the ON state, wherein the first operating state is the pre-sleep state, and the sixteenth switching condition characterizes the switching condition for the cockpit-driver fusion domain to switch from the pre-sleep state to the start state.

[0082] The fifteenth switching condition T15 includes either the OFF signal of ACC or the OFF signal of KL15. The sixteenth switching condition T16 includes either the ON signal of ACC or the ON signal of KL15.

[0083] For example, in the case where the controller only controls the first chip and the second chip, such as... Figure 5 As shown, the first operating state of the cockpit-driver fusion domain is the NORMAL state. If the controller detects T15, the controller controls both SoC A and SoC B to remain in the ON state.

[0084] Another example is the case where the controller only controls the first and second chips, such as... Figure 5 As shown, the first operating state of the cockpit-driver fusion domain is the PRE-SLEEP state. When the controller detects T16, it controls SoC A to remain in the OFF state and controls SoC B to remain in the ON state, or controls SoC A to remain in the SC7 state and controls SoC B to remain in the ON state.

[0085] Based on the same inventive concept, this disclosure provides a vehicle control method applied to the aforementioned cockpit-driver fusion domain controller, such as... Figure 6 As shown, the vehicle control method may include: Based on the first operating state of the cockpit-driving fusion domain, the states of the first chip and the second chip are controlled, and the states of the first chip and the second chip are switched in conjunction. The first chip is used for intelligent driving, and the second chip is used for intelligent cockpit.

[0086] In the above technical solution, the controller in the vehicle's cockpit-driver domain controller controls the states of the first and second chips in the cockpit-driver fusion domain controller according to the operating state of the cockpit-driver fusion domain. This causes the states of the first and second chips to switch in tandem, thereby switching the operating state of the cockpit-driver fusion domain. In other words, a single controller can intelligently make decisions and synchronously adjust the states of the two chips based on the overall state of the cockpit-driver fusion domain. This achieves system-level cross-domain power consumption optimization while being compatible with the operational requirements of intelligent driving and intelligent cockpit. Furthermore, it ensures the timing and consistency of state switching between intelligent driving and intelligent cockpit in the cockpit-driver fusion domain, avoiding state mismatch issues between intelligent driving and intelligent cockpit.

[0087] Based on the same inventive concept, this disclosure provides a vehicle including the above-described cockpit-driver fusion domain controller.

[0088] It is worth noting that the components and control principles of the cabin-riding fusion domain controller can be found in the aforementioned embodiments of the cabin-riding fusion domain controller, and will not be repeated here.

[0089] The preferred embodiments of this disclosure have been described in detail above with reference to the accompanying drawings. However, this disclosure is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this disclosure, various simple modifications can be made to the technical solutions of this disclosure, and these simple modifications all fall within the protection scope of this disclosure.

[0090] It should also be noted that the various specific technical features described in the above embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this disclosure will not describe the various possible combinations separately.

[0091] Furthermore, various different embodiments of this disclosure can be combined in any way, as long as they do not violate the spirit of this disclosure, they should also be regarded as the content disclosed in this disclosure.

Claims

1. A cockpit-riding fusion domain controller, characterized in that, include: The system includes a controller, a first chip, and a second chip. Both the first chip and the second chip are connected to the controller. The first chip is used for intelligent driving, and the second chip is used for intelligent cockpit. The controller is used to control the state of the first chip and the second chip according to the first operating state of the cabin-riding fusion domain, and the states of the first chip and the second chip are switched in conjunction.

2. The cockpit-riding fusion domain controller according to claim 1, characterized in that, The first operating state of the cockpit-driving fusion domain includes the second operating state of intelligent driving, or the third operating state of intelligent cockpit.

3. The cockpit-riding fusion domain controller according to claim 1, characterized in that, The controller is used to control the power state of at least one first sub-control module corresponding to the first chip, and / or control the power state of at least one second sub-control module corresponding to the second chip, according to the first operating state of the cabin-riding fusion domain.

4. The cockpit-riding fusion domain controller according to claim 1, characterized in that, The controller is equipped with a state machine, which is used to control the state of the first chip and the second chip according to the first operating state of the cockpit-riding fusion domain.

5. The cockpit-riding fusion domain controller according to claim 4, characterized in that, The controller is equipped with a state machine, which is used to switch the power state of the controller according to the first operating state of the cockpit-riding fusion domain.

6. The cockpit-riding fusion domain controller according to any one of claims 1-5, characterized in that, The controller is used to control the first chip and / or the second chip to switch states when a state switching condition of the cabin-to-vehicle fusion domain is detected, wherein the state switching condition indicates that the cabin-to-vehicle fusion domain switches from the current state to another state.

7. The cockpit-riding fusion domain controller according to claim 6, characterized in that, The power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to remain in the OFF state and control the second chip to remain in the sleep state when a first switching condition is detected, or to control the first chip to remain in the OFF state and control the second chip to switch from the sleep state to the ON state. The first operating state is the power off state, and the first switching condition represents the switching condition for the cabin-riding fusion domain to switch from the power off state to the transition start state. Alternatively, the controller is configured to, upon detecting a second switching condition, control the first chip to remain in the OFF state and control the second chip to remain in the sleep state, or control the first chip to remain in the OFF state and control the second chip to switch from the ON state to the sleep state, wherein the first operating state is a transitional start state, and the second switching condition characterizes the switching condition for the cabin-riding fusion domain to switch from the transitional start state to the power-off state. Alternatively, the controller is configured to, upon detecting a third switching condition, control the first chip to switch from an OFF state to an ON state and control the second chip to maintain a sleep state, or control the first chip to switch from an OFF state to an ON state and control the second chip to switch from a sleep state to an ON state, wherein the first operating state is a transitional start state, and the third switching condition characterizes the switching condition for the cabin-riding fusion domain to switch from the transitional start state to a full-function operating state.

8. The cockpit-riding fusion domain controller according to claim 6, characterized in that, The power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to switch from the ON state to the OFF state and control the second chip to remain in the ON state when a fourth switching condition is detected, or to control the first chip to switch from the ON state to the OFF state and control the second chip to switch from the ON state to the sleep state. The first operating state is a full-function operating state. The fourth switching condition represents the switching condition for the cabin-riding fusion domain to switch from the full-function operating state to the transition start state. Alternatively, the controller is configured to, upon detecting a fifth switching condition, control the first chip to switch from an ON state to a deep sleep state and control the second chip to remain ON, or control the first chip to switch from an ON state to a deep sleep state and control the second chip to switch from an ON state to a hibernation state, wherein the first operating state is a full-function operating state, and the fifth switching condition characterizes the switching condition for the cockpit-rider fusion domain to switch from the full-function operating state to a pre-hibernation state.

9. The cockpit-riding fusion domain controller according to claim 6, characterized in that, The power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to switch from deep sleep state to ON state and control the second chip to maintain ON state when a sixth switching condition is detected, or to control the first chip to switch from deep sleep state to ON state and control the second chip to switch from hibernation state to ON state. The first operating state is a pre-hibernation state. The sixth switching condition represents the switching condition for the cockpit-rider fusion domain to switch from the pre-hibernation state to the full-function operating state. Alternatively, the controller is configured to, upon detecting a seventh switching condition, control the first chip to maintain a deep sleep state and control the second chip to switch from an ON state to a hibernation state, or control the first chip to maintain a deep sleep state and control the second chip to maintain a hibernation state, wherein the first operating state is a pre-hibernation state, and the seventh switching condition characterizes the switching condition for the cockpit-riding fusion domain to switch from the pre-hibernation state to the hibernation state. Alternatively, the controller is configured to, upon detecting an eighth switching condition, control the first chip to switch from a deep sleep state to an OFF state and control the second chip to maintain its current state, wherein the first operating state is a pre-sleep state, and the eighth switching condition characterizes the switching condition for the cockpit-rider fusion domain to switch from the pre-sleep state to a transitional start-up mode state.

10. The cockpit-riding fusion domain controller according to claim 6, characterized in that, The power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to switch from deep sleep state to OFF state and control the second chip to maintain hibernation state when no signal is detected for a preset time. The current state of the cockpit-vehicle fusion domain is hibernation state. Alternatively, the controller is configured to, upon detecting a ninth switching condition, control the first chip to maintain a deep sleep state and control the second chip to switch from a hibernation state to an ON state, or control the first chip to maintain a deep sleep state and control the second chip to maintain a hibernation state, wherein the first operating state is a hibernation state, and the ninth switching condition characterizes the switching condition for the cabin-riding fusion domain to switch from the hibernation state to a pre-hibernation state.

11. The cockpit-riding fusion domain controller according to claim 6, characterized in that, The power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to remain in the OFF state and control the second chip to switch from the sleep state to the ON state when the tenth switching condition is detected, or to control the first chip to remain in the deep sleep state and control the second chip to switch from the sleep state to the ON state, or to control the first chip to switch from the ON state to the OFF state or the deep sleep state and control the second chip to switch from the sleep state to the ON state. The first operating state is the sleep state, and the tenth switching condition indicates that the cabin-riding fusion domain switches from the sleep state to the pre-start state. or, The controller is used to control the first chip to remain in the OFF state and control the second chip to remain in the ON state when the eleventh switching condition is detected, or to control the first chip to remain in the deep sleep state and control the second chip to remain in the ON state. The first operating state is the pre-start state, and the eleventh switching condition indicates that the cockpit-driver fusion domain switches from the pre-start state to the start state. or, The controller is used to control the first chip to remain in the OFF state and control the second chip to switch from the ON state to the sleep state when the twelfth switching condition is detected, or to control the first chip to remain in the deep sleep state and control the second chip to switch from the ON state to the sleep state. The first operating state is the pre-start state, and the twelfth switching condition represents the switching condition for the cabin-rider fusion domain to switch from the pre-start state to the sleep state.

12. The cockpit-riding fusion domain controller according to claim 6, characterized in that, The power states of the first chip and the second chip are switched in tandem. The controller is used to control the first chip to switch from the OFF state to the ON state and control the second chip to maintain the ON state when the thirteenth switching condition is detected, or to control the first chip to switch from the deep sleep state to the ON state and control the second chip to maintain the ON state. The first running state is the startup state. The thirteenth switching condition represents the switching condition for the cockpit-rider fusion domain to switch from the startup state to the normal operating state. Alternatively, the controller is configured to, upon detecting the fourteenth switching condition, control the first chip to remain in the ON state and control the second chip to remain in the OFF state, or control the first chip to remain in the ON state and control the second chip to remain in a deep sleep state, wherein the first operating state is the startup state, and the fourteenth switching condition characterizes the switching condition for the cabin-riding fusion domain to switch from the startup state to the pre-sleep state.

13. The cockpit-riding fusion domain controller according to claim 6, characterized in that, The power states of the first chip and the second chip are switched in tandem. The controller is used to control both the first chip and the second chip to remain in the ON state when the fifteenth switching condition is detected. The first operating state is the normal operating state. The fifteenth switching condition represents the switching condition for the cabin-riding fusion domain to switch from the normal operating state to the pre-sleep state. Alternatively, the controller is configured to, upon detecting the sixteenth switching condition, control the first chip to remain in the OFF state and control the second chip to remain in the ON state, or control the first chip to remain in a deep sleep state and control the second chip to remain in the ON state, wherein the first operating state is a pre-sleep state, and the sixteenth switching condition characterizes the switching condition for the cockpit-rider fusion domain to switch from the pre-sleep state to the start state.

14. A vehicle control method, characterized in that, Applied to the cockpit-riding fusion domain controller according to any one of claims 1-13, the method includes: Based on the first operating state of the cockpit-driving fusion domain, the states of the first chip and the second chip are controlled, and the states of the first chip and the second chip are switched in conjunction. The first chip is used for intelligent driving, and the second chip is used for intelligent cockpit.

15. A vehicle, characterized in that, Includes the cockpit-riding fusion domain controller as described in any one of claims 1-13.

Images