Vehicle control method and apparatus
The road characteristics and scene recognition are obtained through the vehicle control device, and the torque control parameters of the vehicle are adjusted adaptively, solving the stability problems caused by changes in adhesion of new energy vehicles in complex road environments, and improving driving smoothness and comfort.
Patent Information
- Application Number
- PCT/CN2024/094964
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-25
- Filing Date
- 2024-05-23
- Publication Date
- 2024-11-28
AI Technical Summary
In complex road environments, especially when bumpy potholes, speed bumps and ice and snowy sections, changes in road adhesion cause vehicles to easily get jerks, slip, tail swings or insufficient steering, affecting driving smoothness and comfort.
The road surface characteristics are obtained through the vehicle control device, the scene is identified and the target torque control information is determined, the motor output torque and other control parameters are adjusted to adaptively adjust the vehicle's driving parameters to ensure smoothness and stability.
Effectively reduce the instability of the vehicle under complex road conditions, improve driving experience and driving stability, and ensure the smoothness and comfort of the vehicle.
Smart Images

Figure CN2024094964_28112024_PF_FP_ABST
Abstract
Description
Vehicle control method and device
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on May 25, 2023, with application number 202310609829.0 and application name "A Vehicle Control Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field
[0003] The present application relates to the field of vehicle technology, and in particular to a vehicle control method and device. Background Art
[0004] At present, the development of new energy vehicles has attracted great attention from all countries. Among them, vehicles represented by new energy vehicles usually control the vehicle's driving by controlling the output torque of the motor.
[0005] However, in real-world driving, the road environment is highly complex. When a vehicle traverses unusual surfaces, such as bumps, potholes, speed bumps, and icy or snowy sections, sudden changes in road adhesion can make the vehicle more susceptible to instability. If the control parameters of relevant vehicle components (such as the motor's output torque) fail to respond and adjust promptly to sudden changes in road adhesion, the vehicle can experience a noticeable jerk or forward movement, or even skid, tailspin, or understeer (or oversteer), impacting ride smoothness and comfort, resulting in a poor driving experience.
[0006] Therefore, how to adaptively adjust the control parameters of vehicle-related components to ensure the smoothness and comfort of vehicle driving remains an important issue that needs to be solved urgently.
[0007] Summary of the Invention
[0008] The embodiments of the present application provide a vehicle control method and device for adaptively adjusting control parameters of vehicle-related components to ensure smoothness and comfort of vehicle driving.
[0009] On the one hand, the embodiment of the present application provides a vehicle control method, which can be implemented by a vehicle control device, which can be deployed on the vehicle side, for example, it can be a vehicle control unit (VCU) or a vehicle domain controller (VDC) for controlling the whole vehicle, or it can be an intelligent driving domain control unit or a mobile data center (MDC) for realizing intelligent driving or assisted driving functions. The embodiment of the present application does not limit the product form of the vehicle control device. The vehicle has the function of driving the vehicle with an electric motor, and can be a pure electric vehicle, a hybrid electric vehicle, a two-wheel drive electric vehicle, or a four-wheel drive electric vehicle. The embodiment of the present application does not limit the driving mode of the vehicle.
[0010] In specific implementation, the method may include: obtaining road surface characteristics of a first area, wherein the first area includes an area that the vehicle will enter at a first moment in the future; determining target torque control information based on the road surface characteristics; and controlling the vehicle's travel based on the target torque control information.
[0011] For example, the target torque control information may include a target torque control strategy from one or more torque control strategies associated with the road surface characteristics of the first region. Alternatively, the target torque control information may include adjusted values of corresponding control parameters calculated based on the target torque control strategy. The present embodiment does not limit the content of the target torque control information.
[0012] Through the above method, the vehicle control device can adaptively determine the vehicle's target torque control information by acquiring the road surface characteristics of the first area, thereby adaptively adjusting the vehicle's relevant control parameters. In this way, when the vehicle control device provides the adjusted control parameters to the corresponding components of the vehicle, it can assist in safe driving of the vehicle, thereby ensuring smooth and stable driving.
[0013] It is worth noting that in the embodiment of the present application, if the vehicle is about to enter a paved road at the first moment, the first area may include the lane area or parking space that the vehicle is about to enter. If the vehicle is about to enter an unpaved road at the first moment, such as an empty area without a lane or parking space, or an off-road road, the first area may include any area where the vehicle is allowed to pass. The embodiment of the present application does not limit the specific scope of the first area.
[0014] In combination with the first aspect, in a possible implementation, determining the target torque control information based on the road surface characteristics includes: identifying a first scenario in which the vehicle is located based on the road surface characteristics; and determining the target torque control information based on at least one torque control strategy associated with the first scenario.
[0015] Through the above method, road surface features, scenes and at least one torque control strategy can be associated in advance. During specific implementation, the vehicle control device can determine the first scene the vehicle is currently in based on the association between the identified road surface features and scenes, and thus can determine the target torque control information based on the torque control strategy associated with the first scene.
[0016] The scenario matching scheme described herein is merely an example of how target torque control information is determined in accordance with an embodiment of the present application and is not intended to be limiting. In other embodiments, road surface features may be pre-associated with at least one torque control strategy. After identifying the road surface features, the vehicle control device may determine the target torque control information based on the association between the road surface features and the at least one torque control strategy. This embodiment of the present application is not limiting in this regard.
[0017] In combination with the first aspect, in a possible implementation, the method may further include: determining at least one torque control strategy associated with the first scenario according to any one of the following methods: determining at least one torque control strategy associated with the first scenario based on first information, wherein the first information is used to describe the association relationship (or mapping relationship) between different road scenarios and different torque control strategies; or, determining at least one torque control strategy associated with the first scenario based on a first parameter value associated with the first scenario, wherein the first parameter value is used to characterize the degree of influence of the road surface characteristics of the first area on the driving stability of the vehicle.
[0018] Through the above method, the vehicle control unit can determine the torque control strategy associated with the first scenario based on the first information pre-stored on the storage medium accessible to the vehicle control device, or determine the torque control strategy associated with the first scenario by evaluating the first parameter value associated with the first scenario, so as to improve the overall vitality of the vehicle control scheme.
[0019] In conjunction with the first aspect, in one possible implementation, the first parameter value includes a road adhesion coefficient and / or a slip ratio. In other embodiments, the first parameter value may also be replaced with the value of other parameters that affect the driving stability or safety of the vehicle, which is not limited in this embodiment of the present application.
[0020] In combination with the first aspect, in one possible implementation, at least one torque control strategy associated with the first scenario is used to adjust at least one of the following control parameters: total torque value; torque gradient; inter-axle torque distribution ratio; or brake electro-hydraulic distribution ratio. Exemplarily, each torque control strategy is associated with an adjustment coefficient, and the adjustment coefficient is used to reduce the value of the control parameter to be adjusted by the torque control strategy. This is merely an example of the control parameters of the embodiment of the present application and is not intended to be limiting. In other embodiments, the vehicle control device can also adaptively adjust other control parameters, such as the vehicle's driving speed, steering wheel rotation angle, etc., to ensure the vehicle's driving stability, which is not limited in the embodiment of the present application.
[0021] In combination with the first aspect, in a possible implementation, the identifying the first scene in which the vehicle is located based on the road surface features includes: matching the road surface features with at least one item of scene information to identify the first scene, wherein the scene information is used to describe a road surface scene, the area corresponding to the first scene includes a first road surface feature, the second parameter value associated with the first road surface feature is greater than or equal to a first threshold, and the second parameter value is used to characterize the degree of influence of the first road surface feature on the driving stability of the vehicle.
[0022] Through the above method, the at least one item of scene information can be stored on a storage medium accessible to the vehicle control device, and the vehicle control device can match the identified road surface features with the at least one item of scene information to identify the first scene, so as to adopt at least one torque control strategy associated with the first scene to determine the target torque control information to assist vehicle driving.
[0023] In the embodiments of the present application, the scene information used to describe a road scene may be a scene name. The scene name may be named after a road feature, such as "speed bump," "manhole cover," "temperature crack," "pavement damage," "separated road surface," "flooded road surface," "wet epoxy coating," etc. Different road scenes may also have corresponding scene codes (or scene identifiers), which are not limited in the embodiments of the present application.
[0024] More fine-grained scenario information describing a road scene can include more than just the scene name. For example, each scene can be classified according to the degree to which different road characteristics affect the vehicle's driving stability. The scenario information can also include the road characteristics at different levels.
[0025] Taking the "speed bump" scenario as an example, scenarios can be categorized into "level 1 speed bump," "level 2 speed bump," and "level 3 speed bump" scenarios based on the speed bump's elevation. The corresponding elevation ranges are 0-X1 centimeters (cm), X1-X2 centimeters (cm), and X2-X3 centimeters (cm), respectively. X1, X2, and X3 represent elevation values, with X1 < X2 < X3. The scenario information corresponding to the level 1 speed bump scenario can be expressed as: speed bump, elevation, level 1, 0-X1 centimeters. The scenario information corresponding to the level 2 speed bump scenario can be expressed as: speed bump, elevation, level 2, X1-X2 centimeters. The scenario information corresponding to the level 3 speed bump scenario can be expressed as: speed bump, elevation, level 3, X2-X3 centimeters. After identifying the "speed bump" scenario, the vehicle control device can more precisely identify the speed bump's elevation value. By matching this elevation value with the elevation ranges for the different speed bump scenarios, the specific speed bump classification scenario can be determined. Target torque control information can then be determined using at least one torque control strategy associated with the corresponding classification scenario. A detailed description can be found in the specific implementation section, which will not be repeated here.
[0026] In conjunction with the first aspect, in one possible implementation, the method may further include: receiving the at least one item of scenario information from a cloud server; or receiving the at least one item of scenario information from a user equipment (UE). In other words, the vehicle control device may obtain the at least one item of scenario information through a variety of methods, including active requests by the vehicle control device or passive receipt by the vehicle control device, such as server configuration or manual configuration, which are not limited in this embodiment of the present application.
[0027] In combination with the first aspect, in a possible implementation, the method may further include: obtaining driving parameters of the vehicle; and identifying the first scene in which the vehicle is located based on the road surface characteristics includes: identifying the first scene in which the vehicle is located based on the road surface characteristics and the driving parameters.
[0028] Through the above method, whether the vehicle is actually traveling on a road surface that affects vehicle stability is also a very important factor in vehicle driving control. Therefore, the vehicle control device can also obtain the vehicle's driving parameters in order to combine the driving parameters to predict the vehicle's driving intention at a first moment in the future, so as to identify the first scene in which the vehicle is at the first moment. If the vehicle will actually travel on a road surface that affects vehicle stability at the first moment in the future, the vehicle control device can determine the target torque control information based on at least one torque control strategy associated with the first scene. If the vehicle will not actually travel on a road surface that affects vehicle stability at the first moment in the future, then the vehicle control device does not need to adaptively adjust the corresponding control parameters based on the road surface characteristics. In this way, the vehicle control device can more accurately identify the first scene in which the vehicle is located based on the road surface characteristics and the driving parameters.
[0029] In conjunction with the first aspect, in one possible implementation, the driving parameters may include, but are not limited to, at least one of the following: driving speed, wheel speed, yaw rate, longitudinal acceleration, roll angle, steering wheel angle, heading angle, accelerator pedal position, brake pedal position, gear position, driving mode, road mode, and battery state of charge (SOC). These are merely examples of driving parameters that may be required for predicting a vehicle's driving intent and are not intended to be limiting. In other embodiments, the driving parameters may also include other examples not shown, which are not detailed here.
[0030] In combination with the first aspect, in a possible implementation manner, acquiring the road surface characteristics of the first area includes: acquiring the road surface characteristics of the first area through at least one sensor associated with the vehicle.
[0031] In combination with the first aspect, in a possible implementation, controlling the vehicle driving according to the target torque control information includes: sending a control instruction to a target component of the vehicle, wherein the target component includes at least one of the following: a motor control unit, an electronic stability control system ESC, or a braking system.
[0032] This is merely an example of a target component of a vehicle and does not constitute any limitation. In other embodiments, the target component may have other names, or the control parameter may be replaced by other parameters, and accordingly, the target component may be replaced by a control component corresponding to other parameters, and this embodiment of the application does not limit this.
[0033] On the second aspect, the embodiments of the present application provide a vehicle control method, which can be implemented by a vehicle control device, which can be deployed on the vehicle side, for example, it can be a control unit for implementing vehicle control, such as the vehicle's VCU or VDC, or it can be a control unit for implementing intelligent driving or assisted driving functions, such as an intelligent driving domain control unit or MDC, etc. The embodiments of the present application do not limit the product form of the vehicle control device. The vehicle has the function of driving the vehicle with an electric motor, and can be a pure electric vehicle, a hybrid electric vehicle, a two-wheel drive electric vehicle, or a four-wheel drive electric vehicle. The embodiments of the present application do not limit the driving method of the vehicle.
[0034] In specific implementation, the method may include: obtaining first scene information, where the first scene information is used to indicate a first scene to which the vehicle belongs; determining target torque control information based on at least one torque control strategy associated with the first scene; and controlling the vehicle's travel based on the target torque control information.
[0035] Through the above method, the vehicle control device can obtain the first scenario information to understand the first scenario the vehicle is in, and then adaptively determine target torque control information based on at least one torque control strategy associated with the first scenario, thereby achieving adaptive adjustment of relevant control parameters of the vehicle. In this way, when the vehicle control device provides the adjusted control parameters to the corresponding components of the vehicle, it can assist in safe driving of the vehicle, thereby ensuring the smoothness and stability of the vehicle's driving.
[0036] In combination with the second aspect, in a possible implementation, the method may further include: determining at least one torque control strategy associated with the first scenario according to any one of the following methods: determining at least one torque control strategy associated with the first scenario based on first information, wherein the first information is used to describe the association between different road scenarios and different torque control strategies; or determining at least one torque control strategy associated with the first scenario based on a first parameter value associated with the first scenario, wherein the first parameter value is used to characterize the degree of influence of the road surface characteristics of the first area on the driving stability of the vehicle.
[0037] In combination with the second aspect, in a possible implementation manner, the first parameter value includes a road adhesion coefficient and / or a slip ratio.
[0038] In combination with the second aspect, in one possible implementation, at least one torque control strategy associated with the first scenario is used to adjust at least one of the following control parameters: total torque value; torque gradient; inter-axle torque distribution ratio; or brake electro-hydraulic distribution ratio.
[0039] In combination with the second aspect, in a possible implementation, each torque control strategy is associated with an adjustment coefficient, where the adjustment coefficient is used to reduce a value of a control parameter to be adjusted of the torque control strategy.
[0040] In combination with the second aspect, in a possible implementation method, obtaining the first scene information includes: receiving the first scene information from the intelligent driving domain control unit MDC, wherein the first scene is obtained based on road surface feature recognition in a first area, and the first area includes an area that the vehicle will enter at a first moment in the future.
[0041] In combination with the second aspect, in a possible implementation, the method also includes: obtaining driving parameters of the vehicle; obtaining the first scene information includes: performing scene recognition based on the driving parameters and road surface characteristics of the first area to obtain the first scene information, wherein the first area includes the area that the vehicle will enter at a first moment in the future.
[0042] In combination with the second aspect, in one possible implementation, the driving parameters may include but are not limited to at least one of the following: driving speed, wheel speed, yaw angular velocity, longitudinal acceleration, roll angle, steering wheel angle, heading angle, accelerator pedal opening information, brake pedal opening information, gear position, driving mode, road mode, and battery state of charge SOC.
[0043] In combination with the second aspect, in a possible implementation, controlling the vehicle driving according to the target torque control information includes: sending a control instruction to a target component of the vehicle, wherein the target component includes at least one of the following: a motor control unit, an electronic stability control system ESC, or a braking system.
[0044] In a third aspect, an embodiment of the present application provides a vehicle control device, comprising: an acquisition unit for acquiring road surface characteristics of a first area, wherein the first area includes an area that the vehicle will enter at a first moment in the future; a determination unit for determining target torque control information based on the road surface characteristics; and a control unit for controlling the vehicle's driving based on the target torque control information.
[0045] In combination with the third aspect, in a possible implementation, the determination unit is specifically used to: identify a first scene in which the vehicle is located based on the road surface characteristics; and determine the target torque control information based on at least one torque control strategy associated with the first scene.
[0046] In combination with the third aspect, in a possible implementation, the determination unit is also used to: determine at least one torque control strategy associated with the first scenario according to any one of the following methods: determine at least one torque control strategy associated with the first scenario based on the saved first information, wherein the first information is used to describe the association between different road scenarios and different torque control strategies; or determine at least one torque control strategy associated with the first scenario based on a first parameter value associated with the first scenario, wherein the first parameter value is used to characterize the degree of influence of the road surface characteristics of the first area on the driving stability of the vehicle.
[0047] In combination with the third aspect, in a possible implementation, the first parameter value includes a road adhesion coefficient and / or a slip ratio.
[0048] In combination with the third aspect, in one possible implementation, at least one torque control strategy associated with the first scenario is used to adjust at least one of the following control parameters: total torque value; torque gradient; inter-axle torque distribution ratio; or brake electro-hydraulic distribution ratio.
[0049] In combination with the third aspect, in a possible implementation, each torque control strategy is associated with an adjustment coefficient, where the adjustment coefficient is used to reduce a value of a control parameter to be adjusted of the torque control strategy.
[0050] In combination with the third aspect, in one possible implementation, the determination unit is specifically used to: match the road surface feature with at least one item of scene information to identify the first scene, wherein the scene information is used to describe a road surface scene, the area corresponding to the first scene includes a first road surface feature, the second parameter value associated with the first road surface feature is greater than or equal to a first threshold, and the second parameter value is used to characterize the degree of influence of the first road surface feature on the driving stability of the vehicle.
[0051] In combination with the third aspect, in a possible implementation, the device further includes: a transceiver unit, configured to receive the at least one item of scene information from a cloud server; or, receive the at least one item of scene information from a user equipment UE.
[0052] In combination with the third aspect, in a possible implementation, the acquisition unit is further used to: acquire the driving parameters of the vehicle; and the processing unit is specifically used to: identify the first scene in which the vehicle is located based on the road surface characteristics and the driving parameters.
[0053] In combination with the third aspect, in one possible implementation, the driving parameters include at least one of the following: driving speed, wheel speed, yaw angular velocity, longitudinal acceleration, roll angle, steering wheel angle, heading angle, accelerator pedal opening information, brake pedal opening information, gear position, driving mode, road mode, and battery state of charge SOC.
[0054] In combination with the third aspect, in a possible implementation manner, the acquisition unit is specifically configured to: acquire road surface features of the first area through at least one sensor associated with the vehicle.
[0055] In combination with the third aspect, in a possible implementation, the control unit is specifically used to: send a control instruction to a target component of the vehicle, wherein the target component includes at least one of the following: a motor control unit, an electronic stability control system ESC, or a braking system.
[0056] In a fourth aspect, an embodiment of the present application provides a vehicle control device, comprising: an acquisition unit for acquiring first scenario information, wherein the first scenario information is used to indicate a first scenario described by the vehicle; a determination unit for determining target torque control information based on at least one torque control strategy associated with the first scenario; and a control unit for controlling the vehicle driving according to the target torque control information.
[0057] In combination with the fourth aspect, in a possible implementation, the determination unit is also used to: determine at least one torque control strategy associated with the first scenario according to any one of the following methods: determine at least one torque control strategy associated with the first scenario based on the saved first information, wherein the first information is used to describe the association between different road scenarios and different torque control strategies; or determine at least one torque control strategy associated with the first scenario based on a first parameter value associated with the first scenario, wherein the first parameter value is used to characterize the degree of influence of the road surface characteristics of the first area on the driving stability of the vehicle.
[0058] In combination with the fourth aspect, in a possible implementation, the first parameter value includes a road adhesion coefficient and / or a slip ratio.
[0059] In combination with the fourth aspect, in one possible implementation, at least one torque control strategy associated with the first scenario is used to adjust at least one of the following control parameters: total torque value; torque gradient; inter-axle torque distribution ratio; or brake electro-hydraulic distribution ratio.
[0060] In conjunction with the fourth aspect, in a possible implementation, each torque control strategy is associated with an adjustment coefficient, where the adjustment coefficient is used to reduce a value of a control parameter to be adjusted of the torque control strategy.
[0061] In combination with the fourth aspect, in a possible implementation method, the acquisition unit is specifically used to: receive the first scene information from the intelligent driving domain control unit MDC, wherein the first scene is obtained based on road surface feature recognition in a first area, and the first area includes an area that the vehicle will enter at a first moment in the future.
[0062] In combination with the fourth aspect, in a possible implementation, the acquisition unit is also used to obtain the driving parameters of the vehicle; the acquisition unit obtains the first scene information, including: performing scene recognition based on the driving parameters and the road surface characteristics of the first area to obtain the first scene information, wherein the first area includes the area that the vehicle will enter at a first moment in the future.
[0063] In combination with the fourth aspect, in one possible implementation, the driving parameters include at least one of the following: driving speed, wheel speed, yaw angular velocity, longitudinal acceleration, roll angle, steering wheel angle, heading angle, accelerator pedal opening information, brake pedal opening information, gear position, driving mode, road mode, and battery state of charge SOC.
[0064] In combination with the fourth aspect, in a possible implementation, controlling the vehicle driving according to the target torque control information includes: sending a control instruction to a target component of the vehicle, wherein the target component includes at least one of the following: a motor control unit, an electronic stability control system ESC, or a braking system.
[0065] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a processor, which is coupled to a memory: the processor is used to execute a computer program or instruction stored in the memory, so that the electronic device executes the method described in the first aspect and any possible implementation of the first aspect, or causes the electronic device to execute the method described in the second aspect and any possible implementation of the second aspect.
[0066] In a sixth aspect, an embodiment of the present application provides a vehicle comprising a unit for implementing the method described in the first aspect and any possible implementation of any item of the first aspect, or comprising a unit for implementing the method described in the second aspect and any possible implementation of the second aspect.
[0067] In the seventh aspect, an embodiment of the present application provides a communication device, comprising at least one processor and an interface circuit, wherein the interface circuit is used to provide data or code instructions to the at least one processor, and the at least one processor is used to implement the method as described in the first aspect and any possible implementation of the first aspect through a logic circuit or executing code instructions, or to implement the method as described in the second aspect and any possible implementation of the second aspect.
[0068] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable medium stores a program code. When the program code runs on a computer, the computer executes the method as described in the first aspect and any possible implementation of the first aspect, or the computer executes the method as described in the second aspect and any possible implementation of the second aspect.
[0069] In the ninth aspect, an embodiment of the present application provides a computer program product, which, when running on a computer, enables the computer to execute the method described in the first aspect and any possible implementation of the first aspect, or enables the computer to execute the method described in the second aspect and any possible implementation of the second aspect.
[0070] In a tenth aspect, an embodiment of the present application provides a terminal device, comprising a unit for implementing the method described in the first aspect and any possible design of the first aspect, or a unit for implementing the method described in the second aspect and any possible design of the second aspect. By way of example, the terminal device includes, but is not limited to: intelligent transportation equipment (such as cars, ships, drones, trains, trucks, etc.), intelligent manufacturing equipment (such as robots, industrial equipment, intelligent logistics, smart factories, etc.), and intelligent terminals (mobile phones, computers, tablet computers, PDAs, desktops, headphones, speakers, wearable devices, vehicle-mounted devices, etc.).
[0071] Based on the implementations provided in the above aspects, the embodiments of the present application can be further combined to provide more implementations.
[0072] The technical effects that can be achieved by any possible implementation method in any of the second to tenth aspects mentioned above can be referred to the description of the technical effects that can be achieved by any possible implementation method in any of the first aspect mentioned above, and the repetitions will not be discussed. BRIEF DESCRIPTION OF THE DRAWINGS
[0073] FIG1 is a schematic diagram showing an application scenario to which an embodiment of the present application is applicable;
[0074] FIG2 is a schematic diagram showing the principle of a vehicle control method according to an embodiment of the present application;
[0075] FIG3 is a schematic flow chart of a vehicle control method according to an embodiment of the present application;
[0076] 4 to 6 are schematic diagrams showing a first area located on a road according to an embodiment of the present application;
[0077] FIG7 shows a schematic diagram of a first area located in a parking space according to an embodiment of the present application;
[0078] FIG8 is a schematic diagram showing road surface features that affect vehicle driving stability according to an embodiment of the present application;
[0079] 9 to 12 are schematic diagrams showing adjustment control parameters according to an embodiment of the present application;
[0080] FIG13 is a schematic diagram showing a first scenario identified by combining driving parameters of a vehicle according to an embodiment of the present application;
[0081] FIG14 shows a schematic structural diagram of a vehicle control device according to an embodiment of the present application;
[0082] FIG15 shows a schematic diagram of another vehicle control device according to an embodiment of the present application. DETAILED DESCRIPTION
[0083] The embodiments of the present application provide a vehicle control method and device for adaptively adjusting the control parameters of vehicle-related components to ensure the smoothness and comfort of vehicle driving. The method and the device are based on the same technical concept. Since the principles of the method and the device for solving problems are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated. In addition, in the various embodiments of the present application, unless otherwise specified and there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form a new embodiment according to their internal logical relationships.
[0084] The vehicle control scheme in the embodiment of the present application can be applied to the Internet of Vehicles, such as vehicle to everything (V2X), long term evolution-vehicle (LTE-V), vehicle to vehicle (V2V), etc. For example, it can be applied to a vehicle with a driving mobile function, or other devices in a vehicle with a driving mobile function. The other devices include but are not limited to: other sensors such as an on-board terminal, an on-board control unit, an on-board module, an on-board module, an on-board component, an on-board chip, an on-board unit, an on-board radar or an on-board camera. The vehicle can implement the vehicle control method provided in the embodiment of the present application through the on-board terminal, the on-board control unit, the on-board module, the on-board module, the on-board component, the on-board chip, the on-board unit, the on-board radar or the on-board camera. Of course, the control scheme in the embodiment of the present application can also be used for other intelligent terminals with mobile control functions other than the vehicle, or be set in other intelligent terminals with mobile control functions other than the vehicle, or be set in a component of the intelligent terminal. The intelligent terminal can be an intelligent transportation device, an intelligent home device, a robot, etc. For example, it includes but is not limited to smart terminals or control units, chips, radars, cameras and other sensors, and other components within smart terminals.
[0085] In the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.
[0086] Furthermore, unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish between multiple objects and are not used to define the priority or importance of multiple objects. For example, "first indication information" and "second indication information" are only used to distinguish different indication information, and do not indicate a difference in priority or importance between the two indication information.
[0087] The following describes the embodiments of the present application in conjunction with the accompanying drawings.
[0088] FIG1 is a schematic diagram of an application scenario applicable to an embodiment of the present application. This application scenario may include a vehicle 100. In one possible implementation, this application scenario may also include a cloud server 200, and the vehicle 100 and cloud server 200 may communicate via a network. In one embodiment, cloud server 200 may also be implemented as a virtual machine.
[0089] Some or all functions of the vehicle 100 are controlled by a computing platform 150 (or computer system). The computing platform 150 may include at least one processor 151, which may execute instructions 153 stored in a non-transitory computer-readable medium such as a memory 152. In some embodiments, the computing platform 150 may also be a plurality of computing devices that control individual components or subsystems of the vehicle 100 in a distributed manner. The processor 151 may be any conventional processor, such as a central processing unit (CPU). Alternatively, the processor 151 may also include a graphics processing unit (GPU), a field programmable gate array (FPGA), a system on chip (SoC), an application specific integrated circuit (ASIC), or a combination thereof.
[0090] Alternatively, the vehicle 100 may be a car, truck, motorcycle, bus, boat, airplane, helicopter, lawn mower, recreational vehicle, amusement park vehicle, construction equipment, tram, golf cart, train, etc., which is not particularly limited in this embodiment of the present application. In one possible implementation, the vehicle 100 may be an electric vehicle (EV), such as a two-wheel drive electric vehicle or a four-wheel drive electric vehicle, which is not particularly limited in this embodiment of the present application.
[0091] The structure of the vehicle in FIG1 should not be understood as limiting the embodiments of the present application.
[0092] The vehicle control method of the embodiment of the present application can be implemented by a vehicle control device, which can be an independent device, a chip or component in the vehicle 100 shown in Figure 1, or a software module, which can be deployed on the relevant on-board equipment of the vehicle 100. The embodiment of the present application does not limit the product form and deployment method of the vehicle control device. In the following, for the sake of ease of understanding and description, the vehicle control scheme of the embodiment of the present application will be introduced by taking the vehicle control device as an intelligent driving domain control unit (such as a mobile data center (MDC)) of the computing platform 150 integrated in the aforementioned vehicle 100, or a vehicle control unit (VCU), or a vehicle domain controller (VDC) as an example.
[0093] The following describes the vehicle control scheme of the embodiment of the present application.
[0094] FIG2 shows a schematic diagram of the principle of the vehicle control method of an embodiment of the present application. Referring to FIG2 , taking the vehicle control device (equivalent to the vehicle control decision in FIG2 ) integrated in the MDC of the vehicle as an example, the MDC can interact with the cloud server or other modules in the vehicle to implement the vehicle control solution of the embodiment of the present application. Alternatively, taking the vehicle control device integrated in the VDC or VCU of the vehicle as an example, the VDC or VCU can interact with the cloud server or other modules in the vehicle to implement the vehicle control solution of the embodiment of the present application.
[0095] In one example, the MDC can obtain perception data of the vehicle's environment through the vehicle's sensor system, and keep monitoring and collecting data on the vehicle's surroundings at all times. The sensor system may include, but is not limited to, a camera, light detection and ranging (LIDAR), millimeter-wave radar (RADAR), or other sensor devices. The perception data obtained by the MDC through the sensor system may include: an image or video of the vehicle's current surroundings, a target object identified based on the image or video, and the distance (or interval) between the vehicle and the identified target object. The MDC can match these perception data with at least one stored scene information to identify the scene in which the vehicle is located. If the identified scenario indicates that the vehicle's current position or the position in front of the vehicle that the vehicle is about to enter (including lane areas, parking spaces, or unpaved roads, etc.) has road features that affect the vehicle's driving stability, the MDC can instruct the VDC (or VCU, which will not be distinguished or detailed one by one in the following description) to dynamically make vehicle control decisions based on the scenario, so as to dynamically adjust the control parameters of relevant components of the vehicle (such as the output torque of the motor, etc.), assist in controlling the vehicle's safe driving, and thus ensure the vehicle's driving stability and driving experience.
[0096] In specific implementation, a scenario can usually be associated with one or more torque control strategies. If the MDC can directly connect to the relevant components of the vehicle through the vehicle communication network (such as a gateway) and issue control instructions, the MDC can issue control instructions to the relevant components of the vehicle based on the one or more torque control strategies associated with the identified scenario, so that the relevant components of the vehicle can assist in controlling the safe driving of the vehicle according to the received control instructions. Alternatively, if the MDC and the relevant components of the vehicle need to be connected through the VDC (or VCU), the MDC can indicate the scenario to the VDC (or VCU), and the VDC (or VCU) can allocate torque to the relevant components of the vehicle or adjust other control parameters based on the one or more torque control strategies associated with the scenario. The VDC (or VCU) can issue control instructions to the relevant components of the vehicle through the in-vehicle communication network (or gateway), so that the relevant components of the vehicle can assist in controlling the safe driving of the vehicle according to the control instructions from the VDC, thereby ensuring the vehicle's driving stability and driving experience. As an example, the relevant components of the vehicle may include a motor control unit (MCU), and the MCU may include a front axle motor control unit (denoted as MCU_F) or a rear axle motor control unit (denoted as MCU_R). Or, for example, the relevant components of the vehicle may include an electronic stability control system (ESC). Or, for example, the relevant components of the vehicle may include a braking system of the vehicle, specifically an integrated power brake (IPB), which may integrate an anti-lock brake system (ABS), ESP, an acceleration slip regulation (ASR) (also known as a traction control system), etc.
[0097] In the embodiment of the present application, the scene information is information used to describe at least one scene. At least one item of scene information can be pre-stored on a storage medium accessible to the MDC, VDC, or VCU. The storage medium can be a local storage device of the vehicle, or can be a cloud server. The embodiment of the present application does not limit this. In an optional embodiment, the operator can pre-design at least one associated scene information for different road sections based on crowdsourcing data. The vehicle control device can obtain at least one item of scene information associated with the road section from the cloud server in advance according to the direction of vehicle travel and the road section that the vehicle may enter. The embodiment of the present application does not limit the method for obtaining the at least one item of scene information. In subsequent embodiments, the scene information and the torque control strategy associated with the scene information will be introduced in detail in conjunction with the method flow, which will not be repeated here.
[0098] In an optional embodiment, the sensing system may further include, but is not limited to, a speed sensor, an acceleration sensor, an angular velocity sensor, a roll angle sensor, a steering wheel sensor, and other sensors. The perception data acquired by the vehicle's sensing system may further include vehicle driving parameters, such as driving speed, wheel speed, longitudinal (lateral) acceleration, yaw angular velocity, roll angle, steering wheel angle, heading angle, accelerator pedal opening information, brake pedal opening information, gear position, driving mode, road mode, battery state of charge (SOC), etc. The MDC / VDC / VCU may also acquire various driving parameters of the vehicle to which it belongs, and determine more accurate scenario information or a torque control strategy that is more suitable for the current situation based on the acquired various driving parameters, so that the MDC or VDC (or VCU) can allocate torque to relevant components of the vehicle or adjust control parameters of other components based on the determined torque control strategy.
[0099] In another optional embodiment, after determining the target torque control strategy, the MDC or VDC (or VCU) may also output a reminder message to a vehicle-associated touchscreen, speaker, or other peripheral device via the gateway to indicate the vehicle control decision result to the driver, thereby informing the driver of dynamic changes in relevant vehicle control parameters. The MDC or VDC or VCU may also receive control information from the vehicle driver via a touchscreen, microphone, or other peripheral device (or via the gateway). This control information may be associated with the aforementioned reminder message and may be used to assist the MDC or VDC or VCU in making vehicle control decisions.
[0100] In Figure 2, the bidirectional arrows between different modules are only used to indicate that the corresponding modules can communicate with each other, and do not limit any communication method or information format. The MDC or VDC (or VCU) can use different communication methods or information formats to communicate with different modules. The MDC or VDC (or VCU) can also have a protocol conversion or format conversion function, which is not limited in this embodiment of the present application. The other modules in the vehicle shown in Figure 2 are only examples. The dotted box only indicates that the corresponding module is an optional module. The vehicle may not contain some of the modules shown in Figure 2, or may include other modules in addition to some of the modules shown in Figure 2, or replace some of the modules in Figure 2 with other modules not shown. These will not be repeated here. In some designs, the vehicle's sensing system may also be integrated into any one of the MDC, VCU or VDC, or the VCU or VDC may also be integrated into the MDC. The embodiment of the present application does not limit the product form or integration method of the different modules of the vehicle.
[0101] The vehicle control method provided in the embodiment of the present application can be implemented in combination with the system architecture shown in FIG1 and FIG2 , as shown in FIG3 . The vehicle control method may include the following steps:
[0102] S310: A vehicle control device (eg, MDC, VDC, or VCU) obtains road surface features of a first area.
[0103] In an embodiment of the present application, a vehicle control device may be deployed on a vehicle, and the first area may include at least an area that the vehicle will enter at a first moment in the future. Specifically, if the vehicle is to enter a paved road at the first moment, the first area may include the lane area or parking space that the vehicle is to enter. If the vehicle is to enter an unpaved road at the first moment, such as an unoccupied area without a lane or parking space, or an off-road road, the first area may include any area where the vehicle is allowed to pass. The embodiment of the present application does not limit the specific scope of the first area.
[0104] In the embodiment of the present application, the entire vehicle may be regarded as a control unit, and the future "first moment" is relative to the entire vehicle. Specifically, when the vehicle is traveling forward, the first moment may be the arrival moment of the vehicle's front wheels at the first area in the future, or when the vehicle is traveling backward, the first moment may be the arrival moment of the vehicle's rear wheels at the first area in the future. In other embodiments, the front and rear wheels of the vehicle may be logically regarded as two independent devices. For example, the first moment may be the moment when the vehicle is traveling forward, the front wheels of the vehicle have entered the first area, but the rear wheels of the vehicle have not yet reached the first area, or the moment when the vehicle is traveling backward, the rear wheels of the vehicle have entered the first area, but the front wheels of the vehicle have not yet reached the first area. The embodiment of the present application does not limit this.
[0105] In one example, taking the example that the first area at least includes a lane area that the vehicle will enter at a first moment in the future, the implementation of the first area may be as follows:
[0106] As shown in Figure 4, taking a vehicle traveling in a single lane 1 as an example, the first area may include the area of lane 1 within a predetermined range in front of the vehicle's front end when the vehicle is moving in the direction of travel, as shown in the rectangular fill box in Figure 4. The width of the first area may be the same as the width of lane 1 (a preset width error is allowed), and the length of the first area may be pre-set, either as a numerical value (e.g., 10 meters) or as a length range (e.g., 5-15 meters). This embodiment of the application does not limit the scope of the first area.
[0107] Alternatively, as shown in Figure 5, if lane 1 is not a one-way lane, and there is lane 2 and / or lane 3 adjacent to lane 1 and in the same direction as lane 1 on the road where lane 1 is located, according to the driver's driving intention or the driving intention of the automatic driving, the vehicle may also change lanes while moving in the driving direction, such as changing lanes from lane 1 to lane 2 (i.e., changing lanes to the left) or from lane 1 to lane 3 (i.e., changing lanes to the right). In this case, the first area may include the area of lane 1 within a predetermined range in front of the vehicle's front when the vehicle is moving in the driving direction, as well as the area of lane 2 and / or lane 3.
[0108] As shown in the rectangular filled box in FIG5 , in case (1), if the vehicle changes lanes from lane 1 to lane 2, the first area may include the area of lane 1 within a predetermined distance in front of the vehicle head when the vehicle is moving in the direction of travel, and the area of lane 2. The width of the first area may be the same as the sum of the widths of lane 1 and lane 2 (a preset width error is allowed). The length of the first area may be pre-set, and may be a numerical value (e.g., 10 meters) or a length range (e.g., 5 meters to 15 meters). In case (2), if the vehicle changes lanes to lane 3, the first area may include the area of lane 1 within a predetermined distance in front of the vehicle head when the vehicle is moving in the direction of travel, and the area of lane 3. The width of the first area may be the same as the sum of the widths of lane 1 and lane 3 (a preset width error is allowed). The length of the first area may be pre-set, and may be a numerical value (e.g., 10 meters) or a length range (e.g., 5 meters to 15 meters). In situation (3), regardless of whether the vehicle changes lanes, the first area may also include the area of lane 1, the area of lane 2, and the area of lane 3 within a predetermined distance in front of the vehicle when the vehicle moves in the direction of travel. The width of the first area may be the same as the sum of the widths of lane 1, lane 2, and lane 3 (a preset width error is allowed). The length of the first area may be pre-set and may be a numerical value (e.g., 10 meters) or a length range (e.g., 5 meters to 15 meters).
[0109] The three situations in FIG5 are merely examples of the length or width of the first area and are not intended to be limiting. In actual applications, they can be adjusted according to actual needs or changes in road scenarios, which will not be described in detail here. In some designs, the lane change behavior of the vehicle can also be passive. For example, as shown in FIG6, when the road narrows or the number of lanes is reduced (for example, from 3 lanes to 2 lanes) or the road widens or the number of lanes increases (for example, from 2 lanes to 3 lanes) due to changes in the topological structure of the road on which the vehicle is located, the width of the first area can automatically narrow or widen as the road width changes. This will not be described in detail here.
[0110] In another example, taking the example that the first area includes at least a parking space that the vehicle will enter at a first moment in the future, the implementation of the first area may be as follows:
[0111] As shown in Figure 7 , if a vehicle needs to park in a parallel parking space on the roadside, or needs to enter a perpendicular parking space or an inclined parking space (e.g., with an inclination angle of θ) in a parking lot, the first area at least includes the target parking space to be entered by the vehicle. For example, the first area may also include the area that the vehicle may pass through from its current position to the target parking space. Conversely, if the vehicle is exiting a parking space, the first area may include the area of the lane within a predetermined range in front of the vehicle's front end as it moves forward in the direction of travel, as shown in Figure 4 .
[0112] The first area described in conjunction with the rectangular frame in Figures 4 to 7 is merely an example of the form of the first area and does not limit it in any way. In other embodiments, the first area may also be implemented as a fan-shaped area centered on the front of the vehicle, or an irregular shape, which is not limited in this embodiment of the present application. In actual applications, the road where the vehicle is located may also be an unpaved road, that is, the road / lane where the vehicle is allowed to pass may not have planned lane lines, or the parking space where the vehicle is allowed to park may not have planned parking space lines. The first area may be an area corresponding to a rectangular frame (or other shape) set according to experience, and the size of the rectangular frame may also be set based on experience, which is not limited in this embodiment of the present application.
[0113] When S310 is specifically implemented, the vehicle control device may obtain road surface characteristics of the first area through at least one sensor associated with the vehicle.
[0114] For example, the vehicle control device can collect environmental images or videos in front of or around the vehicle through a camera, and perform feature analysis, target recognition and processing on the image or video to extract the road surface features of the first area. The road surface features may include, for example, features of the road surface material, such as dusty road surface, asphalt road surface, cement concrete road surface, flooded road surface, icy road surface, wet epoxy road surface, etc. Different road surface materials may correspond to different road surface adhesion coefficients. Alternatively, the road surface features may also include target objects identified on the road surface in the first area (such as obstacles that affect vehicle passage or road objects such as manhole covers that affect vehicle driving stability), and the position, shape, size or other attribute information of the target object. In one possible embodiment, the vehicle control device may detect the distance information between the vehicle and the target object through a laser radar or a millimeter wave radar, and the distance information may also be used as an example of the road surface features of the first area.
[0115] S320: The vehicle control device determines target torque control information according to the road surface characteristics.
[0116] For example, when S320 is implemented, the vehicle control device may identify the first scene in which the vehicle is located based on the acquired road surface features of the first area, and determine the target torque control information based on at least one torque control strategy associated with the first scene.
[0117] The vehicle control device may obtain at least one item of scene information from an accessible storage medium (such as a local storage medium of the vehicle or a cloud server), and each item of scene information may be used to describe a road scene. The vehicle control device may match the road surface characteristics of the first area with the at least one item of scene information to identify whether the vehicle is in the first scene. The area corresponding to the first scene may include a first road surface characteristic, which may affect the driving stability of the vehicle. For example, the second parameter value may be used to characterize the degree of influence of the first road surface characteristic on the driving stability of the vehicle, and the second parameter value associated with the first road surface characteristic is greater than or equal to the first threshold.
[0118] For example, as shown in FIG8 , road surface features that affect the driving stability of the vehicle may include but are not limited to the following:
[0119] (1) Speed bumps, also known as speed reduction pads, are traffic facilities installed on roads to slow down passing vehicles. Speed bumps are generally in the shape of strips, but can also be dotted. Speed bumps can be made of rubber or metal. Speed bumps are generally yellow and black to attract visual attention, and slightly bulge the road surface to achieve the purpose of slowing down vehicles. They are generally installed at road intersections, industrial and mining enterprises, schools, residential communities, and other sections of roads where vehicles need to slow down and where traffic accidents are likely to occur. They are new types of traffic safety devices used to reduce the speed of motor vehicles and non-motor vehicles.
[0120] (2) Manhole covers are used to cover roads or deep wells to prevent people or objects from falling. Based on the material, they can be divided into metal manhole covers, high-strength fiber cement concrete manhole covers, resin manhole covers, etc. They are generally circular and can be deployed in green belts, sidewalks, motorway lanes, docks, alleys, etc.
[0121] (3) Temperature joints, generally referred to as building expansion joints (abbreviated as expansion joints), are structural joints installed at appropriate locations along the construction joint direction of a building or structure to prevent cracks or damage to building components (such as roads) due to climate temperature changes (thermal expansion or contraction, etc.). Expansion joints divide building components above the foundation, such as walls, floor slabs, and roofs (except wooden roofs), into two independent parts, allowing the building or structure to expand and contract horizontally along its length.
[0122] (4) Pavement damage, including structural damage and functional damage. Structural damage leads to a decrease in the bearing capacity of the pavement structure, which manifests itself in the form of various structural cracks. Functional damage affects driving quality and safety, manifesting as a decrease in pavement serviceability, flatness, and anti-skid performance. Generally, when structural damage increases to a certain extent, functional damage will also occur.
[0123] (5) Separated road surface, for example, due to the environment, weather (such as rain, snow, and ice), the road surface on different sides of the same lane presents different characteristics. For example, the left side of the same lane is icy, while the right side is not.
[0124] (6) Flooded road surface: a road surface where water accumulates after rain or watering due to uneven road surface.
[0125] (7) Coated epoxy floor (e.g. wet epoxy coating) is made of solvent-based or solvent-free epoxy resin and conductive materials. It has the advantages of anti-static, dust-proof, moisture-proof, bright, beautiful, wear-resistant, impact-resistant, and easy to clean. It is suitable for non-heavy-loaded industrial plants such as electronics factories, electrical appliance factories, machinery factories, chemical factories, pharmaceutical factories, textile factories, garment factories, food factories, beverage factories, cosmetic factories, packaging factories, plastic factories, tobacco factories, etc.; and all cement or terrazzo floors in warehouses, supermarkets, walkways, parking lots and other special places.
[0126] For the above-mentioned different road surface features, multiple scenarios (such as scenario modeling) can be pre-designed. Each scenario can be graded according to the intensity of the road surface features so that the vehicle control device can match the corresponding scenario according to the actual road surface features obtained.
[0127] For example, the multiple scenarios may be shown in Table 1 below:
[0128] Table 1
[0129] Among them, the "scenario code" can also be called the scenario identifier, which corresponds to a road scene. The "road feature" is a road feature associated with a road scene. The "grading basis" is the basis for dividing the degree to which different road features affect vehicle stability. "Level 1", "Level 2", and "Level 3" are different impact levels for different road scenes according to the grading basis. Different impact levels can be associated with one or more torque control strategies, and different torque control strategies have different requirements for the control parameters of related vehicle components.
[0130] For example, in the speed bump scenario, X1, X2, and X3 represent elevation values, where X1 < X2 < X3. In a speed bump scenario at level one, the speed bump is lower, causing less damage to the vehicle's suspension system, tires, and other components, allowing the vehicle to pass more smoothly, and requiring lower control parameters for the vehicle's related components. In contrast, in speed bump scenarios at level two or three, the speed bump is higher, causing greater damage to the vehicle's suspension system, tires, and other components. The vehicle experiences noticeable shaking or jolting when passing over the speed bump, resulting in a less stable passage and requiring higher control parameters for the vehicle's related components. The impacts of manhole cover scenarios, temperature crack scenarios, and damaged road surface scenarios on vehicle stability are similar to those of speed bumps and will not be further elaborated here.
[0131] Alternatively, for example, in a split road scenario, the road adhesion coefficients on a split road are uneven. The greater the difference in road adhesion coefficients, the higher the risk of the vehicle skidding and instability. By matching the identified split road to the corresponding level, the corresponding control parameters can be adjusted based on the control strategy for that level to minimize the risk of vehicle skidding.
[0132] Alternatively, take a flooded road scenario as an example. The road adhesion coefficient on flooded roads is extremely low. The larger the surface area of flooded road, the higher the risk of vehicle skidding and instability. The risk of skidding when both wheels are in contact with flooded road surface is higher than when only one wheel is in contact with flooded road surface. The impact of wet epoxy flooring on vehicle stability is similar to that of flooded road surface and will not be further elaborated here.
[0133] Table 1 is only an example of the scenario of the embodiment of the present application and is not intended to be limiting. In actual applications, more road features that affect vehicle stability can be obtained, and scenario modeling can be performed according to needs or actual road conditions. The basis for grading different road scenarios and the level types are not limited. In specific implementation, the road conditions are more complex depending on the scenario. Different road scenarios may have different features in the perception data. When the perception data recognizes the corresponding features, the scene ahead is considered to be the corresponding scene. The features may include but are not limited to: spectral bands, light intensity, laser radar point cloud geometry, ultrasonic frequency, characteristic frequency bands, etc. Similarly, the above features can also be classified based on different thresholds, which are called feature intensities, also known as the intensity of road features. Similar to Table 1, the road features can be graded in advance according to their intensity so that the corresponding control parameters can be adjusted according to the corresponding control strategies at different levels to ensure the smoothness and stability of vehicle driving. For detailed implementation details, please refer to the relevant description in conjunction with Table 1 above and will not be repeated here.
[0134] The vehicle control device can design control strategies for different control parameters based on relevant components of the vehicle, and determine the association relationship (or mapping relationship) between the scenarios shown in Table 1 and different control strategies, so that when the vehicle control device identifies the first scenario, it can determine one or more torque control strategies associated with the first scenario.
[0135] For example, the control strategies for different control parameters may include at least one of the following:
[0136] a. Total torque limit strategy;
[0137] b. Torque gradient limiting strategy;
[0138] c. Torque distribution strategy among four-wheel drive axles;
[0139] d. Hydraulic brake ratio adjustment strategy.
[0140] Among them, the adjustment object (i.e., control parameter) of the total torque value limitation strategy is the torque extreme value, the adjustment object of the torque gradient limitation strategy is the torque gradient, the adjustment object of the four-wheel drive inter-axle torque distribution strategy is the inter-axle torque distribution ratio, and the adjustment object of the hydraulic brake proportion adjustment strategy is the brake electro-hydraulic distribution ratio. The calculation formulas used can conform to the following expressions (1)-(4):
[0141] Control strategy a: Adjusted torque extreme value = K*(1-LEVEL*5%)*original torque extreme value (1);
[0142] Control strategy b: Adjusted torque gradient = K*(1-LEVEL*5%)*original torque gradient (2);
[0143] Control strategy c: Adjusted torque distribution ratio = K*(1-LEVEL*5%)*original torque distribution ratio (3);
[0144] Control strategy d: adjusted electro-hydraulic distribution ratio = K*(1-LEVEL*5%)*original electro-hydraulic distribution ratio (4);
[0145] Based on the above control strategy, at least one torque control strategy associated with the first scenario can be used to adjust at least one of the following control parameters: total torque value (or torque extreme value); torque gradient; inter-axle torque distribution ratio; or brake electro-hydraulic distribution ratio.
[0146] The torque extreme value can be used as an example of target torque control information. The output component of the torque extreme value can be a VDC or VCU, and the corresponding controlled component can be a motor control unit and its motor. The torque gradient can be used as an example of target torque control information. The output component of the torque gradient can be a VDC or VCU, and the corresponding controlled component can be a motor control unit and its motor. The inter-axle torque distribution ratio can be used as an example of target torque control information. The output component of the inter-axle torque distribution ratio can be a VDC or VCU, and the corresponding controlled component can be a front axle motor control unit and its motor, or a rear axle motor control unit and its motor. The brake electro-hydraulic distribution ratio can be used as an example of target torque control information. The output component of the brake electro-hydraulic distribution ratio can be a VDC or VCU, and the corresponding controlled component can be a front axle motor control unit and its motor, or a rear axle motor control unit and its motor. "K*(1-LEVEL*5%)" can be used as an adjustment coefficient. "K", "LEVEL", or "5%" can be designed as required and are not limited in this embodiment of the application.
[0147] Based on the different road scenarios and different torque control strategies designed above, in specific implementation, the vehicle control device may determine at least one torque control strategy associated with the first scenario according to any of the following methods:
[0148] Method (1): Determine at least one torque control strategy associated with the first scenario based on first information, wherein the first information is used to describe the association between different road scenarios and different torque control strategies.
[0149] Method (2): Determine at least one torque control strategy associated with the first scenario based on a first parameter value associated with the first scenario, wherein the first parameter value is used to characterize the degree of influence of the road surface characteristics of the first area on the driving stability of the vehicle.
[0150] The above-mentioned method (1) is a pre-configured method. The stored first information may be a preferred strategy or strategy combination selected for a scenario after designing multiple sets of strategy combination tests for different road scenarios and different scenario feature levels. In this method, the association between the scenario and the torque control strategy is fixed, and the vehicle control device can directly use this association to determine at least one torque control strategy associated with the first scenario.
[0151] For example, the first information may be as shown in Table 2 or Table 3 below:
[0152] Table 2
[0153] Table 3
[0154] Among them, the scene K value represents an adjustment coefficient associated with the scene. The level (LEVEL) (1 to 3) in Table 3 represents the first, second or third level divided into different road scenes in Table 1, such as "1" represents the first level, "2" represents the second level, and "3" represents the third level. The control strategy (a to d) represents the control strategy for different control parameters described above. The control strategy corresponding to the row where the scene code AG is located is a combination of at least one control strategy in the control strategy (a to d). For example, the control strategy of the row where the scene code A is located is a combination of the hydraulic brake ratio adjustment strategy (d) and the torque distribution strategy (c) between the four-wheel drive shafts. Other combinations are similar and will not be repeated here.
[0155] When applying Table 2 or Table 3 above, taking the example of MDC performing scene recognition and controlling the vehicle through VDC, after identifying the first scene (or key scene), MDC can determine the flag bit associated with the first scene, which can include, for example, a scene code, or a scene code + level. MDC can send the flag bit associated with the first scene as the first scene information to VDC to indicate to VDC the first scene in which the vehicle is located. VDC can determine at least one torque control strategy (or target torque control strategy) associated with the first scene based on the flag bit and Table 2 or Table 3 above. Further, VDC can determine the target torque control information based on the at least one torque control strategy associated with the first scene.
[0156] Taking the first scenario as a level 1 speed bump scenario as an example, the target torque control strategy can be used to reduce (or suppress) the torque gradient and limit the torque extreme value during the normal driving stage or the energy recovery stage. After the VDC receives the flag indicating the level 1 speed bump scenario, it adjusts the torque gradient and torque extreme value accordingly. The changes can be shown in Figure 9, where different dotted line segments represent the adjusted parameter values. Based on the adjusted torque gradient and torque extreme value, the driver (or the on-board terminal of an autonomous driving vehicle, etc.) can autonomously adjust and control the torque within the limit value. Thus, by limiting the torque extreme value, vehicle instability caused by excessive torque can be prevented. By limiting the torque gradient, vehicle instability caused by excessive torque gradient can be prevented.
[0157] Taking the first scenario, a Level 1 separation road scenario, as an example, the target torque control strategy can be used to adjust the torque distribution ratio between axles. After the VDC receives the flag indicating a Level 1 separation road, it adjusts the torque distribution ratio between axles. For example, when driving, the driving torque is distributed based on the axle load, and the torque originally superimposed on the rear axle motor control unit (as shown by the solid arrows in Figure 10) is redistributed and dynamically distributed to the front axle motor control unit and the rear axle motor control unit (as shown by the dotted arrows in Figure 10), thereby ensuring better driving stability. Or, for example, when coasting recovery, the braking recovery torque is redistributed, and the torque originally superimposed on the rear axle motor control unit (as shown by the solid arrows in Figure 11) is redistributed and dynamically distributed to the front axle motor control unit and the rear axle motor control unit (as shown by the dotted arrows in Figure 11), so as to achieve a more ideal braking recovery torque distribution as much as possible.
[0158] Taking the first scenario as a level 1 wet epoxy floor scenario as an example, the target torque control strategy can be used to adjust the brake electro-hydraulic distribution ratio. After the VDC receives the mark position representing the level 1 wet epoxy floor scenario, it adjusts the brake electro-hydraulic distribution ratio. For example, as shown in Figure 12, before the adjustment, the electric braking ratio may be higher, and after the adjustment, the electric braking ratio may be limited so that the hydraulic braking ratio is higher. In other embodiments, the electric braking torque of the cooperative regenerative brake system (CRBS) electro-hydraulic coordination system can also be completely prohibited and only the coasting recovery part is retained, but the total braking torque is not changed, which will not be repeated here. Based on the adjusted electro-hydraulic distribution ratio, the driver (or the on-board terminal of the autonomous driving vehicle, etc.) depresses the brake pedal to autonomously adjust and control the total braking torque to ensure the smoothness and stability of the vehicle's driving.
[0159] The above-mentioned method (2) is an intelligent adaptation method. In this method, the vehicle control device can be a device with intelligent analysis functions. For example, it can use the various information obtained to analyze and obtain the first parameter value associated with the first scenario. The first parameter value can be, for example, the road adhesion coefficient and / or slip rate. The higher the first parameter value, the more serious the impact of the corresponding road surface on the vehicle's driving stability, and the more control parameters need to be adjusted. The vehicle control device can intelligently adapt at least one torque control strategy for the first scenario with the goal of reducing the impact of the road surface characteristics in the area corresponding to the first scenario on the vehicle's driving stability, so that after adjusting the control parameters of the vehicle-related components based on the at least one torque control strategy, the vehicle can drive safely.
[0160] As an example, during specific implementation, different first parameter value intervals and torque control strategies that can be adapted to each value interval can be pre-designed. The vehicle control device can adapt at least one torque control strategy for the first scenario based on the value interval corresponding to the first parameter value associated with the first scenario actually obtained. Taking the slip ratio as an example, the pre-designed first parameter value intervals can include, for example, 20%-40%, 40%-60%, and 60%-80%. The interval 20%-40% can be associated with the aforementioned control strategy c, or d, or c+d. The interval 40%-60% can be associated with, for example, the aforementioned control strategies a+c, or a+d, or b+d, or b+c, or a+c+d, or b+c+d. The interval 60%-80% can be associated with, for example, the aforementioned control strategy a+b+c+d.
[0161] Taking the "speed bump" scenario shown in Table 1 as an example, as the vehicle's front wheels pass over the speed bump, the slip rate of the corresponding axle will suddenly change, reaching, for example, 30%. To effectively control the continued increase in slip rate, the vehicle control device can adapt control strategy c for this scenario to distribute the torque of the axle corresponding to the front wheel that has already passed the speed bump to the axle with the same slip rate, thereby ensuring that the total torque value remains unchanged. When applying control strategy c to transfer and redistribute torque between axles, during braking, a higher hydraulic braking ratio can effectively suppress the increase in slip rate, while a lower electric braking ratio can effectively reduce the risk of instability.
[0162] In method (2), the specific decision-making process based on at least one torque control strategy associated with the first scenario is similar to the solution introduced in the previous text in combination with method (1). For specific implementation details, please refer to the relevant description of the previous text in combination with method (1), which will not be repeated here.
[0163] It is worth noting that, because the actual driving conditions of a vehicle are very complex, in order to more accurately ensure the smoothness and comfort of the vehicle's driving, in another optional embodiment, the vehicle control device (e.g., VDC or VCU) may also obtain the vehicle's driving parameters, which may include but are not limited to at least one of the following: driving speed, wheel speed, yaw angular velocity, longitudinal acceleration, roll angle, steering wheel angle, heading angle, accelerator pedal opening information, brake pedal opening information, gear position, driving mode, road mode, and battery state of charge (SOC). When implementing the above S320, the vehicle control device may specifically identify the first scene in which the vehicle is located based on the road surface characteristics and the driving parameters.
[0164] For example, as shown in situation (1) in FIG13 , taking the first area including lane 1 where the vehicle is located and the area in front of adjacent lanes 2 and 3 as an example, even if the road surface of lane 2 includes a manhole cover, it corresponds to scenario B shown in Table 1. Although the vehicle control device can identify scenario B based on the perception data, when it is predicted that the vehicle has no intention to change lanes based on the vehicle's driving parameters (such as steering wheel angle, yaw angular velocity, steering wheel angle, longitudinal acceleration, lateral acceleration, vehicle speed, etc.), the manhole cover on lane 2 will not affect the stability of the vehicle traveling on lane 1. Therefore, based on the road surface characteristics of the first area and the vehicle's driving parameters, the vehicle control device can still confirm that the area of lane 1 that the vehicle enters at the first moment in the future is not the scenario shown in Table 1, and there is no need to adjust the control parameters of the relevant vehicle components for the time being.
[0165] As shown in situation (2) in Figure 13, taking the first area including lane 1 where the vehicle is located and the area in front of adjacent lanes 2 and 3 as an example, if the road surface in front of lane 2 includes a manhole cover, it corresponds to scenario B shown in Table 1, and if the road surface in front of lane 1 includes a speed bump, it corresponds to scenario A shown in Table 1. Although the vehicle control device can identify scenarios A and B based on the perception data, when it is predicted that the vehicle currently has the intention to change lanes from lane 1 to lane 2 based on the vehicle's driving parameters (such as steering wheel angle, yaw angular velocity, steering wheel angle, longitudinal acceleration, lateral acceleration, vehicle speed, etc.), the manhole cover on lane 2 is more likely to affect the stability of the vehicle. Therefore, based on the road surface characteristics of the first area and the vehicle's driving parameters, the vehicle control device can use scenario A as the first scenario and determine the target torque control information based on the first scenario.
[0166] As shown in situation (3) in Figure 13, taking the first area including the area in front of lane 1 where the vehicle is located as an example, if the road surface in front of lane 1 includes a manhole cover and a speed bump, they correspond to scenario A and scenario B shown in Table 1, respectively. Although the vehicle control device can identify scenario A and scenario B based on the acquired perception data, combined with the vehicle's driving parameters, it is predicted that the vehicle is closer to the left lane line of lane 1 and the manhole cover is closer to the right lane line of lane 1. The vehicle is likely to not pass through the road surface where the manhole cover is located when traveling in the current driving direction. Therefore, combined with the road surface characteristics of the first area and the vehicle's driving parameters, the vehicle control device can use scenario B as the first scenario and determine the target torque control information based on the first scenario.
[0167] In other embodiments, the vehicle control device may further obtain the difference in wheel speeds between the front and rear axles to assist in determining the first scenario the vehicle is in. For example, if the wheel speed difference ratio between the vehicle's front and rear wheels is between 0% and 10%, the vehicle is more likely to be on a normal road surface rather than in a special scenario. If the wheel speed difference ratio between the vehicle's front and rear wheels is between 10% and 30%, the vehicle is more likely to be in Scenario A, Scenario B, Scenario C, Scenario D, or Scenario E as shown in Table 1. If the wheel speed difference ratio between the vehicle's front and rear wheels is between 30% and 100%, the vehicle is more likely to be in Scenario F or Scenario G as shown in Table 1. If the wheel speed difference ratio between the vehicle's left and right wheels is between 0% and 10%, the vehicle is more likely to be on a normal road surface rather than in a special scenario. If the wheel speed difference ratio between the vehicle's left and right wheels is between 10% and 30%, the vehicle is more likely to be in Scenario A, Scenario B, Scenario C, Scenario D, or Scenario E as shown in Table 1. If the wheel speed difference ratio between the vehicle's left and right wheels is between 30% and 100%, the vehicle is more likely to be in Scenario F or Scenario G as shown in Table 1.
[0168] The different scenarios described above in conjunction with FIG13 are merely examples of different road conditions and actual driving conditions. In actual applications, the recognition of the first scenario may also be combined with other possible information, which will not be elaborated here.
[0169] In the embodiment of the present application, as an example, the target torque control information may include a target control strategy from one or more control strategies associated with the first scenario. Alternatively, the target torque control information may include adjusted values of corresponding control parameters calculated by the vehicle control device based on the one or more torque control strategies associated with the identified first scenario, including but not limited to an adjusted torque extreme value, an adjusted torque gradient, an adjusted torque distribution ratio, or an adjusted electro-hydraulic distribution ratio.
[0170] S330: Controlling the vehicle driving according to the target torque control information.
[0171] Taking the target torque control information including the adjusted values of the corresponding control parameters as an example, for example, if the first scene identified by the vehicle control device based on the road surface characteristics of the first area corresponds to the speed bump scene where code A is located, according to the corresponding speed bump level, the vehicle control device can calculate the adjusted torque distribution ratio and electro-hydraulic distribution ratio based on expressions (3) and (4) described above, and provide the adjusted torque distribution ratio and electro-hydraulic distribution ratio as target torque control information to relevant components of the vehicle to assist in controlling the vehicle to drive safely and smoothly.
[0172] Or for example, if the vehicle control device is in a first scene identified according to the road surface characteristics of the first area, which corresponds to the wet epoxy scene where code G is located, the vehicle control device can calculate the adjusted electro-hydraulic distribution ratio based on the expression (4) described above according to the corresponding wet epoxy level, and provide the adjusted electro-hydraulic distribution ratio as the target torque control information to the relevant components of the vehicle to assist in controlling the vehicle to drive safely and smoothly.
[0173] The vehicle control method of the present application has been described above in conjunction with the above-described method embodiments. In this method, a vehicle control device can identify a first scenario in which the vehicle is located based on sensory data and determine target torque control information based on at least one torque control strategy associated with the first scenario. This adaptively adjusts control parameters of relevant vehicle components, reduces vehicle instability, and thereby ensures smooth and stable driving.
[0174] In the above-mentioned method embodiments of the present application, the MDC, VCU, or VDC are used as examples for the vehicle control device, and the product form of the vehicle control device is not limited. In some embodiments, due to the more powerful computing capabilities of the cloud server, the vehicle control device can also be configured on the cloud server. The cloud server can obtain at least one driving parameter from the vehicle's sensor system via a communication network, and after calculating the adjusted control parameters to be provided to the different control components of the vehicle, send the adjusted control parameters of the control components to the vehicle via the communication network to achieve vehicle control. This will not be repeated here.
[0175] An embodiment of the present application also provides a vehicle control device, which can be used to execute the above-mentioned method embodiment. Relevant features can be found in the above-mentioned method embodiment and will not be repeated here.
[0176] As shown in FIG14 , in one example, the vehicle control device 1400 may include: an acquisition unit 1401 for acquiring road surface characteristics of a first area, wherein the first area includes an area that the vehicle will enter at a first moment in the future; a determination unit 1402 for determining target torque control information based on the road surface characteristics; and a control unit 1403 for controlling the vehicle's travel based on the target torque control information. Alternatively, in another example, the vehicle control device 1400 may include: an acquisition unit 1401 for acquiring first scenario information, wherein the first scenario information is used to indicate a first scenario to which the vehicle belongs; a determination unit 1402 for determining target torque control information based on at least one torque control strategy associated with the first scenario; and a control unit 1403 for controlling the vehicle's travel based on the target torque control information. For specific implementation methods, please refer to the method steps implemented by the vehicle control device in the above method embodiment, which will not be repeated here.
[0177] The division of the various units in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity, or they can be physically separated. In addition, the units in the device can be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of the various units of the device, where the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits. The hardware circuit can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units by designing the logical relationship of the components in the circuit. For another example, in another implementation, the hardware circuit can be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units. All units of the above devices can be implemented in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.
[0178] In an embodiment of the present application, a processor is a circuit with a signal processing capability. In one implementation, the processor may be a circuit with instruction reading and execution capability, such as a CPU, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.
[0179] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.
[0180] In addition, the various units in the above devices can be fully or partially integrated together, or can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the various units of the device. The type of the at least one processor can be different, for example, including a CPU and FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.
[0181] In a simple embodiment, those skilled in the art may conceive that the vehicle control devices in the above embodiments may all adopt the form shown in FIG. 15 .
[0182] As shown in FIG15 , the apparatus 1500 includes at least one processor 1510 and a communication interface 1530. In an optional design, the apparatus 1500 may further include a memory 1520. The specific connection medium between the processor 1510 and the memory 1520 is not limited in the embodiments of the present application.
[0183] In the apparatus as shown in FIG. 15 , the processor 1510 may transmit data through the communication interface 1530 when communicating with other devices.
[0184] When the vehicle control device adopts the form shown in Figure 15, the processor 1510 in Figure 15 can call the computer execution instructions stored in the memory 1520, so that the device 1500 can execute any of the above method embodiments.
[0185] An embodiment of the present application also relates to a chip system, which includes a processor for calling a computer program or computer instructions stored in a memory so that the processor executes the method of any of the above embodiments.
[0186] In a possible implementation, the processor may be coupled to the memory through an interface.
[0187] In a possible implementation, the chip system may also directly include a memory, in which a computer program or computer instructions are stored.
[0188] For example, the memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache memory. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0189] An embodiment of the present application further relates to a processor, which is used to call a computer program or computer instruction stored in a memory so that the processor executes the method described in any of the above embodiments.
[0190] For example, in the embodiments of the present application, the processor is an integrated circuit chip with signal processing capabilities. For example, the processor can be an FPGA, a general-purpose processor, a DSP, an ASIC or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a CPU, a network processor (NP), a microcontroller unit (MCU), a PLD or other integrated chip, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0191] The embodiments of the present application may be provided as methods, systems, or computer program products.
[0192] In one possible implementation, an embodiment of the present application provides a computer-readable storage medium, which stores program code. When the program code runs on the computer, the computer executes the above method embodiment.
[0193] In a possible implementation, an embodiment of the present application provides a computer program product. When the computer program product is run on a computer, the computer is caused to execute the above method embodiment.
[0194] Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0195] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0196] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0197] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these changes and variations. In the various embodiments of the present application, unless otherwise specified or logically conflicting, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
Claims
1. A vehicle control method, characterized in that: include: Acquire road surface characteristics of a first area, wherein the first area includes an area that the vehicle will enter at a first moment in the future; determining target torque control information according to the road surface characteristics; The vehicle is controlled to travel according to the target torque control information.
2. The method according to claim 1, characterized in that The determining the target torque control information according to the road surface characteristics includes: Identifying a first scene in which the vehicle is located according to the road surface feature; The target torque control information is determined according to at least one torque control strategy associated with the first scenario.
3. The method according to claim 2, characterized in that The method further comprises: At least one torque control strategy associated with the first scenario is determined according to any one of the following methods: Determine at least one torque control strategy associated with the first scenario according to the first information, wherein the first information is used to describe the association between different road scenarios and different torque control strategies; or At least one torque control strategy associated with the first scenario is determined according to a first parameter value associated with the first scenario, wherein the first parameter value is used to characterize the degree of influence of road features in the first area on driving stability of the vehicle.
4. The method according to claim 3, characterized in that The first parameter value includes a road adhesion coefficient and / or a slip ratio.
5. The method according to any one of claims 2 to 4, characterized in that: The at least one torque control strategy associated with the first scenario is used to adjust at least one of the following control parameters: Total torque value; torque gradient; inter-axle torque distribution ratio; or brake electro-hydraulic distribution ratio.
6. The method according to claim 5, characterized in that Each torque control strategy is associated with an adjustment coefficient, which is used to reduce the value of a control parameter to be adjusted for the torque control strategy.
7. The method according to any one of claims 2 to 6, characterized in that: The identifying, according to the road surface feature, a first scene in which the vehicle is located, comprises: The road surface feature is matched with at least one item of scene information to identify the first scene, wherein the scene information is used to describe a road surface scene, the area corresponding to the first scene includes a first road surface feature, a second parameter value associated with the first road surface feature is greater than or equal to a first threshold, and the second parameter value is used to characterize the degree of influence of the first road surface feature on the driving stability of the vehicle.
8. The method according to claim 7, characterized in that The method further comprises: receiving the at least one item of scene information from a cloud server; or, The at least one item of scene information is received from a user equipment UE.
9. The method according to any one of claims 2 to 8, characterized in that: The method further comprises: Acquiring driving parameters of the vehicle; The identifying, according to the road surface feature, a first scene in which the vehicle is located, comprises: A first scene in which the vehicle is located is identified according to the road surface features and the driving parameters.
10. The method according to any one of claims 1 to 9, characterized in that The obtaining of the road surface characteristics of the first area includes: The road surface characteristics of the first area are acquired by at least one sensor associated with the vehicle.
11. The method according to any one of claims 1 to 10, characterized in that The step of controlling the vehicle to travel according to the target torque control information includes: A control instruction is sent to a target component of the vehicle, wherein the target component includes at least one of the following: a motor control unit, a vehicle body electronic stability control system ESC, or a braking system.
12. A vehicle control method, characterized in that: include: Acquire first scene information, where the first scene information is used to indicate a first scene to which the vehicle belongs; determining target torque control information according to at least one torque control strategy associated with the first scenario; The vehicle is controlled to travel according to the target torque control information.
13. The method according to claim 12, characterized in that The method further comprises: At least one torque control strategy associated with the first scenario is determined according to any one of the following methods: Determine at least one torque control strategy associated with the first scenario according to the first information, wherein the first information is used to describe the association between different road scenarios and different torque control strategies; or According to the first parameter value associated with the first scenario, at least one torque control strategy associated with the first scenario is determined, wherein The first parameter value is used to characterize the degree of influence of the road surface characteristics of the first area on the driving stability of the vehicle.
14. The method according to claim 13, characterized in that The first parameter value includes a road adhesion coefficient and / or a slip ratio.
15. The method according to any one of claims 12 to 14, characterized in that: The at least one torque control strategy associated with the first scenario is used to adjust at least one of the following control parameters: Total torque value; torque gradient; inter-axle torque distribution ratio; or brake electro-hydraulic distribution ratio.
16. The method according to claim 15, characterized in that Each torque control strategy is associated with an adjustment coefficient, which is used to reduce the value of a control parameter to be adjusted for the torque control strategy.
17. The method according to any one of claims 12 to 16, characterized in that: The obtaining of the first scene information includes: The first scene information is received from an intelligent driving domain control unit, wherein the first scene is obtained based on road surface feature recognition in a first area, and the first area includes an area that the vehicle will enter at a first moment in the future.
18. The method according to any one of claims 12 to 16, characterized in that: The method further comprises: Acquiring driving parameters of the vehicle; The obtaining of the first scene information includes: Scene recognition is performed according to the driving parameters and road surface features of a first area to obtain the first scene information, wherein the first area includes an area that the vehicle will enter at a first moment in the future.
19. The method according to any one of claims 12 to 18, characterized in that: The step of controlling the vehicle to travel according to the target torque control information includes: A control instruction is sent to a target component of the vehicle, wherein the target component includes at least one of the following: a motor control unit, a vehicle electronic stability control system ESC, or a braking system.
20. A vehicle control device, characterized in that: include: an acquisition unit, configured to acquire road surface characteristics of a first area, wherein the first area includes an area that the vehicle will enter at a first moment in the future; a determination unit, configured to determine target torque control information according to the road surface characteristics; A control unit is used to control the vehicle driving according to the target torque control information.
21. A vehicle control device, characterized in that: include: An acquisition unit, used to acquire first scene information, where the first scene information is used to indicate a first scene to which the vehicle belongs; a determining unit, configured to determine target torque control information according to at least one torque control strategy associated with the first scenario; A control unit is used to control the vehicle driving according to the target torque control information.
22. An electronic device, characterized in that: comprising a processor coupled to a memory: The processor is used to execute the computer program or instructions stored in the memory, so that the electronic device executes the method as claimed in any one of claims 1 to 11, or the electronic device executes the method as claimed in any one of claims 12 to 19.
23. A vehicle, characterized in that: The method comprises a unit for implementing the method according to any one of claims 1 to 11, or comprises a unit for implementing the method according to any one of claims 12 to 19.
24. A readable storage medium, characterized in that: The method comprises a program or an instruction, and when the program or the instruction is executed, the method according to any one of claims 1 to 11 is executed, or when the program or the instruction is executed, the method according to any one of claims 12 to 19 is executed.
25. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 11, or the computer is caused to execute the method according to any one of claims 12 to 19.
Citation Information
Patent Citations
Vehicle recovery system
CN104797480A
Torque control method and device of vehicle and vehicle
CN113370800A
Energy recovery control method and device, vehicle and storage medium
CN113635772A
Vehicle control method and device, automatic driving equipment and storage medium
CN114872702A
Systems and methods for monitoring off-road vehicles
US20210173399A1
Cited By
Vehicle torque determination method and device, computer equipment and storage medium
CN119898347A
Method for controlling vehicle powertrain based on obstacle detection
US12397775B2
Method for controlling vehicle powertrain based on obstacle detection
US20250074393A1
