Opposition · USPTO

Opposition 91190119

OtherUSPTO

Opposition 91190119 at USPTO between Intel Corporation and Allsun Corporation, over the mark DHF INTELLVISION, filed May 7, 2009. Status in the office record: other.

Status
Other
Result
Other
Filed
May 7, 2009
Marks involved
35
Parties

Who is involved

The parties as named in the office record.

Opponent

Intel Corporation

Company trademarks
Respondent

Allsun Corporation

Timeline

How the case has moved

Dates from the USPTO record and the DHF INTELLVISION filing.

  1. DHF INTELLVISION filed

    Application 77520786 filed at the USPTO.
  2. Opposition filed

    Intel Corporation started opposition 91190119 at USPTO against DHF INTELLVISION.
Marks

Marks involved

1 contested mark, 34 marks the challenger relies on.

MarkRoleApplicationOffice
DHF INTELLVISIONContested77520786USPTO
INTELRelied on72325488USPTO
INTELRelied on72384319USPTO
INTELRelied on72384320USPTO
INTELRelied on73035122USPTO
INTELRelied on73794951USPTO
INTEL INSIDERelied on74159673USPTO
INTELRelied on74225506USPTO
INTELRelied on74225623USPTO
INTEL INSIDERelied on75160103USPTO
INTELRelied on75160105USPTO
INTELRelied on75160106USPTO

+23 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_9beae111-a247-4634-9044-0d0955ae87da
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9beae111-a247-4634-9044-0d0955ae87da",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91190119",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-05-07",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "opponent"
    },
    {
      "name": "ALLSUN CORPORATION",
      "role": "respondent"
    }
  ]
}