System and method for connected vehicle security incident integration based on aggregate events
US 12,289,322 In forceTerm ends Feb 8, 2041 · From the USPTO record
20-year base term ends Jun 2, 2040
Jun 2, 2020
Feb 8, 2041
Apr 29, 2025
How we calculated this date
| Step | Input | Date after this step | Confidence |
|---|---|---|---|
| Base term, 20 years from filing | Clock starts Jun 2, 2020, when this application, 16/890,671, was filed | Jun 2, 2040 | High confidence |
| Continuity chain | Every parent in the chain resolved | no change | High confidence |
| Patent term adjustment | +251 days, USPTO patent term adjustment record | Feb 8, 2041 | 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 | Feb 8, 2041 | 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.