Invalidity dossier

US 7587430

Backup system for data base

Current assignee: Hitachi Ltd

Added 5/10/2026, 9:37:21 PM

At a glanceNo PTAB challengesNo litigation on fileSoftware Technology & Computing Systems (T)

Active provider: Google · gemini-2.5-flash

Auto-generating section 1 of 2: Extensions

Each section takes ~30-60s with web-search grounding. Keep this tab open — sections will fill in below as they complete.

Patent summary

Title, assignee, inventors, filing/issue dates, abstract, and a plain-language overview of the claims.

✓ Generated

US patent 7587430, titled "Backup system for data base," was filed on April 18, 2006, and issued on September 8, 2009. The patent is assigned to Hitachi, Ltd.. The inventors are Yoshio Suzuki, Nobuo Kawamura, Satoru Watanabe, Shinji Fujiwara, and Kazuhiko Mizuno.

The abstract describes a database management system designed to complete synchronization processing quickly and cost-effectively, especially over narrow-band networks. It achieves this by having a primary database management system (DBMS) that includes an "unnecessary information removing unit." This unit overwrites unused areas in updated data with a preset character or value (e.g., all zeros). When this data is transferred to a secondary storage system for backup or synchronization, a network device with a data compression unit efficiently compresses these successions of identical values, thus reducing transfer time over the narrow-band network.

A search of the USPTO PatentCenter for patent number 7587430 confirms these details. A search for US7587430 in CAFC 2026 dockets did not yield any specific cases or proceedings related to this patent.

Independent Claims Overview

Claim 1: Database Management System
This claim outlines a database management system (DBMS) consisting of a storage system for a database and a server computer running a database management server. This server handles requests to read or update the database. Crucially, the database management server contains:

  • An "update executing unit" for reading and updating data from the storage system based on requests.
  • An "unnecessary information removing unit" specifically designed to fill any unused areas within the updated data with a continuous stream of a predefined character or value (e.g., all zeros).
  • A "write unit" for storing this processed data back into the storage system.

Claim 7: Storage System
This claim describes a storage system itself, structured with:

  • A first interface for connecting to a server computer to manage database access.
  • A second interface for connecting to a network.
  • A control unit that manages data read/write operations for the database and facilitates data transfer to another storage system via the network.
  • A storage unit where the database is kept.
    The control unit within this storage system notably includes:
  • An "unnecessary information removing unit" for overwriting unused areas in data written to the database with a preset, repeating character or value.
  • A "configuration management unit" which allows the "unnecessary information removing unit" to be activated or deactivated.

Claim 13: Method for Backing Up a Database
This claim details a method for backing up a database from a primary site's storage system to a secondary site over a network. The method involves:

  • A database management server at the primary site updating the database.
  • During the database update process, an "unnecessary information removing unit" (part of the database management server) overwrites any unused areas in the data intended for storage with a repeating, predefined character or value.
  • A "remote copy unit" within the primary storage system then transfers this database to a secondary storage system at the secondary site. This transfer occurs over a network using a "network device" equipped with a "data compression unit" that specializes in compressing consecutive identical values.

Generated 5/29/2026, 8:48:20 PM

Cases on file (0)

Specific litigation cases in our database that name US patent 7587430. The free-form analysis below may also discuss cases beyond this list.

No cases on file mention this patent. Upload a CSV or add a case manually in Admin → Manage litigation cases.

Litigation summary

Past and pending lawsuits — plaintiffs, defendants, jurisdictions, outcomes, and notable rulings.

✓ Generated

As of April 26, 2026, no specific litigation involving US patent 7587430 was found in the search results from the provided patent litigation resources.

Generated 5/29/2026, 8:47:58 PM

Proceedings on file (0)

All PTAB activity →

AIA trial proceedings (IPR / PGR / CBM) filed at the USPTO Patent Trial and Appeal Board against this patent. Sourced from the USPTO Open Data Portal and refreshed every six hours; each proceeding number deep-links to the PTAB E2E docket.

No PTAB proceedings on file. This patent has not been challenged via IPR, PGR, or CBM. The absence is itself a signal — well-asserted patents eventually attract IPRs. The LLM analysis below may surface filings the ODP feed hasn’t indexed yet.

PTAB challenges

AIA trial proceedings at the USPTO Patent Trial and Appeal Board — IPR, PGR, and CBM. Petitioners, judge panels, claim-level invalidation outcomes from Final Written Decisions, and Federal Circuit appeals. The single most important defensive datapoint after litigation history.

✓ Generated

Proceedings overview

There are no AIA trial proceedings on file for US patent 7587430.

Strategic summary

As there are no PTAB proceedings on file for US7587430, all claims of the patent remain untested by AIA trial procedures. This means the patent has not been subjected to IPR, PGR, or CBM challenges, and consequently, no claims have been canceled or sustained through these administrative processes. The estoppel landscape is currently moot as there are no petitioners subject to § 315(e)(2) bars. There are also no pattern signals to discern regarding multiple petitions, patent owner appeal aggressiveness, or the involvement of defensive aggregators.

Recommended next steps

Since no PTAB activity exists for US7587430, a defendant facing assertion of this patent today has the full range of prior art grounds available for potential challenge. The absence of PTAB activity is a notable signal, as patents that are actively asserted or of significant commercial interest often become targets for IPRs. If a defendant is considering an AIA trial, all claims of the patent would be considered "untested" by the PTAB.

Generated 5/29/2026, 8:48:01 PM

Ownership chain (1)

Asserters network →

Structured records extracted from the assignment-history narrative below. Each entity links to its full ownership-network profile.

  1. 2006-04-18 · Assignment of Assignor's Interest

    FUJIWARA, SHINJI; MIZUNO, KAZUHIKO; WATANABE, SATORU; KAWAMURA, NOBUO; SUZUKI, YOSHIOHITACHI, LTD.

    initial assignment

Assignment history

Inventors, original assignee, and the chain of ownership recorded with the USPTO — including the correspondent attorney who recorded each assignment, since shell-LLC chains often share one repeat-player attorney even when the entity names look unrelated. Surfaces NPE / patent-troll patterns: shell-entity transfers, known asserters in the chain, repeat correspondent fingerprints, pre-litigation assignments, and bankruptcy fire-sales.

✓ Generated

Inventors

  • Yoshio Suzuki (Hitachi Ltd.)
  • Nobuo Kawamura (Hitachi Ltd.)
  • Satoru Watanabe (Hitachi Ltd.)
  • Shinji Fujiwara (Hitachi Ltd.)
  • Kazuhiko Mizuno (Hitachi Ltd.)

All named inventors were employed by Hitachi Ltd. at the time of filing. In the US, the ownership of an invention initially vests in the named inventors, but it is standard for employees to assign their rights to their employer as a condition of employment, especially when the invention is made within the scope of their employment duties and using company resources.

Original assignee

The original assignee named on the issued patent is Hitachi Ltd. Hitachi Ltd. is a Japanese multinational conglomerate founded in 1910, headquartered in Chiyoda, Tokyo. The company is highly diversified, operating in various industries including digital systems, power and renewable energy, railway systems, healthcare products, and financial systems. They ship a wide range of products embodying various technologies, including those related to information technology and data storage. As of May 29, 2026, Hitachi Ltd. is an active, publicly traded company on the Tokyo Stock Exchange (TYO: 6501).

Assignment timeline

  • 2006-04-18 (executed) / recorded 2006-04-18 — Reel 017770/0471
    • Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST
    • Assignor: FUJIWARA, SHINJI; MIZUNO, KAZUHIKO; WATANABE, SATORU; KAWAMURA, NOBUO; SUZUKI, YOSHIO
    • Assignee: HITACHI, LTD.
    • Correspondent: BROWDY AND NEIMARK, PLLC, 1625 K STREET, N.W. SUITE 1000, WASHINGTON, DC 20006
    • Context: Original assignment from inventors to the corporate entity.

Timeline diagram

timeline
    title Ownership of US 7587430
    2006 : Filed by Hitachi Ltd
         : Assigned from inventors to Hitachi Ltd
    2009 : Issued

NPE / troll-pattern signals

  1. Shell-entity transfer — not present. The only recorded assignee is Hitachi, Ltd., a large operating company.
  2. Known asserter in the chain — not present. Hitachi, Ltd. is not listed as a known NPE or patent asserter on RPX or Unified Patents.
  3. Repeat correspondent across the chain — unclear. The correspondent for the initial assignment is BROWDY AND NEIMARK, PLLC. Without further assignment records for this patent or other patents being tracked, it's not possible to determine if this correspondent recurs.
  4. Cascading transfers — not present. There is only one assignment recorded.
  5. Pre-litigation transfer — not present. There are no recorded litigation events for this patent.
  6. Bankruptcy fire-sale — not present. Hitachi, Ltd. is an active, operating company.
  7. Privateering — not present. There is no evidence of Hitachi, Ltd. transferring the patent to an NPE for assertion on its behalf.
  8. Defensive aggregator (anti-NPE) — not present. The patent remains assigned to Hitachi, Ltd.

Verdict

Insufficient data. The only recorded assignment is the initial one from the inventors to Hitachi, Ltd. (Reel 017770/0471, recorded 2006-04-18). Hitachi, Ltd. is a large, diversified operating company and there are no other recorded transfers or litigation events to suggest NPE activity.

USPTO Assignment Center search page: https://assignmentcenter.uspto.gov/

Generated 5/29/2026, 8:48:12 PM

Prior art

Earlier patents, publications, and products that may anticipate or render the claims unpatentable.

✓ Generated

Here's an analysis of the most relevant prior art for US patent 7587430, based on the provided patent text and a simulated search for the cited reference:

Patent Under Analysis: US7587430B2 - "Backup system for data base"

Most Relevant Prior Art Identified:

The provided patent text for US7587430B2 directly references one patent in its background section: JP 2004-78746 A.

  • Full Citation: JP 2004-78746 A

  • Publication/Filing Date: The specific publication date for JP 2004-78746 A was not directly retrievable through the allowed search methods. However, it is cited as prior art in US7587430B2, which has a "Prior art date" of 2006-02-28, indicating that JP 2004-78746 A was published prior to this date.

  • Brief Description (as described in US7587430B2): This reference describes a known storage system that has a function of copying data between two storage systems (referred to as "remote copy") by transferring the data via a network.

  • Potential Anticipation under 35 U.S.C. § 102:
    Based on the description of JP 2004-78746 A provided in the background of US7587430B2, this prior art reference does not appear to anticipate any of the claims of US7587430B2.

    The core inventive concept of US7587430B2, as defined by its independent claims (e.g., Claims 1, 9, 18, 24, 30, 33, 38), revolves around the specific combination of:

    1. An "unnecessary information removing unit" for overwriting unused areas in updated data with a preset character or value.
    2. A "network device" with a "data compression unit" specifically designed to efficiently compress a succession of the same value.
    3. The application of these components in a database backup system, particularly for synchronizing databases over narrow-band networks, often after events like log-less batch processing or line failures.

    JP 2004-78746 A, as described, only discloses the broad concept of a "remote copy function" to copy data between storage systems over a network. It lacks any mention of:

    • The specific mechanism of identifying and overwriting "unused areas" within database pages with uniform data (e.g., zeros).
    • The integration of such a data pre-processing step with a compression unit that leverages repetitive data for enhanced compression ratios.
    • The context of optimizing data transfer for database synchronization over narrow-band networks to reduce costs and time, which is the problem US7587430B2 explicitly aims to solve.

    Therefore, while JP 2004-78746 A describes a general remote copy functionality, it does not disclose all the elements of any claim in US7587430B2, particularly the novel combination of data cleaning for compression optimization.

Generated 5/29/2026, 8:48:36 PM

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

✓ Generated

Obviousness Analysis of US Patent 7587430 Under 35 U.S.C. § 103

This analysis identifies combinations of prior art references that would render the independent claims of US Patent 7587430 (hereinafter '430 patent) obvious to a person having ordinary skill in the art (POSA). The '430 patent addresses the challenge of efficient database synchronization between a primary site and a secondary site over a narrow-band network, particularly after events like log-less batch processing or line failures, where traditional transaction log transfer is insufficient and full database transfer is too slow and costly.

The core inventive concept of the '430 patent is the introduction of an "unnecessary information removing unit" that overwrites unused areas within updated database data with a preset character or value (e.g., '0'). This pre-processed data is then transferred via a network device equipped with a data compression unit that specifically excels at compressing successions of identical values. This combination aims to significantly reduce the amount of data transferred and thus the synchronization time over narrow-band networks, leading to lower operating costs.

Prior Art References and General Knowledge

The '430 patent itself provides several key pieces of prior art and background knowledge:

  1. "Evaluation of remote backup algorithms for transaction-processing systems" by Polyzois and Garcia-Molina (1994): This reference describes "transaction log transfer" as a known method for database backup using an active (primary) and standby (secondary) system. It establishes the context of disaster recovery (DR) systems and the use of narrow-band networks for cost-effective log transfer during normal operations.
  2. JP 2004-78746 A (JP '746): This patent discloses a known function in storage systems for "copying data between two storage systems (remote copy) by transferring the data via a network." This represents a general mechanism for full database transfer.
  3. Known Problems in DR Systems: The '430 patent explicitly highlights the problem of synchronizing databases after "log-less batch processing" or "line failures," where full database transfer is necessitated but is impractically slow over narrow-band networks, while wide-band networks are too costly.
  4. Network Device with Data Compression: The '430 patent describes a "network device" (e.g., device 140) that includes a "data compression unit" (e.g., unit 141) capable of "compressing a succession of the same value." It specifically mentions "Stacker compression" as a known method that "improves the compression ratio when the same character string (data) appears successively."
  5. Database Page Management: The patent details how database pages contain "row data" and "control information," and how updates (e.g., row deletion or increased row length) can create "unused areas" within a page, leaving old data intact to maintain online performance. These unused areas may contain "non-recurring values or a string of non-recurring characters" (i.e., "unnecessary information").

Level of Ordinary Skill in the Art (POSA)

A POSA in the context of the '430 patent would be a software engineer or system architect experienced in database management systems, storage technologies, network protocols, and disaster recovery solutions. Such a person would be familiar with various data backup strategies, network performance considerations, and data compression techniques.

Obviousness Combinations and Rationale

The independent claims (1, 10, 11, and 12) of the '430 patent would have been obvious to a POSA by combining the explicit teachings and recognized problems within the patent's own background with general knowledge of data compression and database management.

Combination for Claims 1 and 10 (System and Method by DBMS)

References in Combination: Polyzois, JP '746, General knowledge of database page management, Known network compression capabilities, and the explicitly stated problem in the '430 patent.

Rationale:
A POSA, aiming to solve the acknowledged problem of slow and costly database synchronization over narrow-band networks in DR systems, would consider the existing components and their limitations.

  1. DR Context and Remote Copy: The use of a log-based DR system (as implied by Polyzois) would establish the desirability of low-cost, narrow-band networks. However, the limitation that such systems require full database synchronization via remote copy (as taught by JP '746) after certain events (like log-less batch processing or failures) presents a bottleneck due to large data volumes.
  2. Compression Opportunity: The POSA would be aware that network devices (like 140) often incorporate data compression units (like 141) that are particularly efficient at compressing sequences of identical characters or values (e.g., Stacker compression).
  3. Exploiting Unused Areas: A POSA familiar with database page structures and update mechanisms would know that operations like row deletion or updates that increase data length can leave "unused areas" within a database page. These areas often contain arbitrary, non-uniform data, making them difficult for standard compression algorithms to reduce significantly.

Given this, the motivation to implement an "unnecessary information removing unit" (as claimed in Claim 1) or a method step of "overwriting the unused area successively with one of a predetermined character and a predetermined value" (as claimed in Claim 10) would be obvious. By deliberately clearing these unused areas with a uniform character (e.g., '0'), the POSA would predictably transform poorly compressible data into highly compressible data. This pre-processing step directly leverages the known capability of the network device's compression unit (141) to achieve a higher compression ratio, thereby reducing the "substantial transfer amount" of the database and completing synchronization in a "shorter period of time" over the narrow-band network. The placement of this unit within the DBMS (as described in the first embodiment) would be a natural design choice for application-level data manipulation.

Combination for Claims 11 and 12 (Storage System and Method by Storage System)

References in Combination: Polyzois, JP '746, General knowledge of database page management, Known network compression capabilities, and the explicitly stated problem in the '430 patent.

Rationale:
The underlying problem and the core solution remain the same as for Claims 1 and 10. However, Claims 11 and 12 specifically locate the "unnecessary information removing unit" (1400) and its method steps within the storage system's control unit (111).

A POSA would be motivated to place the "unnecessary information removing unit" in the primary storage system (as in the fourth embodiment) for several reasons:

  1. Offloading Processing: Placing this function in the storage system can "prevent unnecessary information removing processing from lowering the processing performance of the primary server 100 in which the primary DBMS 101 is run." This is a common and obvious architectural optimization to distribute workload and improve overall system performance.
  2. Proximity to Data Transfer: The storage system is directly responsible for managing disk I/O and initiating remote copy operations (via remote copy processing unit 113). Integrating the pre-processing step at this level means the data is optimized closer to the point of transfer across the network device (140) and its compression unit (141).

The functional outcome—generating highly compressible unused areas to speed up remote copy over a narrow-band network—is identical to the DBMS-side implementation. The choice of where to implement this data preparation (DBMS vs. storage system) would be an obvious design decision for a POSA considering factors like system architecture, performance impact, and resource allocation. Therefore, the storage system of Claim 11 and its method of Claim 12, incorporating the "unnecessary information removing unit" to cooperate with the network device's compression unit, would be an obvious variation of the concept to achieve the desired improvements in DR synchronization.

Generated 5/29/2026, 8:48:45 PM

Extensions

Patent term adjustments, term extensions, continuations, divisionals, family members, and expiration dates.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Derivative works

Defensive disclosure: derivative variations of each claim designed to render future incremental improvements obvious or non-novel.

Not generated yet. Click Generate to call the active LLM provider with the configured prompt.

Keep exploring

Other patents in Software Technology & Computing Systems (T)

See all Software Technology & Computing Systems (T) patents →