"Powertrain system" is about as generic as a title gets, but the CPC tags on Toyota's grant US10958196B2 (issued March 23, 2021) — H02P 6/20 and H02P 6/10 (control of brushless/electronically commutated motors), H02K 47/04 (dynamo-electric converters), and B60L 50/61 (propulsion with on-board generation) — point at a series-hybrid drivetrain, and the claim reveals a specific and somewhat subtle control rule about when not to run the engine.

“A powertrain system includes an electric motor for driving a vehicle; a battery; an internal combustion engine; an electric generator; a motor inverter connected in parallel to the battery, and converting DC electric power of the battery into AC electric power and supplying it to the electric motor;…”— U.S. Patent No. 10,958,196 source

Independent claim 1 first builds the series-hybrid topology in detail: "an electric motor configured to drive a vehicle; a battery; an internal combustion engine; an electric generator configured to generate an electric power using a power of the internal combustion engine; a motor inverter connected in parallel to the battery, and configured to convert direct current electric power of the battery into alternating current electric power and supply the alternating current electric power to the electric motor; a generator inverter connected in parallel to the battery, and configured to convert alternating current electric power generated by the electric generator into direct current electric power and supply the direct current electric power to the battery; and a control device." Both inverters sit in parallel on the DC battery bus — the motor inverter pulling DC out to make traction AC, the generator inverter pushing engine-generated AC back as DC. That shared-bus arrangement is what sets up the problem the claim actually solves.

The novelty is the engine-suppression rule at the end of claim 1: "the control device is configured, where a charging rate of the battery is equal to or lower than a first threshold value, and a ripple current that is generated in association with an operation of the motor inverter and flows into the battery is equal to or greater than a second threshold value, not to start up the internal combustion engine for electric power generation using the electric generator." Read that carefully — it is counterintuitive. Normally a low state of charge is exactly the trigger to fire the engine and charge the pack. Here, even with SOC below threshold, the controller declines to start the engine if the motor inverter is already dumping high ripple current into the battery. The reason is battery health: ripple current from the inverter's switching already stresses and heats the cells, and stacking generator-side charging current on top of that ripple compounds the thermal and degradation load. So the claim trades a little immediate charging for cell protection, suppressing generation precisely in the operating region where the pack is already being churned.

Independent claim 2 is the dynamic mirror image and arguably the more interesting case. It covers the situation where the engine is already running to generate — started because SOC was low and ripple was below threshold — and then "a ripple current... becomes equal to or greater than a second threshold value." In that event the control device is configured "to stop the internal combustion engine." So claim 1 prevents starting under high ripple, and claim 2 commands stopping if ripple climbs past the threshold mid-generation. Together they make ripple current a first-class gating variable for the engine, in both the start and the stop direction — that bidirectional ripple gate is the defensible core of the grant.

The two dependents pin down how the controller knows ripple is high without necessarily measuring it directly. Claim 3 (depending on claim 1) and claim 4 (depending on claim 2) both recite that "where a rotational speed of the electric motor is within a first designated range and a torque of the electric motor is within a second designated range, [the controller is configured] to determine that the ripple current is equal to or greater than the second threshold value." That is a practical inference: certain motor speed/torque operating points are known to produce high inverter ripple, so the controller can infer the ripple condition from commanded speed and torque rather than from a noisy current measurement. It turns an electrical-stress threshold into a lookup over the motor operating map — cheaper and faster to implement.

The reason ripple current earns first-class status in this claim is worth spelling out, because it is the non-obvious move. On a shared DC bus, the motor inverter's switching imposes an alternating ripple on top of the battery's DC current; that ripple drives extra ohmic heating and accelerates degradation in the cells independent of the net charge or discharge. The series-hybrid topology of claim 1 puts both the motor inverter and the generator inverter in parallel on that same bus, so generator charging current and motor-side ripple coexist at the pack terminals. Toyota's rule recognizes that firing the engine to charge during a high-ripple operating point stacks two stressors on the battery at once, and so it suppresses generation there — accepting a lower state of charge briefly to protect cell life. H02P 6/20 and 6/10 (brushless-motor control) and H02K 47/04 (dynamo-electric conversion) place the apparatus accurately, but they give no hint that the inventive content is a battery-health veto over the engine; that is precisely the mismatch between a generic title and a specific claim. The speed/torque-window inference of claims 3 and 4 is the pragmatic glue — it lets the controller flag the high-ripple region from already-known motor commands instead of trusting a noisy direct ripple measurement, which is what makes the rule cheap enough to ship.

The verdict: enabling, examined, and far more specific than its bland title. The classifications correctly place it in brushless-motor control and on-board generation, but they understate the actual invention, which is a battery-protective engine-management rule keyed on inverter ripple current. The moat is the ripple-versus-SOC gating in both directions (claims 1 and 2), with the speed/torque-window inference (claims 3–4) as the implementation that makes the rule deployable. Report it as a ripple-current-gated series-hybrid generation-control claim, and treat the abstract's component list as topology, with the substance living in the "not to start up the internal combustion engine" and "to stop the internal combustion engine" conditions.