Disaster response system and method
US 11,799,519 In forceTerm ends Jan 5, 2037 · From the USPTO record
20-year base term ends Jul 21, 2036
Jul 21, 2016
Jan 5, 2037
Oct 24, 2023
How we calculated this date
| Step | Input | Date after this step | Confidence |
|---|---|---|---|
| Base term, 20 years from filing | Clock starts Jul 21, 2016, when the earliest non-provisional application in its chain was filed (this one was filed Mar 3, 2021); a parent in its chain could not be resolved (the next row) | Jul 21, 2036 | 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 | +168 days, USPTO patent term adjustment record | Jan 5, 2037 | High confidence |
| Terminal disclaimer cap | None on record | no cap applied | High confidence |
| Patent term extension | None on file | no change | High confidence |
| Fee events | 0 of 3 maintenance fees paid | In force | High confidence |
| Computed term end | The steps above, in order | Jan 5, 2037 | From the USPTO record |
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.
Not on this page: the patent's family, its recorded assignments and its citation count. USPTO's assignment records, linked above, list every recorded assignment.
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.