# US 2025/0165378 A1 · Electronic control device and authentication method

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0165378 A1
- Document ID: US20250165378A1
- Status: Published application
- Kind: A1
- Application number: 18/839,822
- Filed: 2023-02-27
- Published: 2025-05-22
- Earliest claimed: 2022-03-10
- Assignees: Hitachi Astemo, Ltd.
- Applicants: Hitachi Astemo, Ltd.
- Inventors: Masayuki TAKEI; Daisuke FURUYA; Takuya KOBAYASHI
- Web page: https://patentgrep.com/patent/US20250165378A1

## CPC

- G06F 11/3648: {using additional hardware}
- G06F 21/572: {Secure firmware programming, e.g. of basic input output system [BIOS]}
- G06F 21/44: Program or device authentication
- G06F 21/73: by creating or determining hardware identification, e.g. serial numbers
- B60R 25/00: Fittings or systems for preventing or indicating unauthorised use or theft of vehicles (locks for vehicles E05B77/00-E05B85/00)
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- B60R: VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR

## Abstract

In an electric control device, a hardware ID unique to an electronic control device and a software ID associated with a software program are set in a ROM, and rewriting of data of the ROM by a data rewriting device is permitted depending on a result of collating the hardware ID with the software ID. Here, a software ID for development used during development of the electronic control device and a software ID for mass-production used during mass-production are set as the software ID in the ROM. Then, the hardware ID and the software ID for mass-production are acquired from the ROM, the IDs are collated, and if there is no conformity between the IDs, the software ID for development is further acquired from the ROM to collate the hardware ID with the software ID for development.

## Claims

### Claim 1

An electronic control device comprising a processor, a nonvolatile storage device that is electrically data rewritable, and an interface that enables communication with an external data rewriting device, the nonvolatile storage device being set with a hardware ID unique to the electronic control device and a software ID associated with a software program, and the data rewriting device being permitted to rewrite data of the nonvolatile storage device depending on a result of collating the hardware ID with the software ID,
wherein a software ID for development used during development of the electronic control device and a software ID for mass-production used during mass-production of the electronic control device are set as the software ID in the nonvolatile storage device, and
wherein the processor acquires the hardware ID and the software ID for mass-production from the nonvolatile storage device, collates the hardware ID with the software ID for mass-production, and when the hardware ID does not conform to the software ID for mass-production, further acquires the software ID for development from the nonvolatile storage device to collate the hardware ID with the software ID for development.

### Claim 2 (depends on 1)

The electronic control device according to claim 1, wherein the hardware ID is set in a region of the nonvolatile storage device that is not rewritable from outside, and the software ID is set in a region of the nonvolatile storage device that is rewritable from outside.

### Claim 3 (depends on 1)

The electronic control device according to claim 1 further comprising an interface that enables communication with an external debugging tool for development, wherein
the processor collates the hardware ID with an ID input to the debugging tool for development, and permits rewriting of data of the nonvolatile storage device by the debugging tool for development on the basis of a result of the collation.

### Claim 4 (depends on 1)

The electronic control device according to claim 1, wherein the hardware ID is generated using an output result of calculation performed with a predetermined calculation formula using, as an input, first information that is stored in the nonvolatile storage device and is readable from the outside and second information that is stored in the nonvolatile storage device and is unreadable from the outside.

### Claim 5

An authentication method executed by a processor of an electronic control device, the electronic control device comprising the processor, a nonvolatile storage device that is electrically data rewritable, and an interface that enables communication with an external data rewriting device, the nonvolatile storage device being set with a hardware ID unique to the electronic control device and a software ID associated with a software program, and the data rewriting device being permitted to rewrite data of the nonvolatile storage device depending on a result of collating the hardware ID with the software ID, the method causing the processor to perform the steps of:
acquiring, from the nonvolatile storage device in which a software ID for development used during development of the electronic control device and a software ID for mass-production used during mass-production of the electronic control device are set as the software ID, the hardware ID, and the software ID for mass-production, and collating the hardware ID with the software ID for mass-production; and when the hardware ID does not conform to the software ID for mass-production, further acquiring the software ID for development from the nonvolatile storage device, and collating the hardware ID with the software ID for development.
