Vehicle-computer resource dynamic allocation method based on application weight value, vehicle and medium

Abstract

The present invention discloses a method, a vehicle and a medium for dynamically allocating vehicle resources based on application weight values. The method comprises the following steps: classifying applications in a domain controller; assigning different dynamic weight values ​​to each application in the domain controller; the dynamic weight values ​​specifically include category weight values, response weight values ​​and scene weight values; dynamically allocating the hardware resources of the domain controller according to the dynamic weight values ​​and target red line values ​​of each application. The present invention includes an innovative design for the allocation of cockpit domain controller system resources. When the domain controller resource occupancy is lower than the red line, the application occupancy is not restricted; when the domain controller resource occupancy is too high, the resource occupancy of the applications ranked later is released. The dynamic allocation of domain controller resources depends on the calculation of application weights, the monitoring of domain controller resources and the management of application resource occupancy. It can release resources in a targeted manner based on different usage scenarios to meet user usage needs.

Description

Technical Field

[0001] The present invention relates to the technical field of domain controller resource allocation, and in particular to a method for dynamically allocating vehicle computer resources based on application weight values, a vehicle and a medium. Background Art

[0002] With the rapid development of the vehicle industry, the vehicle's electronic and electrical systems have become very complex. A vehicle has as many as 70-80 electronic control units (ECUs) with about 100 million lines of code. Therefore, new vehicles, especially new energy vehicles, will increasingly use cockpit domain controllers to achieve centralized control of vehicle functions.

[0003] The cockpit domain controller is an integrated controller used to manage and control multiple ECUs in the vehicle's electronic system. As the hub of the vehicle's electronic system, it processes and distributes data to achieve coordination and communication between various ECUs to achieve comprehensive control and optimization of the vehicle system.

[0004] As more and more ECUs are integrated into cockpit domain controllers, the application functions that cockpit domain controllers can realize are also increasing. However, the system resources of cockpit domain controllers are limited. When a large number of applications frequently call system interfaces, a large amount of system resources will be consumed, which may cause the cockpit domain controller to run slowly or freeze, affecting the vehicle's user experience. Therefore, how to effectively manage these resources, especially to maintain the stability and response speed of the cockpit domain controller under high load, is an important technical challenge. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides a method for dynamically allocating vehicle resources based on application weight values, a vehicle, and a medium.

[0006] A first aspect of the present invention provides a method for dynamically allocating vehicle resources based on application weight values, comprising the following steps:

[0007] Categorize applications in domain controllers;

[0008] A different dynamic weight value is given to each application in the domain controller; the dynamic weight value specifically includes a category weight value, a response weight value and a scenario weight value;

[0009] The hardware resources of the domain controller are dynamically allocated according to the dynamic weight value and target red line value of each application.

[0010] Furthermore, the classification of applications in the domain controller specifically includes vehicle power applications, vehicle transmission applications, assisted driving applications, body electronics applications, and intelligent information applications;

[0011] The vehicle power application is used to control the vehicle power system;

[0012] The vehicle transmission application is used to control the vehicle chassis transmission system;

[0013] The auxiliary driving application is used to realize the control of the vehicle's automatic driving operation;

[0014] The body electronics application is used to realize the integrated control of vehicle body electronic devices;

[0015] The intelligent information application is used to provide in-vehicle infotainment services on the vehicle.

[0016] Furthermore, in the step of respectively assigning different dynamic weight values ​​to each application in the domain controller:

[0017] The category weight value is determined according to the category to which the application belongs;

[0018] The response weight value is determined according to the last response time of the application in the domain controller;

[0019] The scene weight value is determined according to the current working scene of the vehicle and the category to which the application belongs.

[0020] Furthermore, each category in the domain controller is provided with an application priority for each application in the category; and the category weight value of the application is determined according to the application priority of the application in the category to which the application belongs.

[0021] Furthermore, the step of assigning a different dynamic weight value to each application in the domain controller specifically includes the following steps:

[0022] Obtain the category of the target application and determine the category weight value of the target application;

[0023] Read the last response time of the target application and determine the response weight value of the target application;

[0024] Update the scenario weight value of the target application according to the current working scenario of the domain controller;

[0025] The category weight value, response weight value, and scenario weight value of the target application are summed up to obtain the dynamic weight value of the target application.

[0026] Further, the target redline value includes the overall redline value of the domain controller and the individual redline value of the application;

[0027] The overall red line value of the domain controller is set according to the hardware resources of the domain controller;

[0028] The individual red line value of the application is determined according to the overall red line value of the domain controller and the dynamic weight value of each application.

[0029] Furthermore, the hardware resources of the domain controller specifically include CPU resources, GPU resources and NPU resources of the domain controller.

[0030] Furthermore, the dynamic allocation of the hardware resources of the domain controller specifically includes the following steps:

[0031] Allocate domain controller hardware resources no less than the individual red line value of the application to each application currently running on the domain controller.

[0032] Furthermore, when the resource usage of the domain controller reaches the overall red line value of the domain controller, the domain controller performs the following steps:

[0033] Get the dynamic weight values ​​of the applications currently running on the domain controller and sort the applications currently running on the domain controller;

[0034] Closing the application with the lowest dynamic weight value in the ranking;

[0035] Determine whether the resource usage of the domain controller is lower than the overall red line value of the domain controller; if the resource usage of the domain controller is still higher than the overall red line value of the domain controller, return to the step of closing the application with the lowest dynamic weight value in the sorting until the resource usage of the domain controller is lower than the overall red line value of the domain controller.

[0036] Further, when the target application's resource usage of the domain controller reaches the individual red line value of the target application, the domain controller performs the following steps:

[0037] Monitor resource usage of target applications within a preset time period;

[0038] When the resource usage value of the target application within a preset time period exceeds the individual red line value of the target application, the dynamic weight value of the target application is reduced.

[0039] A second aspect of the present invention provides a vehicle, on which is installed a cockpit domain controller, the cockpit domain controller comprising a processor, a memory, and computer program instructions stored in the memory and executable on the processor, wherein the processor implements the method for dynamically allocating vehicle resources based on application weight values ​​when executing the computer program instructions.

[0040] A third aspect of the present invention provides a computer-readable storage medium, wherein the storage medium stores a program, and the program is executed by a processor to implement the method for dynamically allocating vehicle resources based on application weight values.

[0041] The embodiment of the present invention also discloses a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device can read the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the above method.

[0042] The embodiments of the present invention have the following beneficial effects: the present invention provides a method for dynamically allocating vehicle resources based on application weight values, and an innovative design for allocating resources of a vehicle and medium including a cockpit domain controller system. When the domain controller resource occupancy is below the red line, no restriction is imposed on the application occupancy; when the domain controller resource occupancy is too high, the resource occupancy of applications ranked later is released. The dynamic allocation of domain controller resources depends on the calculation of application weights, the monitoring of domain controller resources, and the management of application resource occupancy. It can perform targeted resource release based on different usage scenarios to meet user usage needs.

[0043] Additional aspects and advantages of the present invention will be given in part in the following description, and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0045] Figure 1 It is a basic implementation flow chart of a method for dynamically allocating vehicle resources based on application weight values ​​of the present invention.

[0046] Figure 2 It is a schematic diagram of the application categories of the domain controller of the present invention.

[0047] Figure 3 It is a schematic diagram of the composition of dynamic weight values ​​of the present invention.

[0048] Figure 4 It is a schematic diagram of the association between the category weight value and the application priority of the present invention.

[0049] Figure 5 It is a schematic diagram of the dynamic weight value acquisition process of the present invention.

[0050] Figure 6 It is a schematic diagram of the target red line value composition of the present invention.

[0051] Figure 7 It is a schematic diagram of the hardware resources of the vehicle cockpit domain controller of the present invention.

[0052] Figure 8 It is a schematic diagram of the hardware resource release process of the vehicle cockpit domain controller of the present invention.

[0053] Fig. 9 It is a structural schematic diagram of an electronic device of the present invention.

[0054] Fig.10 It is a schematic diagram of the structure of a computer-readable storage medium of the present invention. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0056] The vehicle cockpit domain controller acts as the hub of the vehicle's electronic system, responsible for data processing, communication management, fault diagnosis and processing, and providing safety and intelligent functions to ensure the normal operation of the vehicle system and improve the driving experience. The vehicle cockpit domain controller has a high level of intelligence and integration, and can integrate different vehicle ECU modules, such as body ECU, chassis ECU, engine ECU, multimedia ECU, auxiliary driving ECU, etc., to achieve collaborative work and optimization between these ECUs. As more and more ECUs are integrated into the cockpit domain controller, the application functions that the cockpit domain controller can achieve are also increasing. However, the system resources of the cockpit domain controller are limited. When a large number of applications frequently call the system interface, a large amount of system resources will be consumed, which may cause the cockpit domain controller to run slowly or jammed, affecting the vehicle's user experience. Therefore, how to effectively manage these resources, especially to maintain the stability and response speed of the cockpit domain controller under high load, is an important technical challenge.

[0057] To solve the above problems, Figure 1 As shown, the first embodiment of the present invention provides a method for dynamically allocating vehicle resources based on application weight values, comprising the following steps:

[0058] S1. Classify the applications in the domain controller;

[0059] S2. Give different dynamic weight values ​​to each application in the domain controller;

[0060] S3. Dynamically allocate hardware resources of the domain controller according to the dynamic weight value and target red line value of each application.

[0061] The implementation process of each step of the present invention is described in detail below:

[0062] S1. Classify applications in the domain controller.

[0063] In the vehicle cockpit domain controller, various applications are usually divided based on area or function. Based on the area division, it can be divided into front body applications, left body applications, and right body applications. Various applications are classified according to the location where their control functions are implemented.

[0064] In contrast, the embodiment of the present invention adopts a division based on functions. Specifically, Figure 2 As shown, the applications carried by the domain controller can be divided into vehicle power applications, vehicle transmission applications, assisted driving applications, body electronics applications and intelligent information applications.

[0065] Vehicle power applications: Vehicle power applications are used to control vehicle power systems, including transmission management, engine management, battery monitoring, alternator regulation, etc. Vehicle power applications mainly calculate and distribute torque for various power system units (internal combustion engine, motor / generator, battery, gearbox), achieve CO2 emission reduction through predictive driving strategy, communication gateway and other functions to achieve powertrain optimization and control; at the same time, they can also have functions such as electrical intelligent fault diagnosis, intelligent power saving, and bus communication.

[0066] Vehicle transmission applications: Vehicle transmission applications are mainly responsible for specific vehicle driving control, and require unified control of systems including transmission systems, driving systems, steering systems and braking systems. The vehicle's transmission system can be divided into mechanical transmission systems, hydraulic transmission systems and electronically controlled transmission systems. Various transmission systems are mainly composed of components such as clutches, transmissions, universal transmission devices and drive axles. The vehicle's driving system includes the frame, suspension, wheels, axles, etc., which are used to connect the various parts of the vehicle into a whole and support the entire vehicle. The vehicle's steering system is used to control the vehicle's steering operation, such as hydraulic steering and wire control steering, to ensure that the vehicle can drive in a straight line or turn according to the driver's wishes. The braking system is used to control the vehicle's braking, deceleration, parking and other operations, and to perform a certain degree of forced braking on the vehicle. The specific application types in vehicle transmission applications are more common, such as air spring control, suspension damper control, rear wheel steering function, electronic stabilizer bar function, steering column position control function, etc.

[0067] Assisted driving applications: Assisted driving applications have the capabilities of multi-sensor fusion, positioning, path planning, decision control, wireless communication, and high-speed communication. They usually require multiple external cameras, millimeter-wave radars, lidars and other equipment, and the functions they complete include image recognition, data processing, etc. The functions integrated in assisted driving applications basically do not involve mechanical components, and are closely related to body electronics applications and intelligent information applications, and have a large amount of data transmission, so they have high requirements for latency.

[0068] Body electronics applications: Body electronics applications are based on the traditional BCM (Body Control Module) module to form an integration of body functions and components. The functions of the traditional body controller (BCM) mainly include the control of internal / external lights, wipers, windows, doors, electronic steering locks, etc. Body electronics applications are equivalent to the integration of functions and components of each body node. On the basis of the traditional BCM, air conditioning, damper control, tire pressure monitoring, PEPS, gateway and other functions are further integrated, so that the body-related functions are concentrated in a general controller. Therefore, including basic drive, keys, lights, doors, windows and other functions, the information collected by each body electronics can be uniformly analyzed and processed through body electronics applications, thereby realizing centralized control of each body electronics.

[0069] Intelligent information applications: Intelligent information applications integrate traditional in-vehicle information systems (instruments) and in-vehicle entertainment systems (IVI) and integrate driver monitoring systems, 360-degree surround view systems, AR HUD, driving recorders, air conditioning controllers and other functions. Intelligent information applications mainly connect system units such as full LCD instruments, large-screen central control systems, in-vehicle infotainment systems, head-up display systems, and streaming media rearview mirrors. Through wired or wireless communication, the integration of head-up display, instrument panel, navigation and other components is realized, further optimizing intelligent driving, in-vehicle interconnection, infotainment and other functions.

[0070] It can be seen from the above description that the functions implemented by different types of applications in the domain controller are different, but when the applications are running, they will uniformly occupy the resources of the vehicle cockpit domain controller. Once a large number of applications call the domain controller interface at the same time, it may cause a large loss of system resources and cause the vehicle cockpit domain controller to freeze. Therefore, the embodiment of the present invention achieves targeted resource release by assigning different dynamic weight values ​​to different applications to ensure the smoothness of the domain controller.

[0071] S2. Give different dynamic weight values ​​to each application in the domain controller.

[0072] like Figure 3 As shown, the dynamic weight value in the embodiment of the present invention specifically includes a category weight value, a response weight value and a scene weight value.

[0073] Category weight value: In the embodiment of the present invention, the category weight value refers to the weight value determined according to the category to which the application belongs. Figure 4 As shown, applications belonging to different categories will have different category weight values. Since the resource usage of applications of different categories is different, for example, the resource usage of applications that require data interaction will be greater than the resource usage of applications that do not require data interaction, the embodiment of the present invention is based on an initial category weight value for different types of applications, and then further distinguishes the weight value of the application according to the activity time of the application and the current working scene of the vehicle.

[0074] In some embodiments, since each application in the same category may have a different priority based on manual setting or automatic setting by the domain controller, for example, the domain controller can set the application priority based on the data transmission volume, and set a higher application priority for applications with a larger data transmission volume, and set a lower application priority for applications that do not require data interaction or have a smaller data transmission volume. The embodiment of the present invention does not limit the method of setting application priority. For applications in this category, the category weight values ​​of applications in the category will differ according to their own application priorities, rather than applications in the same category having the same application weight values. In some embodiments, the calculation and allocation of application priorities can also be achieved through methods such as neural network models, making the domain controller system more intelligent.

[0075] Response weight value: In the embodiment of the present invention, the response weight value refers to the value determined based on the last response time of the application in the domain controller. The last response time of the application in the domain controller represents the time when the application last sent a request / processed a request / received a request. For applications whose last response time is close to the present, it means that the application activities are relatively frequent. Stopping the activities of these applications may affect the normal operation of the vehicle system or the user experience. Therefore, these applications are usually assigned higher response weight values ​​to ensure the normal operation of the application; and for applications whose last response time is far from the present, it may mean that the application has been inactive for a long time. At this time, stopping the activities of these applications will not have much impact on the operation of the vehicle or the user experience. Therefore, they are usually assigned lower corresponding weight values, so that when the resources of the vehicle domain controller are tight, the resource occupation of these inactive applications is released first to avoid unnecessary waste of resources.

[0076] Scenario weight value: The scenario weight value in the embodiment of the present invention refers to the weight value determined according to the current working scene of the vehicle and the category to which the application belongs. For a vehicle, its working scenes include driving scenes and parking scenes; the driving scene refers to the working state of the vehicle when the vehicle is driving on the road, and the parking scene refers to the working state of the vehicle when the vehicle is parked in a parking lot or on the road. It should be noted that for different vehicles, the vehicle cabin domain controller may set different working scenes. For example, for RVs, its working scenes also include camping scenes for deploying vehicle living facilities, etc.; therefore, the embodiment of the present invention does not limit the selection of vehicle working scenes.

[0077] In different working scenarios of vehicles, different types of applications have different importance to vehicle work, so their respective scene weight values ​​will be different. For example, in driving scenarios, the scene weight values ​​of vehicle power applications, vehicle transmission applications and assisted driving applications will be higher than the scene weight values ​​of body electronics applications and intelligent information applications to ensure the normal driving of the vehicle; while in parking scenarios, the scene weight values ​​of body electronics applications and intelligent information applications will be higher than the scene weight values ​​of vehicle power applications, vehicle transmission applications and assisted driving applications to ensure the vehicle's perception of the external environment and the social entertainment needs of users inside the cockpit.

[0078] In the embodiment of the present invention, since the last response time of the application and the working scene of the vehicle are constantly changing, the response weight value and scene weight value of each application are also constantly changing, thereby forming a dynamic weight value of the application. In the embodiment of the present invention, the vehicle cockpit domain controller will periodically (e.g., every 30 seconds) update the category weight value, response weight value, and scene weight value of each application in the domain controller. Figure 5 As shown, when resources need to be released, the following steps are performed to calculate the dynamic weight value of the application:

[0079] S201. Obtain the category of the target application and determine the category weight value of the target application;

[0080] S202. Read the last response time of the target application and determine the response weight value of the target application;

[0081] S203. Update the scenario weight value of the target application according to the current working scenario of the domain controller;

[0082] S204. Sum the category weight value, response weight value, and scenario weight value of the target application to obtain a dynamic weight value of the target application.

[0083] After obtaining the weight values ​​of each target application in the embodiment of the present invention, the dynamic weight value of the target application can be obtained by adding the weight values. The weight value is presented in the form of a score. For example, the category weight value of the target application is 65, the response weight value is 30, and the scene weight value is 45, then the dynamic weight value of the target application is 65+30+45=140. In some embodiments, the score intervals of the category weight value, the response weight value, and the scene weight value may be different. For example, the score interval of the category weight value is [1,100] to indicate the relative priority of different applications, the score interval of the response weight value is [1,50] to indicate the activity level of different applications, and the score interval of the scene weight value is [30,70] to indicate the importance of different applications in different scenarios.

[0084] S3. Dynamically allocate hardware resources of the domain controller according to the dynamic weight value and target red line value of each application.

[0085] like Figure 6 As shown, the target red line value in the embodiment of the present invention refers to the resource carrying threshold of the vehicle cockpit domain controller. Since the computing resources of the vehicle cockpit domain controller are limited, when a large number of applications call the domain controller computing resources at the same time, the domain controller may freeze or crash, affecting the normal operation of the vehicle system and the user experience. Therefore, it is necessary to set a target red line value to constrain the resource usage of the application.

[0086] The target redline value in the embodiment of the present invention includes the overall redline value of the domain controller and the individual redline value of the application; wherein the overall redline value of the domain controller is set according to the hardware resources of the domain controller, and the individual redline value of the application is determined according to the overall redline value of the domain controller and the dynamic weight value of each application. Figure 7 As shown, the hardware resources of the domain controller in the embodiment of the present invention include CPU (Central Processing Unit) resources, GPU (Graphics Processing Unit) resources and NPU (Neural Processing Unit) resources. In some embodiments, the hardware resources also include ISP (Image Signal Processing), DPU (Data Processing Unit), VPU (Video Processing Unit), etc. The domain controller scans the system hardware parameters and defines the overall red line value of the domain controller.

[0087] Specifically, Figure 8As shown in the figure, when the resource usage of the domain controller reaches the overall red line value of the domain controller, the domain controller performs the following steps:

[0088] S3a-1. Obtain the dynamic weight values ​​of the applications currently running on the domain controller and sort the applications currently running on the domain controller;

[0089] S3a-2. Close the application with the lowest dynamic weight in the ranking;

[0090] S3a-3. Determine whether the resource usage of the domain controller is lower than the overall red line value of the domain controller; if the resource usage of the domain controller is still higher than the overall red line value of the domain controller, return to the step of closing the application with the lowest dynamic weight value in the sorting until the resource usage of the domain controller is lower than the overall red line value of the domain controller.

[0091] In an embodiment of the present invention, when the resource usage of the domain controller reaches the overall red line value of the domain controller, it indicates that the resource occupation of the domain controller by the application has reached a preset threshold, and resources need to be released. At this time, the domain controller will obtain the dynamic weight value of the currently running application, and sort the applications according to the dynamic weight value, with applications with high dynamic weight values ​​in front and applications with low dynamic weight values ​​in the back; at this time, the domain controller will automatically close the application with the lowest dynamic weight value, and release the resources of the application with the lowest dynamic weight value for use by other applications in the system. After completing the release of resources, the domain controller will monitor again whether the current resource usage exceeds the overall red line value. If the resource usage is lower than the overall red line value, it is deemed that the resource release operation is over; if the resource usage still exceeds the overall red line value, the application with the lowest dynamic weight value will continue to be closed to further release memory until the current resource usage is lower than the overall red line value.

[0092] Based on the overall red line value of the domain controller, the domain controller of the embodiment of the present invention sets individual red line values ​​for each application based on the dynamic weight value of each application. The individual red line value of an application is used to indicate the system resources that the application is expected to occupy. By default, each application currently running on the domain controller will be allocated domain controller hardware resources that are no less than the individual red line value of the application. When the domain controller hardware resources currently occupied by an application reach the individual red line value of the application set for it, the domain controller will perform the following steps:

[0093] S3b-1. Monitor the resource usage of the target application within a preset time period;

[0094] S3b-2. When the resource usage value of the target application within the preset time period exceeds the individual red line value of the target application, the dynamic weight value of the target application is reduced.

[0095] When the resource usage value of an application exceeds the individual red line value of the target application for a long time within a certain period of time, it indicates that the application is in an abnormal operation state and needs special attention. At this time, setting individual red line values ​​for applications can help the domain controller further locate abnormally running applications and take the initiative to reduce the weight of abnormally running applications, so that when the domain controller resource usage exceeds the overall red line value, these abnormal applications can be more easily closed, ensuring the smoothness of the vehicle cockpit domain controller system with limited system resource support.

[0096] Fig. 9 : is a schematic diagram of the structure of the vehicle proposed in the second embodiment of the present invention. Exemplarily, the vehicle includes a processor and a memory coupled to the processor. Specifically, the vehicle can be a private car, such as a sedan, SUV, MPV or pickup truck. The vehicle can also be an operating vehicle, such as a van, a bus, a small truck or a large trailer. The vehicle can be a fuel vehicle or a new energy vehicle. When the vehicle is a new energy vehicle, it can be a hybrid vehicle or a pure electric vehicle. In this embodiment, the memory stores program instructions for implementing the vehicle-machine resource dynamic allocation method based on the application weight value of any of the above embodiments, the vehicle and the medium. The processor is used to execute the program instructions stored in the memory to dynamically allocate the resources of the vehicle cabin domain controller. Among them, the processor may be an integrated circuit chip with signal processing capabilities. The processor can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0097] The contents of the method in the first embodiment of the present invention are all applicable to this vehicle embodiment. The functions specifically implemented by this vehicle embodiment are the same as those of the above method embodiment, and the beneficial effects achieved are also the same as those achieved by the above method.

[0098] Fig.10It is a schematic diagram of the structure of the computer-readable storage medium of the third embodiment of the present invention. The computer-readable storage medium of the fourth embodiment of the present invention stores program instructions that can implement the above-mentioned vehicle-machine resource dynamic allocation method based on application weight values, vehicles and media, wherein the program instructions can be stored in the above-mentioned storage medium in the form of a software product, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to execute all or part of the steps of the methods of each embodiment of the present invention. The aforementioned computer-readable storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks or optical disks, or terminal devices such as computers, servers, mobile phones, and tablets.

[0099] The contents of the method in the first embodiment of the present invention are all applicable to the computer-readable storage medium embodiment. The functions specifically implemented by the computer-readable storage medium embodiment are the same as those of the above method embodiment, and the beneficial effects achieved are also the same as those achieved by the above method.

[0100] This embodiment also provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute the above-mentioned related steps to implement the vehicle-machine resource dynamic allocation method based on application weight values, vehicle and medium provided in the above-mentioned embodiment.

[0101] Those skilled in the art will appreciate that the modules in the devices in the embodiments of the present invention may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments of the present invention may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the corresponding claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the corresponding claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0102] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0103] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection portion with one or more wirings (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0104] In addition, each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. In particular, for embodiments such as devices and equipment, since they are basically similar to method embodiments, the relevant parts can refer to the partial description of the method embodiments. The embodiments of the devices and equipment described above are merely schematic, wherein the modules, units, etc. described as separate components may or may not be physically separated, that is, they may be located in one place, or they may be distributed in multiple places, such as nodes of a system network. Specifically, some or all of the modules and units may be selected according to actual needs to achieve the purpose of the above-mentioned embodiment scheme. Those skilled in the art can understand and implement it without paying creative labor.

[0105] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0106] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0107] In addition, the terms "first", "second", etc. used in the embodiments of the present invention are only used for descriptive purposes and should not be understood as indicating or implying relative importance, or implicitly indicating the number of technical features indicated in the present embodiment. Therefore, the features defined by the terms "first", "second", etc. in the embodiments of the present invention can explicitly or implicitly indicate that the embodiment includes at least one of the features. In the description of the present invention, the word "multiple" means at least two or two or more, such as two, three, four, etc., unless otherwise clearly and specifically defined in the embodiments.

[0108] In the embodiments of the present invention, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. In addition, components, features, and elements with the same name in different embodiments of the present invention may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context in the specific embodiment.

[0109] Although embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and cannot be construed as limitations of the present invention, and those of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present invention. Those skilled in the art will readily come to think of other embodiments of the present invention after considering the specification and practicing the present invention. This application is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art that are not disclosed in the present invention. The specification and embodiments are intended to be exemplary only, and the true scope and spirit of the present invention are indicated by the following claims.

Claims

1. A method for dynamically allocating vehicle resources based on application weight values, characterized in that: The following steps are involved: Categorize applications in domain controllers; A different dynamic weight value is given to each application in the domain controller; the dynamic weight value specifically includes a category weight value, a response weight value and a scenario weight value; Dynamically allocate the hardware resources of the domain controller according to the dynamic weight value and target red line value of each application; Wherein, in the step of respectively giving different dynamic weight values ​​to each application in the domain controller: The category weight value is determined according to the category to which the application belongs; The response weight value is determined according to the last response time of the application in the domain controller; The scene weight value is determined according to the current working scene of the vehicle and the category to which the application belongs.

2. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 1, characterized in that: The classification of applications in the domain controller specifically includes vehicle power applications, vehicle transmission applications, assisted driving applications, body electronics applications, and intelligent information applications; The vehicle power application is used to control the vehicle power system; The vehicle transmission application is used to control the vehicle chassis transmission system; The auxiliary driving application is used to realize the control of the vehicle's automatic driving operation; The body electronics application is used to realize the integrated control of vehicle body electronic devices; The intelligent information application is used to provide in-vehicle infotainment services on the vehicle.

3. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 1, characterized in that: Each category in the domain controller is provided with an application priority for each application in the category; the category weight value of the application is determined according to the application priority of the application in the category to which the application belongs.

4. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 1, characterized in that: The step of assigning a different dynamic weight value to each application in the domain controller specifically includes the following steps: Obtain the category of the target application and determine the category weight value of the target application; Read the last response time of the target application and determine the response weight value of the target application; Update the scenario weight value of the target application according to the current working scenario of the domain controller; The category weight value, response weight value, and scenario weight value of the target application are summed up to obtain the dynamic weight value of the target application.

5. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 1, characterized in that: The target redline value includes the overall redline value of the domain controller and the individual redline value of the application; The overall red line value of the domain controller is set according to the hardware resources of the domain controller; The individual red line value of the application is determined according to the overall red line value of the domain controller and the dynamic weight value of each application.

6. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 5, characterized in that: The hardware resources of the domain controller specifically include the CPU resources, GPU resources and NPU resources of the domain controller.

7. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 5, characterized in that: The dynamic allocation of the hardware resources of the domain controller specifically includes the following steps: Allocate domain controller hardware resources no less than the individual red line value of the application to each application currently running on the domain controller.

8. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 7, characterized in that: When the resource usage of a domain controller reaches the overall red line value of the domain controller, the domain controller performs the following steps: Get the dynamic weight values ​​of the applications currently running on the domain controller and sort the applications currently running on the domain controller; Closing the application with the lowest dynamic weight value in the ranking; Determine whether the resource usage of the domain controller is lower than the overall red line value of the domain controller; if the resource usage of the domain controller is still higher than the overall red line value of the domain controller, return to the step of closing the application with the lowest dynamic weight value in the sorting until the resource usage of the domain controller is lower than the overall red line value of the domain controller.

9. The method for dynamically allocating vehicle resources based on application weight values ​​according to claim 5, characterized in that: When the target application's resource usage of the domain controller reaches the target application's individual red line value, the domain controller performs the following steps: Monitor resource usage of target applications within a preset time period; When the resource usage value of the target application within a preset time period exceeds the individual red line value of the target application, the dynamic weight value of the target application is reduced.

10. A vehicle, characterized in that: The vehicle is equipped with a cockpit domain controller, which includes a processor, a memory, and computer program instructions stored in the memory and executable on the processor. When the processor executes the computer program instructions, a method for dynamically allocating vehicle resources based on application weight values ​​as described in any one of claims 1 to 9 is implemented.

11. A computer-readable storage medium, characterized in that: The storage medium stores a program, and the program is executed by a processor to implement a method for dynamically allocating vehicle resources based on application weight values ​​according to any one of claims 1 to 9.

Images