Intelligent cockpit domain controller fast starting method

Abstract

The application belongs to the technical field of intelligent cockpit control of automobiles, and particularly relates to a kind of intelligent cockpit domain controller fast starting method; if the intelligent cockpit domain controller receives any one of a vehicle security signal or a hibernation signal, and is in a standby state, then the application that has an influence on hibernation is closed, the network is disconnected, the current process is frozen, the hibernation process of the built-in device is followed, and the device is hibernated one by one; enter a low-power hibernation state; if the intelligent cockpit domain controller receives a start signal, then the hibernation state is ended, and normal functions are restored; the application can enable the user to use the cockpit system related functions immediately in the scenario of fast getting on the car, and achieve the purpose of improving the user experience.

Description

Technical Field

[0001] This invention belongs to the field of automotive intelligent cockpit control technology, specifically relating to a method for quickly starting an intelligent cockpit domain controller. Background Technology

[0002] As smart cockpits offer increasingly more functions, the demands on their various features are also rising. Cockpit startup time is a key indicator directly impacting user experience and the speed of vehicle access. Conventional cockpit startup times are lengthy, requiring users to wait for the system to complete startup before using navigation, voice control, media playback, and other functions – a wait that can sometimes exceed half a minute. Therefore, improving smart cockpit startup time is one way to enhance the user experience. While an active startup system would allow for immediate start-up, it would increase the vehicle's static current, leading to excessive power consumption when the vehicle is parked, impacting the battery and its charge level, and affecting future driving. Therefore, adopting an active startup system for smart cockpits is not advisable. Summary of the Invention

[0003] To overcome the above problems, this invention provides a fast startup method for a smart cockpit domain controller. This method enables the domain controller to enter a low-power sleep state to prepare for the next startup. After the user gets into the vehicle and powers on, the smart cockpit domain controller can start up quickly each time, with a startup time of less than 3 seconds. This allows the user to immediately use the cockpit system's functions even when quickly getting into the vehicle, thus improving the user experience.

[0004] A method for quickly starting up a smart cockpit domain controller includes the following:

[0005] Step 1: If the intelligent cockpit domain controller receives either the vehicle arming signal or the sleep signal, proceed to Step 2. If it receives neither the vehicle arming signal nor the sleep signal, the intelligent cockpit domain controller will not enter the sleep state.

[0006] Step 2: If the intelligent cockpit domain controller is in standby mode, proceed to Step 3; if the intelligent cockpit domain controller is not in standby mode but in working mode, return to Step 1.

[0007] Step 3: The intelligent cockpit domain controller will shut down applications that affect hibernation and disconnect from the external network, while keeping processes 1-n in its built-in whitelist in a keep-alive state.

[0008] Step 4: The intelligent cockpit domain controller determines whether all applications that were closed in Step 3 are closed, and also determines whether the network is closed. If either of these is not closed, it returns to Step 3; if both are closed, it proceeds to Step 5.

[0009] Step 5: The intelligent cockpit domain controller freezes the current process and saves the state of each process to RAM; then, according to the hibernation process of the built-in devices of the intelligent cockpit domain controller, the devices are hibernated one by one.

[0010] Step six: The intelligent cockpit domain controller enters a low-power sleep state;

[0011] Step 7: Periodically monitor the intelligent cockpit domain controller at a cycle T to ensure it remains in a low-power sleep state.

[0012] Step 8: If the intelligent cockpit domain controller receives a start signal, it will end the hibernation state and resume normal functions; if it does not receive a start signal, it will continue to maintain the hibernation state.

[0013] Step five involves freezing the current process in the Kernel real-time operating system and saving its state to RAM.

[0014] In step seven, the effective signal of the intelligent cockpit domain controller being in a low-power state is monitored periodically. If the signal is always present, it indicates that the intelligent cockpit domain controller is in a valid sleep state.

[0015] In step eight, the process of restoring the intelligent cockpit domain controller to normal function is as follows:

[0016] 8.1 The CPU of the intelligent cockpit domain controller is powered on;

[0017] 8.2 The CPU of the intelligent cockpit domain controller is initialized;

[0018] 8.3, Enable the built-in devices of the intelligent cockpit domain controller;

[0019] 8.4 Unfreeze all processes that have been frozen within the intelligent cockpit domain controller;

[0020] 8.5, The intelligent cockpit domain controller connects to the network and restores the use of various application functions.

[0021] In step six, when the intelligent cockpit domain controller is in a sleep state or about to enter a sleep state, the intelligent cockpit domain controller will retain the power supply to the core related hardware. At this time, only some interfaces of some components have a power-on retention mechanism to achieve low power consumption.

[0022] The beneficial effects of this invention are:

[0023] This invention enables the cockpit domain controller to enter a low-power sleep state, preparing and controlling it for rapid startup upon the next wake-up. This avoids excessive static current consumption when the domain controller is not in sleep mode, while also meeting the user's need to quickly experience the intelligent cockpit functions upon entering the vehicle, thus preparing for rapid startup upon the user's next vehicle entry and enabling rapid startup of the domain controller. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the content of the embodiments of the present invention and these drawings without creative effort.

[0025] Figure 1 This is a flowchart of the present invention. Detailed Implementation

[0026] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0027] In the description of this invention, unless otherwise explicitly specified and limited, the terms "connected," "linked," and "fixed" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0028] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can include direct contact between the first and second features, or contact between the first and second features through another feature between them. Furthermore, "above," "over," and "on top" of the second feature includes the first feature directly above or diagonally above the second feature, or simply indicates that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature includes the first feature directly below or diagonally below the second feature, or simply indicates that the first feature is at a lower horizontal level than the second feature.

[0029] In the description of this embodiment, the terms "upper," "lower," "left," and "right," etc., refer to the orientation or positional relationship shown in the accompanying drawings. They are used only for ease of description and simplification of operation, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the present invention. In addition, the terms "first" and "second" are used only for distinction in description and have no special meaning.

[0030] Example 1

[0031] A method for quickly starting up a smart cockpit domain controller, such as Figure 1 As shown, it includes the following:

[0032] Step 1: If the intelligent cockpit domain controller receives either the vehicle arming signal or the sleep signal, proceed to Step 2. If it receives neither the vehicle arming signal nor the sleep signal, the intelligent cockpit domain controller will not enter the sleep state.

[0033] Step 2: If the intelligent cockpit domain controller is in standby mode, proceed to Step 3; if the intelligent cockpit domain controller is not in standby mode but in working mode, return to Step 1.

[0034] Step 3: The intelligent cockpit domain controller will shut down applications that affect hibernation and disconnect from the external network, while keeping processes 1-n in its built-in whitelist in a keep-alive state.

[0035] Step 4: The intelligent cockpit domain controller determines whether all applications that were closed in Step 3 are closed, and also determines whether the network is closed. If either of these is not closed, it returns to Step 3; if both are closed, it proceeds to Step 5.

[0036] Step 5: The intelligent cockpit domain controller freezes the current process and saves the state of each process to RAM (random access memory); then, according to the hibernation process of the built-in devices of the intelligent cockpit domain controller, the devices are hibernated one by one.

[0037] Step six: The intelligent cockpit domain controller enters a low-power sleep state;

[0038] Step 7: Periodically monitor the intelligent cockpit domain controller at a cycle T to ensure it remains in a low-power sleep state.

[0039] Step 8: If the intelligent cockpit domain controller receives a start signal, it will end the hibernation state and resume normal functions; if it does not receive a start signal, it will continue to maintain the hibernation state.

[0040] Step five involves freezing the current process in the Kernel real-time operating system and saving its state to RAM.

[0041] In step seven, the effective signal of the intelligent cockpit domain controller being in a low-power state is monitored periodically. If the signal is always present, it indicates that the intelligent cockpit domain controller is in a valid sleep state.

[0042] In step eight, the process of restoring the intelligent cockpit domain controller to normal function is as follows:

[0043] 8.1 The CPU of the intelligent cockpit domain controller is powered on;

[0044] 8.2 The CPU of the intelligent cockpit domain controller is initialized;

[0045] 8.3, Enable the built-in devices of the intelligent cockpit domain controller;

[0046] 8.4 Unfreeze all processes that have been frozen within the intelligent cockpit domain controller;

[0047] 8.5, The intelligent cockpit domain controller connects to the network and restores the use of various application functions.

[0048] In step six, when the intelligent cockpit domain controller is in a sleep state or about to enter a sleep state, the intelligent cockpit domain controller will retain the power supply to the core related hardware. At this time, only some interfaces of some components have a power-on retention mechanism to achieve low power consumption.

[0049] Example 2

[0050] The technical solution described in this invention can be divided into three parts from a system perspective:

[0051] In terms of system flow, before implementing fast start, the domain controller is in the corresponding working state according to the power supply mode of the vehicle. Before implementing the fast start function, the domain controller enters the sleep state based on the user's power-off action. After the vehicle is locked or put into sleep mode, the domain controller is in a low-power sleep state. When the user starts the vehicle again, the domain controller quickly wakes up according to the fast start requirement and completes the startup to meet the user's needs.

[0052] In terms of hardware, when the domain controller is in hibernation or about to enter hibernation, the domain controller will shut down unnecessary electrical components according to the control method, while retaining the power supply to the hardware related to the startup core. At this time, only some interfaces of some components have a power-on retention mechanism to achieve low power consumption.

[0053] On the software side, based on when the domain controller enters hibernation, unnecessary services and processes are shut down, and the startup process is saved to RAM and retained to prepare for the next fast startup.

[0054] The optimized method of the present invention is described below with reference to the method flowchart:

[0055] 1. Detect whether the vehicle is armed or in sleep mode. Only allow entry into low-power sleep mode if the vehicle is armed or in sleep mode.

[0056] 2. After the low-power sleep entry state is met, attempt to start the low-power sleep entry procedure;

[0057] 3. Close applications and processes that affect hibernation, disconnect from the external network, and keep processes 1 to n in the whitelist in a keep-alive state;

[0058] 4. Freeze the current process in the Kernel real-time operating system and save its state to RAM (Random Access Memory);

[0059] 5. Perform sleep mode on key components one by one, following the device sleep mode procedure;

[0060] 6. Turn off the core components of critical devices such as the CPU and MCU, and keep unnecessary pins connected to RAM;

[0061] 7. The domain controller enters a low-power sleep state;

[0062] 8. Periodically monitor with period T to ensure the low-power sleep state remains effective, and use interruption to determine whether a start signal has been received;

[0063] 9. If a start signal is received, perform a fast start by reversing steps 6) to 3).

[0064] 10. Domain controller functionality restored.

[0065] The preferred embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the scope of protection of the present invention is not limited to the specific details in the above embodiments. Within the scope of the technical concept of the present invention, any person skilled in the art can make equivalent substitutions or changes based on the technical solution and inventive concept of the present invention within the scope of the technology disclosed in the present invention. These simple modifications are all within the scope of protection of the present invention.

[0066] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present invention will not describe the various possible combinations separately.

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

Claims

1. A method for rapid startup of an intelligent cockpit domain controller, characterized in that, Includes the following: Step 1: If the intelligent cockpit domain controller receives either the vehicle arming signal or the sleep signal, proceed to Step 2. If it receives neither the vehicle arming signal nor the sleep signal, the intelligent cockpit domain controller will not enter the sleep state. Step 2: If the intelligent cockpit domain controller is in standby mode, proceed to Step 3; if the intelligent cockpit domain controller is not in standby mode but in working mode, return to Step 1. Step 3: The intelligent cockpit domain controller will shut down applications that affect hibernation and disconnect from the external network, while keeping processes 1-n in its built-in whitelist in a keep-alive state. Step 4: The intelligent cockpit domain controller determines whether all applications that were closed in Step 3 are closed, and also determines whether the network is closed. If either of these is not closed, it returns to Step 3; if both are closed, it proceeds to Step 5. Step 5: The intelligent cockpit domain controller freezes the current process and saves the state of each process to RAM; then, according to the hibernation process of the built-in devices of the intelligent cockpit domain controller, the devices are hibernated one by one. Step six: The intelligent cockpit domain controller enters a low-power sleep state; Step 7: Periodically monitor the intelligent cockpit domain controller at a cycle T to ensure it remains in a low-power sleep state. Step 8: If the intelligent cockpit domain controller receives a start signal, it will end the hibernation state and resume normal function; if it does not receive a start signal, it will continue to maintain the hibernation state. The process by which the intelligent cockpit domain controller restores normal functionality is as follows: S8.1, the CPU of the intelligent cockpit domain controller is powered on; S8.2, the CPU of the intelligent cockpit domain controller is initialized; S8.3, activate the built-in devices of the intelligent cockpit domain controller; S8.4, Unfreeze all processes that have been frozen within the smart cockpit domain controller; S8.5, the intelligent cockpit domain controller connects to the network and restores the use of various application functions.

2. The method for rapid startup of a smart cockpit domain controller according to claim 1, characterized in that, Step five involves freezing the current process in the Kernel real-time operating system and saving its state to RAM.

3. The method for rapid startup of an intelligent cockpit domain controller according to claim 1, characterized in that, In step seven, the effective signal of the intelligent cockpit domain controller being in a low-power state is monitored periodically. If the signal is always present, it indicates that the intelligent cockpit domain controller is in a valid sleep state.

4. The method for rapid startup of an intelligent cockpit domain controller according to claim 1, characterized in that, In step six, when the intelligent cockpit domain controller is in a sleep state or about to enter a sleep state, the intelligent cockpit domain controller will retain the power supply to the core related hardware. At this time, only some interfaces of some components have a power-on retention mechanism to achieve low power consumption.

Images