Opposition · USPTO

Opposition 91276791

OtherUSPTO

Opposition 91276791 at USPTO between Intel Corporation and Network Innovations Inc., over the mark FIELDINTELL, filed May 31, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
May 31, 2022
Marks involved
33
Parties

Who is involved

The parties as named in the office record.

Opponent

Intel Corporation

Company trademarks
Respondent

Network Innovations Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the FIELDINTELL filing.

  1. FIELDINTELL filed

    Application 79279327 filed at the USPTO.
  2. Opposition filed

    Intel Corporation started opposition 91276791 at USPTO against FIELDINTELL.
Marks

Marks involved

1 contested mark, 32 marks the challenger relies on.

MarkRoleApplicationOffice
FIELDINTELLContested79279327USPTO
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_43482260-0b98-4b07-ab70-21dc8f6af5a3
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_43482260-0b98-4b07-ab70-21dc8f6af5a3",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91276791",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-05-31",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "opponent"
    },
    {
      "name": "Network Innovations Inc.",
      "role": "respondent"
    }
  ]
}