Opposition · USPTO

Opposition 91227040

OtherUSPTO

Opposition 91227040 at USPTO between Sirius XM Radio Inc. and DEWESoft, LLC, over the mark SIRIUS, filed Mar 23, 2016. Status in the office record: other.

View SIRIUSGet this data via the API
Status
Other
Result
Other
Filed
Mar 23, 2016
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Sirius XM Radio Inc.

Company trademarks
Respondent

DEWESoft, LLC

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SIRIUS filing.

  1. SIRIUS filed

    Application 86444356 filed at the USPTO.

  2. Opposition filed

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

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
SIRIUSContested86444356USPTO
SIRIUSRelied on75769598USPTO
SIRIUSRelied on75778346USPTO
SIRIUS SATELLITE RADIORelied on75796701USPTO
SIRIUSRelied on75796898USPTO
SIRIUSXMRelied on85279859USPTO
SIRIUSXM SATELLITE RADIORelied on85279869USPTO
SIRIUSXM SATELLITE RADIORelied on85279879USPTO
SIRIUSXMRelied on85279884USPTO
SIRIUSXM READYRelied on85947612USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_7d8dcec7-02da-4649-8ec2-8d14aee1de13
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7d8dcec7-02da-4649-8ec2-8d14aee1de13",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91227040",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-03-23",
  "parties": [
    {
      "name": "Sirius XM Radio Inc.",
      "role": "opponent"
    },
    {
      "name": "DEWESoft, LLC",
      "role": "respondent"
    }
  ]
}