Opposition · USPTO

Opposition 91252245

OtherUSPTO

Opposition 91252245 at USPTO between IMAX Corporation and DRG 3 LLC, over the mark IMAX MEDICAL BILLING, filed Nov 13, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 13, 2019
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

IMAX Corporation

Respondent

DRG 3 LLC

Timeline

How the case has moved

Dates from the USPTO record and the IMAX MEDICAL BILLING filing.

  1. IMAX MEDICAL BILLING filed

    Application 88487829 filed at the USPTO.
  2. Opposition filed

    IMAX Corporation started opposition 91252245 at USPTO against IMAX MEDICAL BILLING.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
IMAX MEDICAL BILLINGContested88487829USPTO
IMAXRelied on72356735USPTO
IMAXRelied on73388162USPTO
MOVIES TO THE MAXRelied on74073899USPTO
IMAXRelied on75131600USPTO
THE IMAX EXPERIENCERelied on75230700USPTO
AN IMAX EXPERIENCERelied on75497758USPTO
TO THE MAXRelied on75840741USPTO
IMAX DMRRelied on76532215USPTO
AT THE MAXRelied on76632397USPTO
IMAXRelied on85135280USPTO
IMAXRelied on86524430USPTO

+4 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_6758bd3f-4b54-4463-a776-cb93be63b120
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6758bd3f-4b54-4463-a776-cb93be63b120",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91252245",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-11-13",
  "parties": [
    {
      "name": "IMAX Corporation",
      "role": "opponent"
    },
    {
      "name": "DRG 3 LLC",
      "role": "respondent"
    }
  ]
}