Patent Publication Number: US-2022219715-A1

Title: Vehicle control system, vehicle control method, and storage medium

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims the benefit of China Patent Application No. 202110035337.6 filed Jan. 12, 2021, the entire contents of which are incorporated herein by reference in its entirety. 
     TECHNICAL FIELD 
     This application relates to the field of vehicle control, and in particular to a vehicle control system, a vehicle control method, and a storage medium. 
     BACKGROUND ART 
     High-level intelligent driving has imposed increasingly high requirements on vehicle motion control. However, most of the current vehicle control methods perform transverse and longitudinal control separately, and rarely take impact in the normal direction into consideration. Furthermore, most of the current software architectures are flow-oriented. When a new function is added externally, it is required to add a function to the corresponding motion control, and consider the cooperation between the function and other functions, resulting in a heavy workload. In addition, unexpected problems may often occur to the coordination between functions. 
     SUMMARY OF THE INVENTION 
     Embodiments of this application provide a vehicle control system, a vehicle control method, and a storage medium, which are used for providing a comprehensive service combination by means of shielding underlying hardware, so as to implement more rational vehicle control. 
     According to a first aspect of this application, a vehicle control system is provided. The system includes: a planning layer in which a service is configured to generate an operation instruction according to a driving task; a reference layer in which a service is configured to generate a target parameter according to the operation instruction, the target parameter reflecting a requirement for state control of a vehicle; an advanced control layer in which a service is configured to generate an execution parameter according to the target parameter, the execution parameter reflecting an execution capability of a vehicle executor for the requirement for state control; an allocation control layer in which a service is configured to allocate category task parameters to category executors according to the execution parameter; and an underlying control layer in which a service is configured to provide the category task parameter for at least one of the category executors. 
     In some embodiments of this application, optionally, the reference layer includes at least one of the following: a longitudinal trajectory tracking service configured to provide a target longitudinal trajectory parameter of the vehicle; a transverse trajectory tracking service configured to provide a target transverse trajectory parameter of the vehicle; a six-degree-of-freedom mode service configured to provide target parameters for mode setting of the vehicle, including accelerations in three directions and angular velocities in the three directions; and a gear control service configured to provide a target parameter for gear setting of the vehicle. 
     In some embodiments of this application, optionally, the advanced control layer includes at least one of the following: a driver required torque service configured to determine a manual operation required torque; a vehicle longitudinal acceleration control service configured to determine an acceleration required torque or an execution parameter requested for parking; a yaw motion control service configured to determine a yaw motion required torque; a slip rate control service configured to determine a slip rate required torque; a normal control service configured to determine a normal torque; a pitch control service configured to determine a pitch torque; and a roll control service configured to determine a roll control torque. 
     In some embodiments of this application, optionally, the allocation control layer includes at least one of the following: a driving and braking coordination control service configured to allocate a torque control category task parameter to a driving category executor and a braking category task parameter to a braking category executor; a low-speed parking service configured to allocate a parking braking category task parameter to a parking braking category executor and a gear control category task parameter to a gear control category executor; a yaw motion control coordination service configured to allocate a braking category task parameter to a braking category executor, a steering category task parameter to a steering assistance category executor, and a suspension adjustment category task parameter to a suspension control category executor; a driving and braking slip rate control coordination service configured to allocate a torque control category task parameter to a motor torque category executor and a braking category task parameter to a braking slip rate control category executor; and a six-degree-of-freedom coordination control service configured to allocate a torque control category task parameter to a driving category executor, a braking category task parameter to a braking category executor, a steering category task parameter to a steering assistance category executor, a vehicle body height adjustment category task parameter to a vehicle body height adjustment category executor, and a normal force control category task parameter to a suspension control category executor. 
     In some embodiments of this application, optionally, the underlying control layer includes at least one of the following: a driver required torque allocation service configured to provide an actual torque control task parameter for at least one of driving category executors; a motor torque slip rate control service configured to provide an actual torque control task parameter for at least one of driving category executors; a braking force allocation service configured to provide an actual braking task parameter for at least one of braking category executors; a braking response slip rate control service configured to provide an actual braking task parameter for at least one of braking category executors; an electronic steering assistance service configured to provide an actual steering task parameter for at least one of steering assistance category executors; an air spring control service configured to provide an actual vehicle body height adjustment task parameter for at least one of vehicle body height adjustment category executors; and a suspension control service configured to provide an actual normal force control task parameter for at least one of suspension control category executors. 
     According to another aspect of this application, a vehicle control method is provided. The method includes: generating an operation instruction according to a driving task; generating a target parameter according to the operation instruction, the target parameter reflecting a requirement for state control of a vehicle; generating an execution parameter according to the target parameter, the execution parameter reflecting an execution capability of a vehicle executor for the requirement for state control; allocating category task parameters to category executors according to the execution parameter; and providing the category task parameter for at least one of the category executors. 
     In some embodiments of this application, optionally, generating a target parameter according to the operation instruction includes at least one of the following: providing a target longitudinal trajectory parameter of the vehicle; providing a target transverse trajectory parameter of the vehicle; providing target parameters for mode setting of the vehicle, including accelerations in three directions and angular velocities in the three directions; and providing a target parameter for gear setting of the vehicle. 
     In some embodiments of this application, optionally, generating an execution parameter according to the target parameter includes at least one of the following: determining a manual operation required torque; determining an acceleration required torque or an execution parameter requested for parking; determining a yaw motion required torque; determining a slip rate required torque; and determining a normal torque, a pitch torque, and a roll control torque. 
     In some embodiments of this application, optionally, allocating category task parameters to category executors according to the execution parameter includes at least one of the following: allocating a torque control category task parameter to a driving category executor; allocating a braking category task parameter to a braking category executor; allocating a parking braking category task parameter to a parking braking category executor; allocating a gear control category task parameter to a gear control category executor; allocating a steering category task parameter to a steering assistance category executor; allocating a suspension adjustment category task parameter to a suspension control category executor; allocating a torque control category task parameter to a motor torque category executor; allocating a braking category task parameter to a braking slip rate control category executor; allocating a vehicle body height adjustment category task parameter to a vehicle body height adjustment category executor; and allocating a normal force control category task parameter to a suspension control category executor. 
     In some embodiments of this application, optionally, providing the category task parameter for at least one of the category executors includes at least one of the following: providing an actual torque control task parameter for at least one of driving category executors; providing an actual braking task parameter for at least one of braking category executors; providing an actual steering task parameter for at least one of steering assistance category executors; providing an actual vehicle body height adjustment task parameter for at least one of vehicle body height adjustment category executors; and providing an actual normal force control task parameter for at least one of suspension control category executors. 
     According to still another aspect of this application, a computer-readable storage medium is provided, which has instructions stored therein, where the instructions, when executed by a processor, cause the processor to perform any one of the methods described above. 
     According to yet still another aspect of this application, a vehicle control system is provided. The system includes: an instruction generation unit configured to generate an operation instruction according to a driving task; a target parameter generation unit configured to generate a target parameter according to the operation instruction, the target parameter reflecting a requirement for state control of a vehicle; an execution parameter generation unit configured to generate an execution parameter according to the target parameter, the execution parameter reflecting an execution capability of a vehicle executor for the requirement for state control; a category parameter generation unit configured to allocate category task parameters to category executors according to the execution parameter; and a parameter allocation unit configured to provide the category task parameter for at least one of the category executors. 
     In some embodiments of this application, optionally, the target parameter generation unit may particularly perform at least one of the following: providing a target longitudinal trajectory parameter of the vehicle; providing a target transverse trajectory parameter of the vehicle; providing target parameters for mode setting of the vehicle, including accelerations in three directions and angular velocities in the three directions; and providing a target parameter for gear setting of the vehicle. 
     In some embodiments of this application, optionally, the execution parameter generation unit may particularly perform at least one of the following: determining a manual operation required torque; determining an acceleration required torque or an execution parameter requested for parking; determining a yaw motion required torque; determining a slip rate required torque; and determining a normal torque, a pitch torque, and a roll control torque. 
     In some embodiments of this application, optionally, the category parameter generation unit may particularly perform at least one of the following: allocating a torque control category task parameter to a driving category executor; allocating a braking category task parameter to a braking category executor; allocating a parking braking category task parameter to a parking braking category executor; allocating a gear control category task parameter to a gear control category executor; allocating a steering category task parameter to a steering assistance category executor; allocating a suspension adjustment category task parameter to a suspension control category executor; allocating a torque control category task parameter to a motor torque category executor; allocating a braking category task parameter to a braking slip rate control category executor; allocating a vehicle body height adjustment category task parameter to a vehicle body height adjustment category executor; and allocating a normal force control category task parameter to a suspension control category executor. 
     In some embodiments of this application, optionally, the parameter allocation unit may particularly perform at least one of the following: providing an actual torque control task parameter for at least one of driving category executors; providing an actual braking task parameter for at least one of braking category executors; providing an actual steering task parameter for at least one of steering assistance category executors; providing an actual vehicle body height adjustment task parameter for at least one of vehicle body height adjustment category executors; and providing an actual normal force control task parameter for at least one of suspension control category executors. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The above and other objectives and advantages of this application will be more thorough and clearer from the following detailed description in conjunction with the drawings, where the same or similar elements are represented by the same reference numerals. 
         FIG. 1  shows a vehicle control system according to an embodiment of this application. 
         FIG. 2  shows a vehicle control system according to an embodiment of this application. 
         FIG. 3  shows a working principle of a service according to an embodiment of this application. 
         FIG. 4  shows a vehicle control method according to an embodiment of this application. 
         FIG. 5  shows a vehicle control system according to an embodiment of this application. 
     
    
    
     DETAILED DESCRIPTION OF EMBODIMENTS 
     For the sake of brevity and illustrative purposes, the principles of this application are mainly described herein with reference to its exemplary embodiments. However, those skilled in the art would easily realize that the same principles may be equivalently applied to all types of vehicle control systems, vehicle control methods, and storage media, and these same or similar principles may be implemented therein, where any such changes do not depart from the true spirit and scope of this application. 
     The invention provides a service-oriented vehicle motion control mechanism, in which various services that may be provided through vehicle motion control are abstracted for output through a unified interface. By using an SOA architecture, which may allow for the planning and integration of service functions on different operating systems and different platforms of different OEMs to implement rapid iteration and reorganization of the functions and meet rapid and changeable business requirements, the services provided in the invention can always meet external requirements no matter how external newly-added functions change. 
     According to an aspect of this application, a vehicle control system is provided. As shown in  FIG. 1 , a vehicle control system  10  includes a planning layer L 1 , a reference layer L 2 , an advanced control layer L 3 , an allocation control layer L 4 , and an underlying control layer L 5 . Each layer is composed of several services. Each service may implement several abstract functions, thus providing various functionalities on the basis of shielding underlying hardware. 
     The services among the layers may transfer information. According to the design, a service includes several inputs and outputs. An output of a service in an upper layer may be used as an input of a service in a lower layer, and a command is finally issued to specific execution hardware. How the services in each layer transfer information is associated with a driving task. A given driving task connects one or more services in each layer in series (these services connected in series may be fixed as a model corresponding to the driving task for invocation), and a command is finally issued to execution hardware to complete the driving task. 
     A service in the planning layer L 1  of the vehicle control system  10  is configured to generate an operation instruction according to a driving task. The driving task may be a driver manipulating operable hardware as required, for example, turning a steering wheel, stepping on a brake pedal, stepping on an accelerator pedal, etc. The driving task may also be an execution process of an automatic execution mechanism according to an established procedure, for example, automatic parking, automatic vehicle following, etc. The execution process of the above driving task may be reflected by a specific operation instruction according to manipulation of the operable hardware or an automatic execution process. For example, slamming on an accelerator may be a rapid accelerating driving task. In this case, an operation instruction may be accelerating, and an acceleration value may be associated with a throttle openness. For another example, in an automatic parking process, a vehicle speed may be specifically adjusted based on obstacles in front and behind. In this case, an operation instruction may also be accelerating. 
     A service in the reference layer L 2  of the vehicle control system  10  is configured to generate a target parameter according to the operation instruction, the target parameter reflecting a requirement for state control of a vehicle. The above operation instruction generated in the planning layer L 1  is coarse and primitive. Sometimes, the operation instruction reflects only a requirement of a single driving task, but more often driving tasks are performed simultaneously. For example, the steering wheel may also be turned in a process of slamming on the accelerator pedal. The service in the reference layer L 2  may comprehensively consider a plurality of driving tasks to give a comprehensive value as the target parameter, for example, integrating received angular velocity operation instructions into a target angular velocity parameter. Furthermore, the service in the reference layer L 2  may also optimize an operation instruction value to generate the target parameter. For example, the operation instruction indicates a uniformly accelerated motion with an acceleration of 5 m/s 2 . However, for comfort of a driver and passengers and preventing the driver from stepping on the pedal accidentally, an acceleration reflected by the target parameter may have a certain hysteresis, and an acceleration curve may be smoother at an initial section.  FIG. 3  shows an acceleration curve (indicated by a dotted line) reflecting an operation instruction, and an acceleration curve (indicated by a solid line) reflecting a target parameter. Compared with the acceleration curve of the operation instruction, the acceleration curve of the target parameter has a hysteresis, in which acceleration starts at a time t 1 , and an initial acceleration section is smooth. Finally, at a time t 2 , a speed required for a driving task is reached in both curves. 
     A service in the advanced control layer L 3  of the vehicle control system  10  is configured to generate an execution parameter according to the target parameter, the execution parameter reflecting an execution capability of a vehicle executor for the requirement for state control. The target parameter determined in the reference layer L 2  reflects state requirements for the vehicle, but these requirements need to be met through execution of various resources (executors) of the vehicle. There is thus a need to convert these requirements into execution parameters of the resources of the vehicle. For example, when the target parameter is an acceleration X m/s 2 , a corresponding execution parameter is torque Y N·m. Therefore, the advanced control layer L 3  converts the state requirement for the vehicle into the execution capability of the vehicle. 
     A service in the allocation control layer L 4  of the vehicle control system  10  is configured to allocate category task parameters to category executors according to the execution parameter. In the context of this application, a class of resources that may execute the same task is classified as executors of a category. For example, when a vehicle is provided with four hub motors, the four hub motors may execute a deceleration task. In addition, four-wheel braking systems may also execute the deceleration task. The four hub motors and the four braking systems may be classified as one category of executors. During the execution of the deceleration task, the allocation control layer L 4  may allocate a corresponding category task parameter to each of the four hub motors and the four braking systems according to an execution parameter for execution of the deceleration task. 
     A service in the underlying control layer L 5  of the vehicle control system  10  is configured to provide the category task parameter for at least one of the category executors. The underlying control layer L 5  may send a command to the executor so that the executor executes a corresponding action, and may particularly send a previously determined category task parameter to one of specific hardware executors. 
     In some embodiments of this application, the reference layer L 2  may include the following services: (1) A longitudinal trajectory tracking service configured to provide a target longitudinal trajectory parameter of the vehicle, the target longitudinal trajectory parameter being used for meeting a requirement for longitudinal motion of the vehicle. (2) A transverse trajectory tracking service configured to provide a target transverse trajectory parameter of the vehicle, the target transverse trajectory parameter being used for meeting a requirement for transverse motion of the vehicle. (3) A six-degree-of-freedom mode service configured to provide target parameters for mode setting of the vehicle, for example, including accelerations in three directions and angular velocities in the three directions. Compared with the longitudinal trajectory tracking service and the transverse trajectory tracking service, the six-degree-of-freedom mode service also takes requirement in the normal direction into consideration. (4) A gear control service configured to provide a target parameter for gear setting of the vehicle. 
     In some embodiments of this application, the advanced control layer L 3  may include the following services: (1) A driver required torque service configured to determine a manual operation required torque. (2) A vehicle longitudinal acceleration control service configured to determine an acceleration required torque or an execution parameter requested for parking (for example, a braking system parameter and a gear selection parameter). (3) A yaw motion control service configured to determine a yaw motion required torque. (4) A slip rate control service configured to determine a slip rate required torque. (5) A normal control service configured to determine a normal torque. (6) A pitch control service configured to determine a pitch torque. (7) A roll control service configured to determine a roll control torque. 
     In some embodiments of this application, the allocation control layer L 4  may include the following services: (1) A driving and braking coordination control service configured to allocate a torque control category task parameter to a driving category executor and a braking category task parameter to a braking category executor. (2) A low-speed parking service configured to allocate a parking braking category task parameter to a parking braking category executor and a gear control category task parameter to a gear control category executor. (3) A yaw motion control coordination service configured to allocate a braking category task parameter to a braking category executor, a steering category task parameter to a steering assistance category executor, and a suspension adjustment category task parameter to a suspension control category executor. (4) A driving and braking slip rate control coordination service configured to allocate a torque control category task parameter to a motor torque category executor and a braking category task parameter to a braking slip rate control category executor. (5) A six-degree-of-freedom coordination control service configured to allocate a torque control category task parameter to a driving category executor, a braking category task parameter to a braking category executor, a steering category task parameter to a steering assistance category executor, a vehicle body height adjustment category task parameter to a vehicle body height adjustment category executor, and a normal force control category task parameter to a suspension control category executor. 
     In some embodiments of this application, the underlying control layer L 5  may include the following services: (1) A driver required torque allocation service configured to provide an actual torque control task parameter for at least one (for example, a front motor or a rear motor) of driving category executors. (2) A motor torque slip rate control service configured to provide an actual torque control task parameter for at least one of driving category executors. (3) A braking force allocation service configured to provide an actual braking task parameter for at least one (for example, a four-wheel braking system) of braking category executors. (4) A braking response slip rate control service configured to provide an actual braking task parameter for at least one of braking category executors. (5) An electronic steering assistance service configured to provide an actual steering task parameter (for example, a torque and an angle) for at least one (for example, an electric power steering system) of steering assistance category executors. (6) An air spring control service configured to provide an actual vehicle body height adjustment task parameter for at least one (for example, an air spring) of vehicle body height adjustment category executors. (7) A suspension control service configured to provide an actual normal force control task parameter for at least one of suspension control category executors. 
       FIG. 2  shows an example of a longitudinal motion control task according to an example of the invention, in which each small block in each layer of a vehicle control system  20  denotes one service, and a combination of these services is used to complete the longitudinal motion control task. In order to complete the longitudinal motion control task, a constructed service combination takes into consideration: a vehicle longitudinal acceleration control service and a slip rate control service in the advanced control layer L 3 ; a driving and braking coordination control service and a driving and braking slip rate control coordination service in the allocation control layer L 4 ; and a driver required torque allocation service, a motor torque slip rate control service, a braking force allocation service, and a braking response slip rate control service in the underlying control layer L 5 . Services not shown in each layer are not taken into consideration. If no service in a layer is taken into consideration, this means that an operation instruction generated in the planning layer L 1  is not specifically processed in the layer and is directly sent to the next layer. 
     In the example of  FIG. 2 , outputs (execution parameters) of the vehicle longitudinal acceleration control service and the slip rate control service in the advanced control layer L 3  are used as an input of the driving and braking coordination control service in the allocation control layer L 4 ; an output (a category task parameter) of the slip rate control service in the advanced control layer L 3  is used as an input of the driving and braking slip rate control coordination service in the allocation control layer L 4 ; and an output of the driving and braking coordination control service in the allocation control layer L 4  is used as inputs of the driver required torque allocation service and the braking force allocation service in the underlying control layer L 5 , and an output of the driving and braking slip rate control coordination service in L 4  is used as inputs of the braking force allocation service and the braking response slip rate control service in the underlying control layer L 5 . Through a service architecture constructed in this way, the longitudinal motion control task can be implemented. 
     According to another aspect of this application, a vehicle control method is provided. As shown in  FIG. 4 , the vehicle control method includes the following steps. Step S 401 : Generate an operation instruction according to a driving task. The driving task may be a driver manipulating operable hardware as required, for example, turning a steering wheel, stepping on a brake pedal, stepping on an accelerator pedal, etc. The driving task may also be an execution process of an automatic execution mechanism according to an established procedure, for example, automatic parking, automatic vehicle following, etc. The execution process of the above driving task may be reflected as a specific operation instruction according to manipulation of the operable hardware or an execution process. For example, slamming on an accelerator may be a rapid accelerating driving task. In this case, an operation instruction may be accelerating, and an acceleration value may be associated with a throttle openness. For another example, in an automatic parking process, a vehicle speed may be specifically adjusted based on obstacles in front and behind. In this case, an operation instruction may also be accelerating. 
     The vehicle control method includes generating a target parameter according to the operation instruction in step S 402 , the target parameter reflecting a requirement for state control of a vehicle. The operation instruction generated in step S 401  above is coarse and primitive. Sometimes, the operation instruction reflects only a requirement of a single driving task, but more often driving tasks are performed simultaneously. For example, the steering wheel may also be turned in a process of slamming on the accelerator pedal. In step S 402 , a plurality of driving tasks may be comprehensively considered to give a comprehensive value as the target parameter. Furthermore, in step S 402 , an operation instruction value may also be optimized to generate the target parameter. For example, the operation instruction indicates a uniformly accelerated motion with an acceleration of 5 m/s 2 . However, for comfort of a driver and passengers and preventing the driver from stepping on the pedal accidentally, an acceleration reflected by the target parameter may have a certain hysteresis, and an acceleration curve may be smoother at an initial section.  FIG. 3  shows an acceleration curve (indicated by a dotted line) reflecting an operation instruction, and an acceleration curve (indicated by a solid line) reflecting a target parameter. Compared with the acceleration curve of the operation instruction, the acceleration curve of the target parameter has a hysteresis, in which acceleration starts at a time t 1 , and an initial acceleration section is smooth. Finally, at a time t 2 , a speed required for a driving task is reached. 
     The vehicle control method includes generating an execution parameter according to the target parameter in step S 403 , the execution parameter reflecting an execution capability of a vehicle executor for the requirement for state control. The target parameter determined in step S 402  reflects state requirements for the vehicle, but these requirements need to be met through execution of various resources (executors) of the vehicle. There is thus a need to convert these requirements into execution parameters of the resources of the vehicle. For example, when the target parameter is an acceleration X m/s 2 , a corresponding execution parameter is torque Y N·m. Therefore, in step S 403 , the state requirement for the vehicle may be converted into the execution capability of the vehicle. 
     The vehicle control method includes allocating category task parameters to category executors according to the execution parameter in step S 404 . In the context of this application, a class of resources that may execute the same task is classified as executors of a category. For example, when a vehicle is provided with four hub motors, the four hub motors may execute a deceleration task. In addition, four-wheel braking systems may also execute the deceleration task. The four hub motors and the four braking systems may be classified as one category of executors. During the execution of the deceleration task, in step S 404 , a corresponding category task parameter may be allocated to each of the four hub motors and the four braking systems according to an execution parameter for execution of the deceleration task. 
     The vehicle control method includes providing the category task parameter for at least one of the category executors in step S 405 . In step S 405 , a command may be sent to the executor so that the executor executes a corresponding action, and particularly, a previously determined category task parameter may be sent to a specific hardware executor. 
     In some embodiments of this application, generating a target parameter according to the operation instruction in step S 402  includes at least one of the following: (1) Providing a target longitudinal trajectory parameter of the vehicle, the target longitudinal trajectory parameter being used for meeting a requirement for longitudinal motion of the vehicle. (2) Providing a target transverse trajectory parameter of the vehicle, the target transverse trajectory parameter being used for meeting a requirement for transverse motion of the vehicle. (3) Providing target parameters for mode setting of the vehicle, for example, including accelerations in three directions and angular velocities in the three directions. Compared with the longitudinal trajectory tracking service and the transverse trajectory tracking service, the six-degree-of-freedom mode service also takes requirement in the normal direction into consideration. (4) Providing a target parameter for gear setting of the vehicle. 
     In some embodiments of this application, generating an execution parameter according to the target parameter in step S 403  includes at least one of the following: (1) Determining a manual operation required torque. (2) Determining an acceleration required torque or an execution parameter requested for parking (for example, a braking system parameter and a gear selection parameter). (3) Determining a yaw motion required torque. (4) Determining a slip rate required torque. (5) Determining a normal torque, a pitch torque, and a roll control torque. 
     In some embodiments of this application, allocating category task parameters to category executors according to the execution parameter in step S 404  includes at least one of the following: (1) allocating a torque control category task parameter to a driving category executor; (2) allocating a braking category task parameter to a braking category executor; (3) allocating a parking braking category task parameter to a parking braking category executor; (4) allocating a gear control category task parameter to a gear control category executor; (5) allocating a steering category task parameter to a steering assistance category executor; (6) allocating a suspension adjustment category task parameter to a suspension control category executor; (7) allocating a torque control category task parameter to a motor torque category executor; (8) allocating a braking category task parameter to a braking slip rate control category executor; (9) allocating a vehicle body height adjustment category task parameter to a vehicle body height adjustment category executor; and (10) allocating a normal force control category task parameter to a suspension control category executor. 
     In some embodiments of this application, providing the category task parameter for at least one of the category executors in step S 405  includes at least one of the following: (1) Providing an actual torque control task parameter for at least one (for example, a front motor or a rear motor) of driving category executors. (2) Providing an actual braking task parameter for at least one (for example, a four-wheel braking system) of braking category executors. (3) Providing an actual steering task parameter (for example, a torque and an angle) for at least one (for example, an electric power steering system) of steering assistance category executors. (4) Providing an actual vehicle body height adjustment task parameter for at least one (for example, an air spring) of vehicle body height adjustment category executors. (5) Providing an actual normal force control task parameter for at least one of suspension control category executors. 
     According to still another aspect of this application, a computer-readable storage medium is provided, which has instructions stored therein, where the instructions, when executed by a processor, cause the processor to perform any one of the vehicle control methods described above. The computer-readable medium in this application includes various types of computer storage media, and may be any usable medium accessible to a general-purpose or special-purpose computer. For example, the computer-readable medium may include a RAM, a ROM, an EPROM, an EEPROM, a register, a hard disk, a removable hard disk, a CD-ROM or another optical memory, a magnetic disk memory or another magnetic storage device, or any other transitory or non-transitory media that can carry or store expected program code having an instruction or data structure form and be accessible to the general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Data is usually copied magnetically in a disk used herein, while data is usually copied optically by using lasers in a disc. A combination thereof shall also fall within the scope of protection of the computer-readable media. For example, the storage medium is coupled to a processor, so that the processor can read information from and write information to the storage medium. In an alternative solution, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative solution, the processor and the storage medium may reside as discrete assemblies in a user terminal. 
     According to yet still another aspect of this application, a vehicle control system is provided. As shown in  FIG. 5 , a vehicle control system  50  includes an instruction generation unit  501 , a target parameter generation unit  502 , an execution parameter generation unit  503 , a category parameter generation unit  504 , and a parameter allocation unit  505 . 
     The instruction generation unit  501  is configured to generate an operation instruction according to a driving task. The driving task may be a driver manipulating operable hardware as required, for example, turning a steering wheel, stepping on a brake pedal, stepping on an accelerator pedal, etc. The driving task may also be an execution process of an automatic execution mechanism according to an established procedure, for example, automatic parking, automatic vehicle following, etc. The execution process of the above driving task may be reflected as a specific operation instruction according to manipulation of the operable hardware or an execution process. For example, slamming on an accelerator may be a rapid accelerating driving task. In this case, an operation instruction may be accelerating, and an acceleration value may be associated with a throttle openness. For another example, in an automatic parking process, a vehicle speed may be specifically adjusted based on obstacles in front and behind. In this case, an operation instruction may also be accelerating. 
     The target parameter generation unit  502  is configured to generate a target parameter according to the operation instruction, the target parameter reflecting a requirement for state control of a vehicle. The operation instruction generated by the instruction generation unit  501  described above is coarse and primitive. Sometimes, the operation instruction reflects only a requirement of a single driving task, but more often driving tasks are performed simultaneously. For example, the steering wheel may also be turned in a process of slamming on the accelerator pedal. The target parameter generation unit  502  may comprehensively consider a plurality of driving tasks to give a comprehensive value as the target parameter. Furthermore, the target parameter generation unit  502  may also optimize an operation instruction value to generate the target parameter. For example, the operation instruction indicates a uniformly accelerated motion with an acceleration of 5 m/s 2 . However, for comfort of a driver and passengers and preventing the driver from stepping on the pedal accidentally, an acceleration reflected by the target parameter may have a certain hysteresis, and an acceleration curve may be smoother at an initial section.  FIG. 3  shows an acceleration curve (indicated by a dotted line) reflecting an operation instruction, and an acceleration curve (indicated by a solid line) reflecting a target parameter. Compared with the acceleration curve of the operation instruction, the acceleration curve of the target parameter has a hysteresis, in which acceleration starts at a time t 1 , and an initial acceleration section is smooth. Finally, at a time t 2 , a speed required for a driving task is reached. 
     The execution parameter generation unit  503  is configured to generate an execution parameter according to the target parameter, the execution parameter reflecting an execution capability of a vehicle executor for the requirement for state control. The target parameter determined by the target parameter generation unit  502  reflects state requirements for the vehicle, but these requirements need to be met through execution of various resources (executors) of the vehicle. There is thus a need to convert these requirements into execution parameters of the resources of the vehicle. For example, when the target parameter is an acceleration X m/s 2 , a corresponding execution parameter is torque Y N·m. Therefore, the target parameter generation unit  502  may convert the state requirement for the vehicle into the execution capability of the vehicle. 
     The category parameter generation unit  504  is configured to allocate category task parameters to category executors according to the execution parameter. In the context of this application, a class of resources that may execute the same task is classified as executors of a category. For example, when a vehicle is provided with four hub motors, the four hub motors may execute a deceleration task. In addition, four-wheel braking systems may also execute the deceleration task. The four hub motors and the four braking systems may be classified as one category of executors. During the execution of the deceleration task, the category parameter generation unit  504  may allocate a corresponding category task parameter to each of the four hub motors and the four braking systems according to an execution parameter for execution of the deceleration task. 
     The parameter allocation unit  505  is configured to provide the category task parameter for at least one of the category executors. The parameter allocation unit  505  may send a command to the executor so that the executor executes a corresponding action, and may particularly send a previously determined category task parameter to a specific hardware executor. 
     In some embodiments of this application, the target parameter generation unit  502  may particularly perform at least one of the following: (1) Providing a target longitudinal trajectory parameter of the vehicle, the target longitudinal trajectory parameter being used for meeting a requirement for longitudinal motion of the vehicle. (2) Providing a target transverse trajectory parameter of the vehicle, the target transverse trajectory parameter being used for meeting a requirement for transverse motion of the vehicle. (3) Providing target parameters for mode setting of the vehicle, for example, including accelerations in three directions and angular velocities in the three directions. Compared with the longitudinal trajectory tracking service and the transverse trajectory tracking service, the six-degree-of-freedom mode service also takes requirement in the normal direction into consideration. (4) Providing a target parameter for gear setting of the vehicle. 
     In some embodiments of this application, the execution parameter generation unit  503  may particularly perform at least one of the following: (1) Determining a manual operation required torque. (2) Determining an acceleration required torque or an execution parameter requested for parking (for example, a braking system parameter and a gear selection parameter). (3) Determining a yaw motion required torque. (4) Determining a slip rate required torque. (5) Determining a normal torque, a pitch torque, and a roll control torque. 
     In some embodiments of this application, the category parameter generation unit  504  may particularly perform at least one of the following: (1) allocating a torque control category task parameter to a driving category executor; (2) allocating a braking category task parameter to a braking category executor; (3) allocating a parking braking category task parameter to a parking braking category executor; (4) allocating a gear control category task parameter to a gear control category executor; (5) allocating a steering category task parameter to a steering assistance category executor; (6) allocating a suspension adjustment category task parameter to a suspension control category executor; (7) allocating a torque control category task parameter to a motor torque category executor; (8) allocating a braking category task parameter to a braking slip rate control category executor; (9) allocating a vehicle body height adjustment category task parameter to a vehicle body height adjustment category executor; and (10) allocating a normal force control category task parameter to a suspension control category executor. 
     In some embodiments of this application, the parameter allocation unit  505  may particularly perform at least one of the following: (1) Providing an actual torque control task parameter for at least one (for example, a front motor or a rear motor) of driving category executors. (2) Providing an actual braking task parameter for at least one (for example, a four-wheel braking system) of braking category executors. (3) Providing an actual steering task parameter (for example, a torque and an angle) for at least one (for example, an electric power steering system) of steering assistance category executors. (4) Providing an actual vehicle body height adjustment task parameter for at least one (for example, an air spring) of vehicle body height adjustment category executors. (5) Providing an actual normal force control task parameter for at least one of suspension control category executors. 
     The above description is merely illustrative of specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any feasible variation or replacement conceived by a person skilled in the art within the technical scope disclosed in this application shall fall within the scope of protection of this application. In the case of no conflict, the embodiments of this application and features in the embodiments may also be combined with each another. The scope of protection of this application shall be subject to recitations of the claims.