Cancellation · USPTO

Cancellation 92080747

OtherUSPTO

Cancellation 92080747 at USPTO between Intel Corporation and Navitent, Inc., over the mark DEEPERINTEL, filed Oct 10, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 10, 2022
Marks involved
33
Parties

Who is involved

The parties as named in the office record.

Petitioner

Intel Corporation

Company trademarks
Respondent

Navitent, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the DEEPERINTEL filing.

  1. DEEPERINTEL filed

    Application 90803818 filed at the USPTO.
  2. DEEPERINTEL registered

  3. Cancellation filed

    Intel Corporation started cancellation 92080747 at USPTO against DEEPERINTEL.
Marks

Marks involved

1 contested mark, 32 marks the challenger relies on.

MarkRoleApplicationOffice
DEEPERINTELContested90803818USPTO
INTELRelied on72384319USPTO
INTELRelied on72384320USPTO
INTELRelied on73035122USPTO
INTELRelied on74225506USPTO
INTELRelied on74225623USPTO
INTELRelied on75160105USPTO
INTELRelied on75160106USPTO
INTELRelied on75163576USPTO
INTELRelied on75349837USPTO
INTELRelied on75371362USPTO
INTELRelied on75371363USPTO

+21 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_63885b3a-74ac-45ba-8aba-71b821101308
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_63885b3a-74ac-45ba-8aba-71b821101308",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92080747",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-10-10",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "petitioner"
    },
    {
      "name": "Navitent, Inc.",
      "role": "respondent"
    }
  ]
}