A patent infringement analysis can get close to a complete overlap and still fail because of one claim limitation.
That was the situation Sam faced as a senior patent analyst at a global database technology company. His team was assessing whether a potential database-related patent could support a broader defensive strategy.
The patent under review, USxxxxx309B2, covered aspects of a database system. Most of the relevant claim limitations could be mapped to the target product. One could not. The missing limitation was not just a gap in the available documentation. The technical evidence indicated that the target product handled that part of the process differently.
For the issued claim under review, the analysis therefore showed a non-overlap. The more useful finding came from understanding what the product did instead.
The infringement read stopped at one limitation
The relevant claim described a database system with a hardware processor, memory, a base table stored across shared storage devices, and several operations involving that table.
The portion of the claim provided for the analysis read as follows:
A system …:
… hardware processor; …
… memory …
… a base table … shared storage devices;
generating… based on the base table, … combining … in the base table …;
combining, …, the base table and …;
inspecting… to the base table…, the update … the base table;
applying, by … assigned by the …. service manager, … to the set … in the base table…;
and
executing, by the … service manager, … without accessing the base table.
Most of these elements were supported by evidence from the target product. One required step was not.
That distinction mattered. A complete claim requires support for every limitation. A close technical match cannot be treated as a complete one simply because the remaining elements line up. This is why claim-chart construction must tie product evidence to each limitation, rather than rely on an overall technical similarity.
The documentation showed that the missing step was not hidden behind poor public disclosure. The target product appeared to follow another process at that point. More searching was unlikely to turn that technical difference into an overlap.
If the only goal had been to determine whether the issued claim fully read on the target product, the analysis could have ended there.
Have a patent that does not fully read on a competitor’s product?
The client objective allowed a different question
Sam was not preparing an immediate infringement complaint. The company was reviewing patents that could support a defensive position in later negotiations or a possible countersuit.
That changed the type of analysis and conclusions that would be most useful. A clean non-overlap still had to be reported, but the analysis didn’t need to stop there.
The next step was not another broad search for the missing limitation. The analysis focused on the process the target product was actually using in its place.
This is where the non-overlap became useful. The gap was specific. The target product did not perform one claimed step, but it did perform an alternate step that could be traced through its technical documentation.
The target product used an alternate process already described in the patent
The target product documentation provided evidence of the process used in place of the missing claim step.
That implementation was then compared with the patent as a whole, not only with the issued claim language.
The alternate process appeared in the patent specification. This created a much more useful set of facts. The issued claim contained a limitation that did not map. The target product used a different process at that point. The patent specification already described that alternate process.
None of those facts changed the non-overlap conclusion for the issued claim. The required limitation was still missing. They did show that the target product operated within the technical territory the original patent disclosure had already contemplated.
However, now we have support from the specification. We also discovered that the patent in consideration had a pending application. This opened up a route for claim amendment in the application.
A pending family member changed the value of the finding
The patent family contained one more relevant fact. A related application was still pending.
That status mattered because the issued claim was fixed, while the pending application still gave prosecution counsel a live asset to assess.
The point was not that the issued claim could be rewritten. It could not. A pending application also did not guarantee that a new or amended claim would be allowed.
The opportunity was narrower and more useful. The target-product analysis had identified a specific implementation. That implementation appeared in the patent disclosure. A related application remained pending.
This created a prosecution question that did not exist at the start of the infringement review. Could the pending application support claim language directed to the disclosed implementation that the target product was using?
Any such route would still need review by prosecution counsel. The application as filed would need to support the proposed claim language. Prior art, prosecution history, claim scope, procedural status, and other patentability requirements would also matter.
The infringement analysis did not answer those prosecution questions. It identified the technical basis for asking them.
The failed claim mapping became input for prosecution
The finding was not reported as infringement. The issued claim still lacked one required limitation.
Instead, the analysis connected four pieces that had been sitting in different parts of the case. It identified the failed limitation, the product behavior that caused the failure, the corresponding disclosure in the patent specification, and the pending family member through which that disclosure could be assessed.
That connection made the recommendation more specific than a general instruction to review the patent family.
The technical work showed where the existing claim ended and where the target product began. The specification showed that the alternate route had already been contemplated. The family review showed that prosecution was still open in a related application.
The result was a concrete issue for prosecution counsel to evaluate, not a promise that claim scope could or should be changed.
The portfolio conversation changed
Sam presented the finding to the company’s management team. The team considered the prosecution route in the context of the broader defensive strategy.
According to the project information, the company later approached the business behind the target product. The discussion moved into licensing and then into negotiations around a possible settlement.
The non-overlap itself had not disappeared. The issued claim still did not completely read on the product.
What changed was the value of the analysis. The same technical difference that prevented a complete infringement mapping also pointed to a part of the original disclosure that could be assessed through a pending family member.
The client later began asking about amendment potential in other non-overlap matters. That shift in the questions was important. It meant a negative claim chart was no longer treated only as the end of an infringement review. In the right fact pattern, it could also trigger a family and specification check for a separate prosecution option.
A non-overlap can expose what the portfolio has not claimed yet
A non-overlap does not always end an infringement analysis. In this case, the missing claim limitation showed exactly how the target product differed from the issued claim. That difference led back to an implementation already described in the patent specification and, in turn, to a pending family member that could be assessed for a different claim position.
The issued claim itself remained a non-overlap. The value came from understanding why it failed and whether that technical difference created another option within the patent family.
This is also where infringement analysis can go beyond a yes-or-no claim chart. A detailed review can uncover technical gaps, alternative implementations, hidden product behavior, or family-level options that affect the broader patent strategy.
If you are dealing with a similar infringement question, a complex claim mapping exercise, or an uncertain overlap scenario, connect with the GreyB team that worked through this analysis to understand how this approach can be applied to your patent portfolio.