Vehicle intelligent cabin computing power dispatching release method and cabin domain controller
By collecting the real-time status of the vehicle in the smart cockpit system and performing computing power scheduling control based on the driving and parking status, the experience problems caused by insufficient computing power in the smart cockpit system are solved, and the effects of computing power scheduling release and cost reduction are achieved.
Patent Information
- Application Number
- CN202411355989.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2025-01-17
AI Technical Summary
In mid- and low-end models, the smart cockpit system is slow to respond and has poor experience due to low computing power SOC chips. High-end models have insufficient computing power as software updates cannot meet the system needs, which affects the user experience.
By collecting the real-time status of the vehicle, the cabin computing power is scheduled and controlled based on the driving and parking status, giving priority to the functions required by the vehicle's real-time status, and disabling irrelevant functions or running them in the background to release computing power.
It realizes the dynamic scheduling and release of the computing power of the smart cockpit system, meets the computing power needs of different vehicle states, improves user experience, and effectively reduces the demand for high-computing power SOC chips and reduces vehicle costs.
Smart Images
Figure CN119322473A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of smart cockpits, and in particular to a method for scheduling and releasing computing power of a vehicle smart cockpit. Background Art
[0002] With the development of automobile technology, smart cockpit applications are becoming more and more widespread, with more functions and more applications. The smart cockpit system has higher and higher requirements for SOC computing power and memory. The price of the cockpit SOC chip is often proportional to the computing power. The higher the computing power, the higher the chip price. Therefore, in many cases, the cockpit SOC chips used by the OEM are often associated with cost. The chips used in mid- and low-end models have lower computing power, while the SOC chips used in high-end models have higher computing power. This will lead to defects such as slow response and poor experience of the smart cockpit system in mid- and low-end models due to low computing power SOC.
[0003] Moreover, even the high-end SOC chips used in high-end models, although their computing power meets the user's needs at the time, with the upgrade of software OTA, the functions and complexity of the software have increased over time, and the high-end SOC chips cannot fully adapt to the computing power requirements of the smart cockpit system, thus affecting the user experience. Summary of the invention
[0004] The purpose of the present invention is to overcome the shortcomings of the prior art and provide a method for scheduling and releasing computing power of a vehicle intelligent cockpit. For an intelligent cockpit system of a SOC chip with insufficient computing power, the computing power demand of the intelligent cockpit system can be met by scheduling and releasing computing power.
[0005] In order to achieve the above-mentioned purpose, the technical solution adopted by the present invention is: a method for scheduling and releasing vehicle intelligent cockpit computing power, including collecting the real-time status of the vehicle, and scheduling and controlling the cockpit computing power based on the real-time status of the vehicle: configuring the cockpit functions that match the real-time status of the vehicle to be allowed to run, and configuring the cockpit functions that do not match the real-time status of the vehicle to be prohibited from running, running in the background, or exiting after a background delay.
[0006] The real-time status of the vehicle is collected, and the vehicle is divided into driving status and parking status. The cockpit functions are allocated and restricted based on the driving status and parking status respectively to realize the release of cockpit computing power.
[0007] The real-time vehicle status is determined based on the vehicle's handbrake and / or vehicle speed signal and divided into driving status and parking status.
[0008] When the vehicle is in motion, the domain control computing power is released to the instrument function, including: making the AVM function and the DMS / OMS function mutually exclusive at the application layer, so that when one of them is working, the process of the other software is killed; at the same time, the camera function of the air-conditioning entertainment is killed; the instrument is controlled to remain in a working state and the functions unrelated to the instrument are controlled by a blacklist and whitelist to achieve process optimization of unrelated functions.
[0009] In the parking state, the domain control computing power is released to the central control entertainment function and AVM function, which are controlled to be in an activated working state and are controlled by a whitelist to optimize the process of vehicle functions other than the central control entertainment function and AVM function.
[0010] When the vehicle is in the parking state, the central control function mutual exclusion rules are preset. Among the two preset mutually exclusive functions, if one of the functions is running, the other function is disabled or stopped.
[0011] Set the basic system functions related to domain control to the whitelist. The functions in the whitelist are allowed to be enabled in parking or driving mode. When the functions are enabled, the functions in the whitelist are judged by the foreground and background. If they are in the background, the background running time is counted. When the timing time is reached, the process of the whitelist function is closed; when the function in the whitelist is switched from the background to the foreground, the background running time is reset.
[0012] A blacklist is set according to the importance of multimedia-related domain control functions. After the domain control functions in the blacklist run in the background for a set time, the process shutdown interface is called to shut down the corresponding functions.
[0013] The blacklist is divided into multiple levels. The set time allowed for the background operation of the functions in each level of the blacklist is different. The corresponding set time threshold is set according to the importance of the function.
[0014] A vehicle cockpit domain controller, which uses the vehicle intelligent cockpit computing power scheduling and release method to perform cockpit domain control computing power scheduling.
[0015] The advantages of the present invention are: through dynamic and elastic optimization of computing power release, it can meet the computing power needs of the user's vehicle smart cockpit, reasonably allocate computing power in different situations, and improve user experience; at the same time, it can effectively reduce the computing power needs of the smart cockpit, thereby reducing vehicle costs, achieving cost reduction and efficiency improvement, and at the same time achieving a better user experience based on a low-computing power SOC chip. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The following is a brief description of the contents expressed in the drawings of the present invention and the symbols in the drawings:
[0017] Figure 1 This is a schematic diagram of the architecture of a certain smart cockpit SOC chip commonly used in the prior art;
[0018] Figure 2 Schematic diagram of the hardware structure of the smart cockpit. DETAILED DESCRIPTION
[0019] The specific implementation of the present invention will be further explained in detail below by describing the optimal embodiment with reference to the accompanying drawings.
[0020] The SOC chip used in the cockpit domain controller will have different costs depending on its computing power. Generally, low-end models may not have sufficient computing power, while high-end models can meet the computing power requirements. The computing power is actually related to the response of the functions related to the cockpit domain controller. If the computing power is insufficient, it may cause untimely responses, which is reflected at the user level as software function jams, affecting the user experience. The computing power of the chip is certain, but the iterative update of software functions will put forward some new requirements for computing power. Even if the high-end models at the time have sufficient computing power, it may cause insufficient computing power over time as the system software is updated. Therefore, both high-end and low-end vehicles have insufficient computing power, but the difference is whether this problem occurs in real time or after the software update.
[0021] like Figure 1 As shown, a cockpit domain controller SOC chip in the prior art includes 4 A53 cores and 4 A72 cores; data transmission between A53 and A72 is achieved through mailbox; generally, the A53 core is used to run cockpit instrument related functions, while the A72 core runs cockpit entertainment functions, and the two are isolated and controlled by hard isolation.
[0022] like Figure 2 As shown, it is a hardware architecture block diagram of the entire cockpit domain controller, which actually includes instrument-related functions and central control entertainment-related functions as well as other functions such as AVM, DMS, and OMS. If these functions are not planned, scheduled, and controlled, they will consume the computing power of the cockpit domain controller, resulting in the interaction of computing power requirements between various functions, resulting in untimely response and jamming of cockpit domain control functions. For this application, a scheduling method is provided to release computing power, as follows:
[0023] This solution provides a method for scheduling and releasing the computing power of a vehicle intelligent cockpit, including collecting the real-time status of the vehicle, and scheduling and controlling the cockpit computing power based on the real-time status of the vehicle. The scheduling and control strategies include: configuring the cockpit functions that match the real-time status of the vehicle to be allowed to run, and configuring the cockpit functions that do not match the real-time status of the vehicle to be prohibited from running, running in the background, or exiting the running after a background delay. In this way, based on the real-time status of the vehicle, the functions required by the real-time status of the vehicle are given priority, and the functions that are not related to the real-time status and are not required are prohibited from running, or those that are already running are closed or killed in the background, thereby reducing the requirements of other functions for computing power, and the limited computing power is used as much as possible to meet the needs of the real-time vehicle status of the user, thereby realizing the scheduling and release of computing power, and reducing the problems of computing power waste and insufficient computing power caused by unreasonable computing power allocation.
[0024] The real-time status of the vehicle is collected, and based on the collected real-time status of the vehicle, the vehicle is divided into driving status and parking status. The cockpit functions are allocated and restricted based on the driving status and parking status respectively to realize the release of cockpit computing power. The computing power scheduling and release strategy in the driving state and the computing power scheduling and release strategy in the parking state are configured in advance through software. Based on the computing power scheduling and release strategy, the cockpit functions are allocated and restricted to realize the release of cockpit computing power. In the two states, the cockpit domain control functions are divided, some functions are allowed to start working, some are allowed to limit the background running time, and the remaining parts can be directly prohibited from running, thereby realizing the scheduling and control of computing power.
[0025] For the division of parking state and driving state, the real-time vehicle state is judged based on the vehicle's handbrake and / or speed signal and divided into driving state and parking state. The vehicle's speed signal and handbrake signal are collected. When the handbrake / electronic handbrake is released and the vehicle speed is greater than or equal to 5km / h, it is judged as driving state. When the handbrake / electronic handbrake is pulled up and the vehicle speed signal is less than 5km / h, it is judged as parking state.
[0026] When the vehicle is in driving state, the domain control computing power is released to the instrument function. When the vehicle is parked, the computing power of the cockpit domain controller is released to the central control entertainment function. By giving priority to the supply of computing power to meet the functions in different states, the scheduling control of computing power is achieved.
[0027] In the driving state, the computing power scheduling and release control strategy includes: giving priority to the computing power to meet the instrument function, and only meeting other functions when there is surplus computing power. Therefore, in this state, the instrument function is always kept in working state, and the AVM function and the DMS / OMS function are mutually exclusive at the application layer, so that when one of them is working, the process of the other software is killed; at the same time, the camera function of the hollow entertainment is killed to control functions other than the instrument, reduce the operation of irrelevant functions, and reduce computing power consumption. The control instrument keeps working and controls the functions not associated with the instrument through black and white lists to optimize the processes of unrelated functions. Other functions except AVM and DMS / OMS functions are restricted and controlled through black and white lists, and the processes of the functions are kept activated or killed in the background through black and white lists.
[0028] In the parking state, the domain control computing power is released to the central control entertainment function and AVM function, and the central control entertainment function and AVM function are controlled to be in an activated working state and controlled by a whitelist to optimize the process of vehicle functions other than the central control entertainment function and AVM function. In the parking state, the central control function mutual exclusion rules are pre-set. Among the two pre-set mutually exclusive functions, if one of the functions is running, the other function is disabled or stopped. For example, when the multimedia plays music, the video application is disabled. The navigation application works in the background or is disabled.
[0029] As shown in Table 1, the basic system functions related to the domain control are set as a whitelist. The functions in the whitelist are allowed to be turned on and used in parking or driving mode. When the functions are started and used, the functions in the whitelist are judged by the foreground and background. If they are in the background, the background running time is counted. After the timing time is reached, the process of the whitelist function is closed; when the function in the whitelist is switched from the background to the foreground, the background running time is reset.
[0030] Table 1
[0031]
[0032] A blacklist is set according to the importance of multimedia-related domain control functions. When the domain control functions in the blacklist run in the background for a set time, the process shutdown interface is called to shut down the corresponding functions. The blacklist is divided into multiple levels. The set time allowed for the background running of the functions in each level of the blacklist is different. The corresponding set time threshold is set according to the importance of the function.
[0033] The functions in the whitelist include launcher, System UI (status bar, negative one screen, navigation bar), air conditioning, Bluetooth phone, voice and other functions. For these functions, keep the foreground running continuously, and allow the background to run as long as possible, so as to ensure that the functions can run for a long time in the background; when these functions are switched from the foreground to the background, keep running and count the background running time until the whitelist timing threshold is reached. When the background timing threshold is reached, the corresponding function calls the kill process interface to kill the background function. If the timing threshold is not reached, the background is switched to the foreground, and the timing is reset.
[0034] The blacklist function includes the first-level blacklist and the second-level blacklist. The second-level blacklist includes personal center, karaoke application, online music, online video and other functions, and the first-level blacklist includes user manual, function mode, multimedia, USB video and pictures, system upgrade and other functions. The difference between the first-level and second-level blacklists is the time that the first-level and second-level blacklist applications are allowed to run in the background. The APP in the first-level blacklist runs in the background for 2 minutes and calls the system interface to exit the function; the APP in the second-level blacklist runs in the background for 5 minutes and calls the system interface to exit the function. The system interface called is the kill process interface, which is used to kill the corresponding functional process, thereby closing the process.
[0035] This embodiment also provides a vehicle cockpit domain controller, which adopts the above-mentioned vehicle intelligent cockpit computing power scheduling and release method to schedule the cockpit domain controller computing power, thereby also meeting the cockpit domain controller's demand for computing power.
[0036] like Figure 1 This is the architecture diagram of a SOC chip, which is mainly composed of 4 A53 cores and 4 A72 cores, and the rest of the components are omitted; data transmission between A53 and A72 is achieved through mailbox; Figure 2 The hardware block diagram of the entire cockpit system. The A53 runs the instrument function, AVM function, DMS and OMS functions; the A72 runs multimedia, navigation, voice, camera photography (calling the OMS camera data in the A53), online applications and other functions.
[0037] The working principle of the patent of this invention is as follows:
[0038] 1. The working principle of the patent of this invention is mainly based on the two scene settings of driving and parking. When driving, the computing power tends to the instrument, and when parking, the computing power tends to the central control entertainment.
[0039] 2. Judgment conditions for driving and parking: handbrake / electronic handbrake pulled up / released, and whether the vehicle speed signal is greater than 5km / h.
[0040] That is: Driving: handbrake / electronic handbrake released, vehicle speed greater than or equal to 5km / h. Parking: handbrake / electronic handbrake pulled up,
[0041] The vehicle speed signal is less than 5km / h.
[0042] 3. When driving:
[0043] ① The AVM and DMS / OMS functions are mutually exclusive at the application layer; that is, when the AVM is triggered, the system process management kills the DMS / OMS related functions and the camera function of the central control entertainment. The computing power consumption is released to the instrument to ensure the instrument function and experience.
[0044] ② Other functions not related to the instrument are also optimized to release computing power to the instrument;
[0045] 4. When parking:
[0046] ① At this time, the user is in a resting state, and the DMS / OMS function is not working. The computing power is released to the AVM, as well as the central control camera, video and other functions to ensure that the central control responds in time and guarantees the user experience.
[0047] ② Central control functions are mutually exclusive: When multimedia is playing music, the video application is disabled. The navigation application works in the background or is disabled.
[0048] Obviously, the specific implementation of the present invention is not limited to the above-mentioned methods. As long as various non-substantial improvements are made using the method concept and technical solution of the present invention, they are all within the protection scope of the present invention.
Claims
1. A method for scheduling and releasing computing power of a vehicle intelligent cockpit, characterized in that: It includes collecting the real-time status of the vehicle and scheduling and controlling the cockpit computing power based on the real-time status of the vehicle: configuring the cockpit functions that match the real-time status of the vehicle to be allowed to run, and configuring the cockpit functions that do not match the real-time status of the vehicle to be prohibited from running, running in the background, or exiting after a background delay.
2. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as claimed in claim 1, characterized in that: The real-time status of the vehicle is collected, and the vehicle is divided into driving status and parking status. The cockpit functions are allocated and restricted based on the driving status and parking status respectively to realize the release of cockpit computing power.
3. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as claimed in claim 2, characterized in that: The real-time vehicle status is determined based on the vehicle's handbrake and / or vehicle speed signal and divided into driving status and parking status.
4. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as described in any one of claims 1 to 3, characterized in that: When the vehicle is in motion, the domain control computing power is released to the instrument function, including: making the AVM function and the DMS / OMS function mutually exclusive at the application layer, so that when one of them is working, the process of the other software is killed; at the same time, the camera function of the air-conditioning entertainment is killed; the instrument is controlled to remain in a working state and the functions unrelated to the instrument are controlled by a blacklist and whitelist to achieve process optimization of unrelated functions.
5. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as claimed in claim 4, characterized in that: In the parking state, the domain control computing power is released to the central control entertainment function and AVM function, which are controlled to be in an activated working state and are controlled by a whitelist to optimize the process of vehicle functions other than the central control entertainment function and AVM function.
6. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as claimed in claim 5, characterized in that: When the vehicle is in the parking state, the central control function mutual exclusion rules are preset. Among the two preset mutually exclusive functions, if one of the functions is running, the other function is disabled or stopped.
7. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as claimed in claim 4 or 5, characterized in that: Set the basic system functions related to domain control to the whitelist. The functions in the whitelist are allowed to be enabled in parking or driving mode. When the functions are enabled, the functions in the whitelist are judged by the foreground and background. If they are in the background, the background running time is counted. When the timing time is reached, the process of the whitelist function is closed; when the function in the whitelist is switched from the background to the foreground, the background running time is reset.
8. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as claimed in claim 4 or 5, characterized in that: A blacklist is set according to the importance of multimedia-related domain control functions. After the domain control functions in the blacklist run in the background for a set time, the process shutdown interface is called to shut down the corresponding functions.
9. A method for scheduling and releasing computing power of a vehicle intelligent cockpit as claimed in claim 8, characterized in that: The blacklist is divided into multiple levels. The allowed setting time for the background operation of the functions in each level of the blacklist is different. The corresponding setting time threshold is set according to the importance of the function.
10. A vehicle cockpit domain controller, characterized in that: The cockpit domain controller uses the vehicle intelligent cockpit computing power scheduling and release method as described in any one of claims 1-9 to schedule the cockpit domain control computing power.