# US 12,602,221 B2 · Software component update system, and software component update method

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

- Number: US 12,602,221 B2
- Document ID: US12602221B2
- Status: Granted
- Kind: B2
- Application number: 18/550,882
- Filed: 2022-01-25
- Published: 2024-03-14
- Granted: 2026-04-14
- Earliest claimed: 2021-06-28
- Assignees: Hitachi Astemo, Ltd.
- Applicants: Hitachi Astemo, Ltd.
- Inventors: Miki Yamada; Takafumi Suzuki; Takashi Matsubara
- Web page: https://patentgrep.com/patent/US12602221B2

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/36: Software reuse
- G06F 8/70: Software maintenance or management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A software component update system is connected to a first database and a second database and includes a component tree rebuilding unit that rebuilds a software component tree of the second database on the basis of tag information and software component tree information of the first database; a component extraction unit that specifies the software components of the second database requiring update mirroring, on the basis of the rebuilt software component tree; and a file update unit that updates the software component file of the specified software components.

## Claims

### Claim 1

A software component update system configured by a computer including a processor and a memory, the computer connected to a first database and a second database that store software component tree information representing a plurality of software components in a tree format, tag information representing respective attributes of the software components, and a software component file including design information and a source code that constitute the software components, the software component update system including:
a component tree rebuilder configured to rebuild rebuilding unit that rebuilds a software component tree of the second database based on the tag information, tag selection information defining sharing tags and non-sharing tags, and the software component tree information of the first database, the software component tree information defining constraint information associated with the tag information;
a component extractor configured to specify the software components of the second database requiring update mirroring, based on the rebuilt software component tree; and
a file updater configured to update the software component file of the specified software components.

### Claim 2 (depends on 1)

The software component update system according to claim 1,
wherein each of the first database and the second database store tag selection information in which a combination of the tag information for specifying software components to be managed is recorded.

### Claim 3 (depends on 1)

The software component update system according to claim 1,
wherein the file updater is configured to generate display data for displaying, on a screen, the software component tree information and difference information for before and after the software component update.

### Claim 4

A software component update method executed by a computer including a processor and a memory, wherein the computer is connected to a first database and a second database that store software component tree information representing a plurality of software components in a tree format, tag information representing respective attributes of the software components, and a software component file including design information and a source code that constitute the software components, the software component update method including:
rebuilding, by a component tree rebuilder, the software component tree of the second database based on the tag information, tag selection information defining sharing tags and non-sharing tags, and the software component tree information of the first database, the software component tree information defining constraint information associated with the tag information;
specifying, by a component extractor, the software components of the second database requiring update mirroring, based on the rebuilt software component tree; and
updating, by a file updater, the software component file of the specified software components.

### Claim 5 (depends on 4)

The software component update method according to claim 4,
wherein each of the first database and the second database store tag selection information in which a combination of the tag information for specifying software components to be managed is recorded.

### Claim 6 (depends on 4)

The software component update method according to claim 4, further comprising:
generating, by the file updater, display data for displaying, on a screen, the software component tree information and difference information for before and after the software component update.