Opposition · USPTO

Opposition 91284149

OtherUSPTO

Opposition 91284149 at USPTO between Sirius XM Radio Inc. and Ding Haifeng, over the mark XM, filed Mar 27, 2023. Status in the office record: other.

View XMGet this data via the API
Status
Other
Result
Other
Filed
Mar 27, 2023
Marks involved
25
Parties

Who is involved

The parties as named in the office record.

Opponent

Sirius XM Radio Inc.

Company trademarks
Respondent

Ding Haifeng

Timeline

How the case has moved

Dates from the USPTO record and the XM filing.

  1. XM filed

    Application 97186261 filed at the USPTO.

  2. Opposition filed

    Sirius XM Radio Inc. started opposition 91284149 at USPTO against XM.
Marks

Marks involved

1 contested mark, 24 marks the challenger relies on.

MarkRoleApplicationOffice
XMContested97186261USPTO
XMRelied on75539388USPTO
XMRelied on75827183USPTO
XM PREVIEWRelied on76002810USPTO
XMURelied on76183784USPTO
SIRIUSXM FANTASY SPORTS RADIORelied on85092782USPTO
SIRIUSXMRelied on85279859USPTO
SIRIUSXMRelied on85279884USPTO
XMWXRelied on85315877USPTO
SXMRelied on85413762USPTO
SXMRelied on85413766USPTO
SXM COMES ALIVERelied on85494441USPTO

+13 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_8f01652f-4527-4e5f-af2f-503cdc7cf8bb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8f01652f-4527-4e5f-af2f-503cdc7cf8bb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91284149",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-03-27",
  "parties": [
    {
      "name": "Sirius XM Radio Inc.",
      "role": "opponent"
    },
    {
      "name": "Ding Haifeng",
      "role": "respondent"
    }
  ]
}