Fuel cut control method and device, storage medium and processor

Abstract

This application discloses a fuel cut-off control method, device, storage medium, and processor. The method includes: monitoring the current intake air volume of the engine in response to initiating a fuel cut-off process; and controlling the engine's slow torque request value in stages based on the current intake air volume to control the engine's fuel cut-off process. This application solves the technical problem of reducing the power shock caused by untimely torque response in the air and fuel circuits and excessively rapid fuel supply recovery during fuel cut-off control in P2 configuration hybrid vehicles.

Description

Technical Field

[0001] This application relates to the field of hybrid electric vehicle technology, and more specifically, to a fuel cut-off control method, device, storage medium, and processor. Background Technology

[0002] P2 hybrid electric vehicles achieve torque coupling by placing the electric motor between the engine and the transmission. In hybrid driving conditions, to balance power and economy, an engine fuel cut-off strategy is often used to reduce fuel consumption. In related technologies, engine fuel cut-off control mainly relies on the coordinated action of air circuit torque (throttle adjustment) and spark circuit torque (ignition angle adjustment). When the vehicle is in a low torque demand scenario such as coasting or light braking and the fuel cut-off conditions are met, the vehicle controller (Hybrid Control Unit, or HCU) sends slow torque and fast torque requests to the engine management system (EMS) to execute fuel cut-off. During the fuel cut-off period, the intake air volume is increased to perform emission maintenance operations such as DPF regeneration, misfire self-learning, and post-oxygen diagnostics.

[0003] However, the relevant technology has significant drawbacks during fuel cut-off: First, the slow torque request issued by the HCU decreases too rapidly, causing the ignition torque, which is meant to compensate for the rapid response, to drop sharply. This results in an unsmooth engine response and can easily cause power shocks to the entire vehicle. Second, if the engine needs to increase intake air volume for emissions maintenance during fuel cut-off, restoring fuel supply at this time will cause another torque shock because the intake air volume is already high, leading to an excessively rapid recovery of fast torque. This affects the driving smoothness of the entire vehicle and the reliability of the powertrain. Summary of the Invention

[0004] This application provides a fuel cut-off control method, device, storage medium, and processor to at least solve the technical problem of how to reduce the power shock caused by untimely torque response of the gas circuit and the fuel circuit and excessively fast fuel supply recovery during the fuel cut-off control process in P2 configuration hybrid vehicles.

[0005] According to one aspect of the embodiments of this application, a fuel cut-off control method is provided, which may include: monitoring the current intake air volume of the engine in response to initiating a fuel cut-off process; and controlling the slow torque request value of the engine in stages according to the current intake air volume to control the fuel cut-off process of the engine.

[0006] Furthermore, before monitoring the engine's current intake air volume, the process includes: acquiring vehicle status parameters and user demand information; and determining whether the engine should initiate a fuel cut-off process based on the vehicle status parameters and user demand information.

[0007] Furthermore, the vehicle status parameters include at least one of vehicle speed information, gear information, and braking information; the user demand information includes at least one of accelerator pedal opening information, road resistance information, and wheel torque information.

[0008] Further, the system acquires the user-demanded torque value, the engine fuel cut-off threshold, and the original torque value of the engine air circuit; in response to the user-demanded torque value being less than the engine fuel cut-off threshold, it controls the engine to enter the fuel cut-off process; in response to the decrease in the original torque value of the engine air circuit, and the torque value corresponding to the current intake air volume being greater than a first comparison value, it controls the slow torque request value to decrease to the maximum value between the original torque value of the engine air circuit and the torque value corresponding to a first preset intake air volume, wherein the first comparison value is the sum of the torque value corresponding to the first preset intake air volume and a first threshold; in response to the slow torque request value being less than a second comparison value, it determines that the fuel cut-off process is complete, wherein the second comparison value is... The value is the difference between the engine fuel cut-off threshold and the second threshold. The second comparison value is less than the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume. In response to receiving an engine maintenance request and the number of engine maintenance requests is less than the third threshold, the current intake volume is controlled to increase and a timer is started to count a preset time period. In response to the completion of the timer and the torque value corresponding to the current intake volume decreasing after the increase to the torque value corresponding to the first preset intake volume, the slow torque request value is controlled to increase from the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume to close the fuel cut-off process and restore fuel supply.

[0009] Furthermore, the preset time period is a buffer time for engine maintenance requests.

[0010] Furthermore, engine maintenance requests include at least one of after-oxygen diagnostics, misfire self-learning, and exhaust gas regeneration.

[0011] According to another aspect of the embodiments of this application, a fuel cut-off control device is also provided. The device may include: a monitoring module for monitoring the current intake air volume of the engine in response to the start of the fuel cut-off process; and a control module for controlling the slow torque request value of the engine in stages according to the current intake air volume, so as to control the fuel cut-off process of the engine.

[0012] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein, when the program is running, it controls the device where the computer-readable storage medium is located to execute the fuel cut-off control method of the embodiments of this application.

[0013] According to another aspect of the embodiments of this application, a processor is also provided for running a program, wherein the program is executed by the processor to perform the fuel cut-off control method of the embodiments of this application.

[0014] According to another aspect of the embodiments of this application, a program product is also provided, the program product including computer instructions, wherein when the computer instructions are executed by a processor, they implement the fuel cut-off control method of the embodiments of this application.

[0015] According to another aspect of the embodiments of this application, a vehicle is also provided, which can be used to perform the fuel cut-off control method of the embodiments of this application.

[0016] In this embodiment, in response to the start of the fuel cut-off process, the current intake air volume of the engine is monitored, and the slow torque request value of the engine is controlled in stages according to the current intake air volume to control the fuel cut-off process of the engine. This achieves the technical effect of significantly improving the driving smoothness of the vehicle while cutting off fuel with low fuel consumption. It also solves the technical problem of how to reduce the power shock caused by untimely torque response of the air circuit and the fire circuit and excessively fast fuel supply recovery during the fuel cut-off control process of P2 configuration hybrid vehicles. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a flowchart of a fuel cut-off control method according to an embodiment of this application;

[0019] Figure 2 This is a phased control timing diagram of slow torque request and fast torque request during the engine fuel cut-off process according to an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of a fuel cut-off control device according to an embodiment of this application;

[0021] Figure 4 This is a structural block diagram of a computer terminal according to an embodiment of this application;

[0022] Figure 5 This is a block diagram of an electronic device for a fuel cut-off control method according to an embodiment of this application. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0025] According to an embodiment of this application, an embodiment of a fuel cut-off control method is provided. The steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0026] In the hybrid driving mode of P2 hybrid vehicles, when the vehicle is in scenarios with low driver torque demand, such as coasting or light braking, the vehicle control unit (HCU) triggers an engine fuel cut-off strategy to reduce fuel consumption. In related technologies, engine fuel cut-off typically requires the following conditions to be met simultaneously:

[0027] Low driver demand: The torque demanded by the driver is consistently below the throttle cut-off threshold (TorqLoss, which is dynamically calibrated with engine speed and is usually a negative value, such as -5 to -15 N·m).

[0028] Motor capacity limitations: Due to factors such as excessively high battery state of charge (SOC) and extreme temperatures, the motor's negative torque output capability is weakened, making it unable to independently meet the vehicle's reverse towing requirements;

[0029] Engine operating conditions permit: engine speed is above the idle speed threshold, there are no faults, and the emission after-treatment system is normal.

[0030] When the above conditions are met, the HCU sends two types of torque requests to the Engine Management System (EMS) via the CAN bus at a high frequency (e.g., 10ms): one is a filtered "slow torque request," used to quickly reduce the throttle opening to cut off the intake air; the other is a "fast torque request," used to adjust the ignition advance angle to compensate for torque deviation. Subsequently, the EMS stops fuel injection and enters fuel cut-off mode. During fuel cut-off, the EMS often actively increases the throttle opening (increasing the intake air volume) to raise the exhaust temperature, in order to meet the maintenance needs of the emission aftertreatment system, such as Diesel Particulate Filter (DPF) regeneration, misfire self-learning, and three-way catalytic converter efficiency diagnostics.

[0031] Although the aforementioned technologies can achieve basic fuel cut-off functionality, they suffer from the following technical defects in practical applications, directly affecting the driving smoothness and component reliability of the entire vehicle:

[0032] (1) Mismatch in torque response during fuel cut-off, causing power shock: In the relevant control strategies, the rate of decrease of the slow torque request (air circuit) issued by the HCU is often too fast. Due to the inherent delay in the torque response of the air circuit (about 100-150ms), while the torque response of the fuel circuit is extremely fast, when the slow torque request drops sharply, the EMS will force the fast torque request to change drastically in order to maintain torque balance. This asynchrony between the changes in torque of the air circuit and the fuel circuit leads to transient and violent fluctuations in the engine torque output, which in turn causes the entire vehicle power system to jerk and shock, reducing driving comfort.

[0033] (2) Incoordination between fuel supply restoration timing and intake air status exacerbates torque shock: During fuel cut-off, to meet the needs of the emission aftertreatment system (such as DPF regeneration and after-oxygen diagnostics), the EMS needs to actively increase the engine intake air volume (EngAirBase). If the HCU immediately commands the fuel supply to be restored due to increased driver demand, the engine torque will recover rapidly because the engine intake air volume is already high and the air circuit response is lagging. At this time, the fast torque request needs to rise rapidly from a low value to match the new torque demand. This combination of "high intake air volume + fast torque recovery" can easily cause a step increase in engine torque, resulting in severe power shock. Existing technologies lack a coordinated optimization mechanism for changes in intake air volume and torque recovery timing, and cannot effectively suppress such secondary shocks.

[0034] To address the aforementioned technical problems in related technologies, this application provides a fuel cut-off control method. Figure 1 This is a flowchart of a fuel cut-off control method according to an embodiment of this application. Figure 1 As shown, the method may include the following steps:

[0035] In step S102, in response to the start of the fuel cut-off process, the current intake air volume of the engine is monitored.

[0036] For example, when it is decided to start cutting off fuel, the HCU can begin to read and monitor the current intake air volume of the engine in real time in order to make subsequent control decisions based on this real-time data.

[0037] In one exemplary embodiment, before monitoring the engine's current intake air volume, the following steps are included:

[0038] Obtain vehicle status parameters and user demand information;

[0039] Determine whether the engine should initiate the fuel cut-off process based on vehicle status parameters and user demand information.

[0040] In one exemplary embodiment, the vehicle state parameters include at least one of vehicle speed information, gear information, and braking information;

[0041] User requirements information includes at least one of the following: accelerator pedal opening information, road resistance information, and wheel-end torque information.

[0042] For example, the HCU can determine whether the vehicle can currently cut off fuel based on the fuel availability condition identification conditions, and then determine the load range (high, medium, low load range, fuel cut-off range) that the driver should be in based on the driver's needs. If the vehicle is identified as entering the fuel cut-off range, the fuel cut-off process begins.

[0043] For example, the conditions for identifying fuel cut-off availability can be vehicle speed less than or equal to a comparison threshold, gear position less than or equal to a predetermined gear position within the comparison threshold, or braking less than or equal to a comparison threshold. If it is determined that fuel cut-off is possible, the load range is then determined based on information such as accelerator pedal opening, road resistance, and wheel torque. If it is determined that the engine should be in the fuel cut-off zone, it indicates that the engine can initiate the fuel cut-off process.

[0044] Step S104: Based on the current intake air volume, control the engine's slow torque request value in stages to control the engine's fuel cut-off process.

[0045] For example, when it is decided to start fuel cut-off, the HCU can control the engine's slow torque request value in stages according to the current intake air volume to control the engine's fuel cut-off process, thereby slowing down the engine's torque response speed and reducing the impact caused by torque changes during the fuel cut-off process.

[0046] In one exemplary embodiment, the engine's slow torque request value is controlled in stages based on the current intake air volume, including:

[0047] Obtain the user's required torque value, engine throttle cut-off threshold, and original torque value of the engine's air intake circuit;

[0048] In response to user demand, if the torque value is less than the engine fuel cut-off threshold, the engine is controlled to enter the fuel cut-off process.

[0049] In response to the decrease in the original torque value of the engine air circuit, if the torque value corresponding to the current intake volume is greater than the first comparison value, the control slow torque request value is reduced to the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume, wherein the first comparison value is the sum of the torque value corresponding to the first preset intake volume and the first threshold.

[0050] In response to the slow torque request value being less than the second comparison value, it is determined that the fuel cut-off process is completed, wherein the second comparison value is the difference between the engine fuel cut-off threshold and the second threshold, and the second comparison value is less than the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume;

[0051] In response to receiving an engine maintenance request, and if the number of engine maintenance requests is less than a third threshold, the current intake air volume is increased and a timer is started to count a preset time period.

[0052] In response to the completion of the timing, and the torque value corresponding to the current intake volume decreases after rising to the torque value corresponding to the first preset intake volume, the control slow torque request value rises from the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume, so as to close the fuel cut-off process and restore fuel supply.

[0053] For example, the HCU can obtain information such as the user-demanded torque value, engine fuel cut-off threshold (TorqLoss), and engine air circuit original torque value (HCU_SlowRaw) on the vehicle CAN bus network. When the user-demanded torque value is less than the engine fuel cut-off threshold, the engine enters the fuel cut-off process.

[0054] When the original torque value of the engine air circuit (HCU_SlowRaw) decreases and the torque value corresponding to the current intake volume is greater than the first comparison value, the slow torque request value (HCU_EMSSlowReq) can be controlled to decrease to the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume.

[0055] For example, when HCU_SlowRaw decreases, and the current intake air volume EngAirBase is greater than the torque corresponding to the engine's minimum intake air volume + 20, HCU_EMSSlowReq takes the maximum value between HCU_SlowRaw and the torque corresponding to the engine's minimum intake air volume (e.g., 30). This allows for a period of slow torque, where EngAirBase also decreases to the minimum intake air volume torque (30 Nm). This is because HCU_SlowRaw requests torque quickly, and HCU_EMSSlowReq decreases in stages to slow down the rate of EngAirBase's descent, ensuring that the rapid decrease in torque does not cause a shock. When HCU_EMSSlowReq is less than TorqLoss-10, the fuel cut-off is considered complete.

[0056] For example, when the HCU receives an engine maintenance request, and the number of such requests is less than a third threshold (e.g., 5 times), it actively increases the intake air volume and raises the EngAirBase to meet the engine's functional requirements. After the engine issues a maintenance request, this process takes a certain amount of time, so the HCU starts a timer (e.g., a 5-second timer). After the timer completes and the EngAirBase drops to the minimum intake air volume torque (30 Nm), it controls the HCU_EMSSlowReq to increase.

[0057] In one exemplary embodiment, the preset time period is a buffer time for engine maintenance requests.

[0058] In one exemplary embodiment, the engine maintenance request includes at least one of post-oxygen diagnostics, misfire self-learning, and exhaust gas regeneration.

[0059] Through the above embodiments, in response to the start of the fuel cut-off process, the current intake air volume of the engine is monitored, and the decrease and increase of the slow torque request value of the engine are controlled in stages according to the current intake air volume to control the start and stop of the fuel cut-off process. This effectively coordinates the timing difference between the air circuit response delay and the fire circuit rapid response, significantly reduces the drastic degree of torque change during the fuel cut-off process, thereby suppressing the power shock caused by torque fluctuation and improving driving smoothness.

[0060] Figure 2 This is a phased control timing diagram of slow torque request and fast torque request during the engine fuel cut-off process according to an embodiment of this application, as follows: Figure 2 As shown.

[0061] (i) The HCU determines whether the vehicle can be cut off from fuel based on the fuel cut-off availability conditions, and then determines the load range (high, medium, low load range, fuel cut-off range) based on the driver's needs. If the vehicle is identified as entering the fuel cut-off range, the fuel cut-off process begins.

[0062] For example, a vehicle can only enter a fuel-cut-off-available state if the following conditions are met simultaneously:

[0063] The vehicle speed is greater than 30 km / h, the actual gear is greater than or equal to 7, the brake pedal travel is greater than 10 mm, the engine speed is in the range of 1400 rpm to 3500 rpm, and the motor has the positive torque output capability to meet the requirements.

[0064] The condition that "the motor has a certain positive torque capability" is set as follows:

[0065] During fuel cut-off, if the EMS triggers functions such as exhaust gas regeneration, misfire self-learning, or post-oxygen diagnostics, it will actively increase the EngAirBase. If the driver presses the accelerator pedal to restore fuel supply at this time, the engine torque response may be too rapid due to the currently high EngAirBase, potentially causing a shock. Therefore, the system must wait for the EMS to adjust the EngAirBase back to the minimum intake air level before restoring fuel supply. However, during this waiting period, the driver's acceleration demand may continue to increase, and the engine cannot respond immediately due to the fuel cut-off state. Therefore, the positive torque capability of the electric motor is required to ensure that the driver's needs are met in a timely manner.

[0066] (ii) such as Figure 2 As shown in stage one, the torque changes in the air and fire circuits during the fuel cut-off process: When the driver's demand is less than the fuel cut-off threshold, the HCU requests fuel cut-off, the engine enters the fuel cut-off process, and HCU_SlowRaw decreases. When EngAirBase is greater than the engine's minimum intake air volume torque + 20, the slow torque demand HCU_EMSSlowReq takes the maximum value of HCU_SlowRaw and the engine's minimum intake air volume torque (30Nm), maintaining slow torque for a period of time, while EngAirBase also decreases to the minimum intake air volume torque (30Nm). The reason is that the HCU_SlowRaw request is relatively fast, and the decrease in EngAirBase is slowed down by HCU_EMSSlowReq in stages to ensure that the fast torque decrease is not too fast and causes a shock.

[0067] For example, during the restoration of fuel supply, the slow torque request (HCU_EMSSlowReq) gradually increases, causing EngAirBase to gradually increase, and the fast torque (HCU_EMSSFastReq) rises synchronously with EngAirBase. If the engine is in a condition that requires increasing EngAirBase, such as self-learning or post-oxygen diagnostics, the fuel cut-off state must be maintained for 0.5 seconds until EngAirBase returns to a normal level before fuel supply is restored. This is to avoid the fast torque rising too quickly and causing torque shock, ensuring that the fast torque does not increase too rapidly and cause a shock.

[0068] (iii) If Figure 2 As shown in stage two, HCU_EMSSlowReq continuously decreases, and when it becomes less than TorqLoss-10, the fuel cut-off is considered complete. Figure 2As shown in Phase 3, during the engine fuel cut-off process, if the HCU receives an engine maintenance request and the number of maintenance requests is less than 5, it actively increases the intake air volume and raises EngAirBase to meet the engine's functional requirements. After the engine issues a maintenance request, this process takes a certain amount of time, so the HCU starts a timer (e.g., a timer of 5 seconds). Even if the fuel cut-off is restored during this period (i.e., HCU_SlowRaw enters its rising edge), HCU_EMSSlowReq must continue to remain near TorqLoss to ensure the engine's functional requirements are met.

[0069] (iv) such as Figure 2 As shown in stage four, after the timing is completed and EngAirBase drops to the minimum intake torque (30Nm), HCU_EMSSlowReq is controlled to rise. During the process from fuel cut-off to fuel supply restoration, HCU_EMSFastReq always takes the minimum value between HCU_EMSSlowReq and EngAirBase, limiting the rate of increase of fast torque, thereby effectively mitigating the torque shock problem caused by HCU_EMSFastReq recovering too quickly.

[0070] Figure 3 This is a schematic diagram of a fuel cut-off control device according to an embodiment of this application, as shown below. Figure 3 As shown, the fuel cut-off control device 30 may include:

[0071] Monitoring module 32 is used to monitor the current intake air volume of the engine in response to the start-up fuel cut-off process;

[0072] The control module 34 is used to control the engine's slow torque request value in stages according to the current intake air volume, so as to control the engine's fuel cut-off process.

[0073] In one exemplary embodiment, the fuel cut-off control device 30 may further include:

[0074] The acquisition module is used to acquire vehicle status parameters and user request information;

[0075] The judgment module is used to determine whether the engine should start the fuel cut-off process based on vehicle status parameters and user demand information.

[0076] In one exemplary embodiment, the vehicle status parameters include at least one of vehicle speed information, gear information, and braking information; the user demand information includes at least one of accelerator pedal opening information, road resistance information, and wheel-end torque information.

[0077] In one exemplary embodiment, the control module includes:

[0078] The acquisition submodule is used to acquire the user's required torque value, engine fuel cut-off threshold, and original torque value of the engine air circuit.

[0079] The control submodule is used to: 1) control the engine to enter a fuel cut-off process in response to a user-requested torque value being less than the engine fuel cut-off threshold; 2) control the slow torque request value to decrease to the maximum value between the engine's original airflow torque value and the torque value corresponding to the current intake air volume being greater than a first comparison value, where the first comparison value is the sum of the torque value corresponding to the first preset intake air volume and a first threshold value; 3) determine that the fuel cut-off process is complete in response to the slow torque request value being less than a second comparison value, where the second comparison value is the difference between the engine fuel cut-off threshold and a second threshold value, and the second comparison value is less than the maximum value between the engine's original airflow torque value and the torque value corresponding to the first preset intake air volume; 4) control the current intake air volume to increase and start a timer to count a preset time period in response to receiving an engine maintenance request and the number of engine maintenance requests being less than a third threshold value; 5) control the slow torque request value to increase from the maximum value between the engine's original airflow torque value and the torque value corresponding to the first preset intake air volume after the timer has increased and decreased to the torque value corresponding to the first preset intake air volume, thereby closing the fuel cut-off process and restoring fuel supply.

[0080] In one exemplary embodiment, the preset time period is a buffer time for engine maintenance requests.

[0081] In one exemplary embodiment, the engine maintenance request includes at least one of post-oxygen diagnostics, misfire self-learning, and exhaust gas regeneration.

[0082] Embodiments of this application may provide a computer terminal, which may be any computer terminal device in a group of computer terminals. Optionally, in this embodiment, the aforementioned computer terminal may also be replaced by a mobile terminal or other terminal device.

[0083] Optionally, in this embodiment, the computer terminal may be located in at least one of a plurality of network devices in a computer network.

[0084] Optionally, Figure 4 This is a structural block diagram of a computer terminal according to an embodiment of this application, such as... Figure 4 As shown, the computer terminal 408 may include one or more (only one is shown in the figure) processors 402, memory 404, and transmission devices 406.

[0085] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the fuel cut-off control method and device in this application embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby realizing the aforementioned fuel cut-off control method. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to computer terminal 408 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0086] The processor can access information and applications stored in memory via a transmission device to perform the following steps: in response to the start of the fuel cut-off process, monitor the current intake air volume of the engine; based on the current intake air volume, control the engine's slow torque request value in stages to control the engine's fuel cut-off process.

[0087] Those skilled in the art will understand that Figure 4 The structure shown is for illustrative purposes only. Computer terminal 408 can also be a smartphone (such as an Android phone, iOS phone, etc.), tablet computer, handheld computer, mobile internet device (MID), PAD and other terminal devices. Figure 4 This does not limit the structure of the computer terminal 408 described above. For example, the computer terminal 408 may also include components that are more advanced than those described above. Figure 4 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 4 The different configurations shown.

[0088] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0089] According to an embodiment of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein the program executes the fuel cut-off control method in the above embodiments.

[0090] Optionally, in this embodiment, the computer-readable storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.

[0091] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: monitoring the current intake air volume of the engine in response to initiating the fuel cut-off process; and controlling the engine's slow torque request value in stages according to the current intake air volume to control the engine's fuel cut-off process.

[0092] According to an embodiment of this application, a processor is also provided for running a program, wherein the fuel cut-off control method in the above embodiments is executed when the program is run by the processor.

[0093] Optionally, in this embodiment, the computer terminal may be located in at least one of a plurality of network devices in a computer network.

[0094] In this embodiment, the computer terminal described above can execute program code for the following steps in the fuel cut-off control method: in response to initiating the fuel cut-off process, monitoring the current intake air volume of the engine; and controlling the engine's slow torque request value in stages according to the current intake air volume, so as to control the engine's fuel cut-off process.

[0095] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the fuel cut-off control method and device in this application embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby realizing the aforementioned fuel cut-off control method. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0096] The processor can access information and applications stored in memory via a transmission device to perform the following steps: in response to the start of the fuel cut-off process, monitor the current intake air volume of the engine; based on the current intake air volume, control the engine's slow torque request value in stages to control the engine's fuel cut-off process.

[0097] According to an embodiment of this application, a computer program product is also provided, which includes computer instructions, wherein when the computer instructions are executed by a processor, they implement the fuel cut-off control method in the above embodiments.

[0098] Embodiments of this application may provide an electronic device that may include a memory and a processor.

[0099] Figure 5 This is a block diagram of an electronic device for a fuel cut-off control method according to an embodiment of this application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present application described and / or claimed herein.

[0100] like Figure 5 As shown, device 500 includes a computing unit 501, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 502 or a computer program loaded from storage unit 508 into random access memory (RAM) 503. RAM 503 can also store various programs and data required for the operation of device 500. The computing unit 501, ROM 502, and RAM 503 are interconnected via bus 504. Input / output (I / O) interface 505 is also connected to bus 504.

[0101] Multiple components in device 500 are connected to I / O interface 505, including: input unit 506, such as keyboard, mouse, etc.; output unit 504, such as various types of monitors, speakers, etc.; storage unit 508, such as disk, optical disk, etc.; and communication unit 509, such as network card, modem, wireless transceiver, etc. Communication unit 509 allows device 500 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0102] The computing unit 501 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as the fuel cut-off control method. For example, in some embodiments, the fuel cut-off control method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by the computing unit 501, one or more steps of the fuel cut-off control method described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform the fuel cut-off control method by any other suitable means (e.g., by means of firmware).

[0103] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0104] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0105] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0106] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display, monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or pathball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0107] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0108] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0109] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0110] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0111] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0112] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0113] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0114] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0115] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A fuel cut-off control method, characterized in that, include: In response to the start-up fuel cut-off process, monitor the engine's current intake air volume; Based on the current intake air volume, the engine's slow torque request value is controlled in stages to control the engine's fuel cut-off process.

2. The method according to claim 1, characterized in that, Before monitoring the engine's current intake air volume, this includes: Obtain vehicle status parameters and user demand information; Based on the vehicle status parameters and the user demand information, it is determined whether the engine should initiate the fuel cut-off process.

3. The method according to claim 2, characterized in that, The vehicle status parameters include at least one of vehicle speed information, gear information, and braking information; The user demand information includes at least one of the following: accelerator pedal opening information, road resistance information, and wheel end torque information.

4. The method according to claim 1, characterized in that, Based on the current intake air volume, the engine's slow torque request value is controlled in stages, including: Obtain the user's required torque value, engine throttle cut-off threshold, and original torque value of the engine's air intake circuit; In response to the user's demand torque value being less than the engine fuel cut-off threshold, the engine is controlled to enter the fuel cut-off process; In response to a decrease in the original torque value of the engine air circuit, if the torque value corresponding to the current intake volume is greater than a first comparison value, the slow torque request value is controlled to decrease to the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume, wherein the first comparison value is the sum of the torque value corresponding to the first preset intake volume and a first threshold. In response to the slow torque request value being less than the second comparison value, it is determined that the fuel cut-off process is completed, wherein the second comparison value is the difference between the engine fuel cut-off threshold and the second threshold, and the second comparison value is less than the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume; In response to receiving an engine maintenance request, and the number of engine maintenance requests is less than a third threshold, the current intake air volume is increased and a timer is started to count a preset time period. In response to the completion of the timing, and the torque value corresponding to the current intake volume decreases after rising to the torque value corresponding to the first preset intake volume, the slow torque request value is controlled to rise from the maximum value between the original torque value of the engine air circuit and the torque value corresponding to the first preset intake volume, so as to close the fuel cut-off process and restore fuel supply.

5. The method according to claim 4, characterized in that, The preset time period is a buffer time for the engine maintenance request.

6. The method according to claim 4, characterized in that, The engine maintenance request includes at least one of post-oxygen diagnostics, misfire self-learning, and exhaust gas regeneration.

7. A fuel cut-off control device, characterized in that, include: The monitoring module is used to monitor the engine's current intake air volume in response to the start-up fuel cut-off process; The control module is used to control the slow torque request value of the engine in stages according to the current intake air volume, so as to control the fuel cut-off process of the engine.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1 to 6.

9. A processor, characterized in that, The processor is used to run a program, wherein the program is executed by the processor to perform the method according to any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the method described in any one of claims 1 to 6.

Images