Opposition · USPTO

Opposition 91263689

OtherUSPTO

Opposition 91263689 at USPTO between Intel Corporation and Core Pacific, Inc., over the mark INTEL HUMAN, filed Jul 17, 2020. Status in the office record: other.

View INTEL HUMANGet this data via the API
Status
Other
Result
Other
Filed
Jul 17, 2020
Marks involved
32
Parties

Who is involved

The parties as named in the office record.

Opponent

Intel Corporation

Respondent

Core Pacific, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the INTEL HUMAN filing.

  1. INTEL HUMAN filed

    Application 88618992 filed at the USPTO.

  2. Opposition filed

    Intel Corporation started opposition 91263689 at USPTO against INTEL HUMAN.
Marks

Marks involved

1 contested mark, 31 marks the challenger relies on.

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

+20 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_f50b7402-7f55-4219-8416-addeb1220870
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f50b7402-7f55-4219-8416-addeb1220870",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91263689",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-07-17",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "opponent"
    },
    {
      "name": "Core Pacific, Inc.",
      "role": "respondent"
    }
  ]
}