Opposition · USPTO

Opposition 91254694

OtherUSPTO

Opposition 91254694 at USPTO between Quantum Corporation and AI Incorporated, over the mark QUANTUM SLAM, filed Mar 16, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 16, 2020
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Quantum Corporation

Respondent

AI Incorporated

Timeline

How the case has moved

Dates from the USPTO record and the QUANTUM SLAM filing.

  1. QUANTUM SLAM filed

    Application 87821500 filed at the USPTO.
  2. Opposition filed

    Quantum Corporation started opposition 91254694 at USPTO against QUANTUM SLAM.
Marks

Marks involved

5 contested marks, 12 marks the challenger relies on.

MarkRoleApplicationOffice
QUANTUM SLAMContested87821500USPTO
QUANTUM OSContested87821512USPTO
QUANTUM SLAM OSContested87821521USPTO
QUANTUM SLAM OPERATING SYSTEMContested87821526USPTO
QUANTUMSLAMContested87897424USPTO
QUANTUMRelied on72327773USPTO
QUANTUMRelied on73127739USPTO
QUANTUMRelied on74242149USPTO
QUANTUMRelied on75052261USPTO
QUANTUMRelied on75387699USPTO
QUANTUMRelied on75601999USPTO
QUANTUMRelied on75604153USPTO

+5 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_5a059106-d451-4e29-ac48-bccdfd2896f4
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5a059106-d451-4e29-ac48-bccdfd2896f4",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91254694",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-03-16",
  "parties": [
    {
      "name": "Quantum Corporation",
      "role": "opponent"
    },
    {
      "name": "AI Incorporated",
      "role": "respondent"
    }
  ]
}