Term ends Nov 24, 2026 · Medium confidence
20-year base term ends Jan 18, 2027
Why Medium: A parent in the chain could not be resolved.
No current holder resolved from the recorded chain.
Filed Aug 12, 2011 as application 13/208,932 · Granted Mar 3, 2015
Base term plus 830 days of patent term adjustment (USPTO delay) · capped by a resolved terminal disclaimer
Today
2007
2027
Clock starts
Jan 18, 2007
Jan 18, 2007
Term ends
Nov 24, 2026
Nov 24, 2026
Granted
Mar 3, 2015
Mar 3, 2015
base term
after the term ends
fee events
Updated Nov 22, 2026 · includes USPTO assignment data published Nov 21, 2026, status data published Nov 22, 2026 and grant & fee data published Nov 17, 2026 (weekly) · how we know
830
Days of term adjustment
Read from the USPTO patent term adjustment record, not recalculated here.
Capped
Terminal disclaimer
Resolved from the filed document, referencing US 8,017,075.
2 of 2
Maintenance fees paid
Two maintenance fees can end this term early, the ones due 3.5 and 7.5 years from grant; the third one's grace period runs past the term end. This counts the ones the record shows paid.
2
Family applications on record here
Applications sharing this one's continuity chain, as the file histories and patent records this site holds name them. The family may have others.
This patent's term runs 830 days past its 20-year base term on prosecution delay. A terminal disclaimer resolved from the filed document caps it earlier. 2 of 2 maintenance fees are paid so far. Confidence: Medium. from the record
How we calculated this date
One row per rule, each showing its own input and what it did to the date. A step we could not verify says so instead of resolving itself.
| Step | Input | Date after this step | Confidence |
|---|---|---|---|
| Base term, 20 years from filing | Clock starts Jan 18, 2007, when application 11/654,599, the earliest non-provisional in its chain, was filed (this one was filed Aug 12, 2011); a parent in its chain could not be resolved (the next row) | Jan 18, 2027 | High confidence |
| Continuity chain | A parent in the chain could not be resolved | dated from this application's own claim | Medium confidence |
| Patent term adjustment | +830 days, USPTO patent term adjustment record | Apr 27, 2029 | High confidence |
| Terminal disclaimer cap | Disclaimer resolved from the filed document (refs US 8,017,075) | capped to Nov 24, 2026 | High confidence |
| Patent term extension | None on file | no change | High confidence |
| Fee events | 2 of 2 maintenance fees paid | In force | High confidence |
| Computed term end | The steps above, in order | Nov 24, 2026 | Medium confidence |
This family
| US 8,017,075 | In force Nov 2026 | Nov 2026 |
| US 8,968,652 | this patent Nov 2026 | Nov 2026 |
Every application listed has its file history here. The family may have others.
Sources
Google Patents · The patent document at USPTO · Assignment records at USPTO
USPTO account required: This application in Patent Center · USPTO's maintenance fee lookup
Maintenance fee events come from USPTO's own fee records. Its fee lookup asks for the patent number and the application number.
What's changing
Nov 2026
Term ends Nov 24, 2026. No further fees fall due before then
Note
The 830 days of patent term adjustment (USPTO delay) are read from the USPTO record, not recalculated by us
Disclaimer cap
This term is capped by a terminal disclaimer resolved from the filed document, referencing US 8,017,075.
Citations
2
later US patents cite this one
That is below the median of utility patents granted in 2015 in our data, the only group it is compared against.
How we rank
Every date shows its work: the base term, any term adjustment or extension, any disclaimer cap, and the maintenance fee record, each with a confidence tier. How this record was built
Computed patent terms end on the dates shown. Related patents and pending applications may cover overlapping subject matter.
In force means the term is running and no lapse is on record. It is not a finding that the patent is valid.