Hitachinaka, Japan

Takeshi Eto

This inventor holds 2 USPTO granted patents. Top assignee: Hitachi Astemo Ltd.. Active years: 2026.

IDiyas Innovation Intelligence. (2026). Inventor Profile: Takeshi Eto. Retrieved from https://idiyas.com/inventor/takeshi-eto

Data source: USPTO (United States Patent and Trademark Office) public patent records. Weekly synchronization. How IDiyas builds this profile

Calculating rank

% Patents Active = 50.0

Average Co-Inventor Count = 2.0

ph-index = 1


Company Filing History:


Years Active: 2026

Loading Chart...
2 patents (USPTO):Explore Patents

Title: Takeshi Eto and His Work on Engine Control Technology.

Introduction

Takeshi Eto is an inventor associated with Hitachinaka, Japan, and Hitachi Astemo Ltd. His patent work concerns control technology for estimating intake-air flow in an internal combustion engine.

Latest Patents

Eto is credited with 1 patent, titled “Internal Combustion Engine Control Device.” The invention describes an electronic control unit that repeatedly estimates intake-air flow. It records flow-sensor readings and timestamps, then uses those records to determine an integration period matching the current calculation interval. The device calculates the integrated intake-air mass over that period and uses it to estimate the air-flow rate.

Career Highlights

Eto’s listed patent highlights his contribution to engine-control systems, particularly the timing and processing of sensor data used to estimate intake-air flow. He is associated with Hitachi Astemo Ltd.

Collaborations

Shinya Matohara is identified as Eto’s coworker. The available information does not specify whether Matohara collaborated with him on the patent.

Conclusion

Takeshi Eto’s patent focuses on using timestamped sensor measurements to improve intake-air-flow estimation in internal combustion engine control.

Profile summary based on public USPTO records.
Data Sources: USPTO Patent Grant XML, Patent Center, EPO & CIPO • Normalized by IDiyas Innovation Graph. Methodology & provenance architecturePlease report any incorrect information to [email protected]
Loading…