Open protocol for authentication and key establishment with privacy
US H002,270 In forceTerm ends Jul 9, 2030 · Low confidence
20-year base term ends Jul 9, 2030
Jul 9, 2010
Jul 9, 2030
Jun 5, 2012
How we calculated this date
| Step | Input | Date after this step | Confidence |
|---|---|---|---|
| Base term, 20 years from filing | Clock starts Jul 9, 2010, when this application, 12/803,968, was filed | Jul 9, 2030 | High confidence |
| Continuity chain | Every parent in the chain resolved | no change | High confidence |
| Patent term adjustment | No term adjustment record on a grant after 2005, so none is added | no change | Medium confidence |
| Terminal disclaimer cap | None on record | no cap applied | High confidence |
| Patent term extension | None on file | no change | High confidence |
| Fee events | No fee events in USPTO's record of this patent. A gap in the record, not evidence of lapse | In force | Medium confidence |
| Computed term end | The steps above, in order | Jul 9, 2030 | Low confidence |
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.