Opposition · USPTO

Opposition 91187365

OtherUSPTO

Opposition 91187365 at USPTO between Sirius XM Radio Inc. and Ersol Thin Film GmbH, over the mark SIRIUS, filed Nov 3, 2008. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 3, 2008
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Sirius XM Radio Inc.

Respondent

Ersol Thin Film GmbH

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SIRIUS filing.

  1. SIRIUS filed

    Application 79044958 filed at the USPTO.
  2. Opposition filed

    Sirius XM Radio Inc. started opposition 91187365 at USPTO against SIRIUS.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
SIRIUSContested79044958USPTO
SIRIUSRelied on75432324USPTO
SIRIUSRelied on75769598USPTO
SIRIUS RADIORelied on75777847USPTO
SIRIUS RADIORelied on75778344USPTO
SIRIUSRelied on75778346USPTO
SIRIUS SATELLITE RADIORelied on75796701USPTO
SIRIUSRelied on75796884USPTO
SIRIUSRelied on75796898USPTO
GET SIRIUSRelied on75838490USPTO
SIRIUSRelied on75979592USPTO
SIRIUS READYRelied on76297378USPTO

+1 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_1ffa86f8-8b41-4c7f-9754-b62e81a85f35
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1ffa86f8-8b41-4c7f-9754-b62e81a85f35",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91187365",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-11-03",
  "parties": [
    {
      "name": "Sirius XM Radio Inc.",
      "role": "opponent"
    },
    {
      "name": "Ersol Thin Film GmbH",
      "role": "respondent"
    }
  ]
}