Opposition 91188658
OtherUSPTO
Opposition 91188658 at USPTO between Sirius XM Radio Inc. and Jumeirah International LLC, over the mark SIRIUS, filed Feb 2, 2009. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Feb 2, 2009
- Marks involved
- 13
Parties
Who is involved
The parties as named in the office record.
Timeline
How the case has moved
Dates from the USPTO record and the SIRIUS filing.
SIRIUS filed
Application 77432020 filed at the USPTO.Opposition filed
Sirius XM Radio Inc. started opposition 91188658 at USPTO against SIRIUS.
Marks
Marks involved
1 contested mark, 12 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| SIRIUS | Contested | 77432020 | USPTO |
| SIRIUS | Relied on | 75432324 | USPTO |
| SIRIUS | Relied on | 75769598 | USPTO |
| SIRIUS RADIO | Relied on | 75777847 | USPTO |
| SIRIUS RADIO | Relied on | 75778344 | USPTO |
| SIRIUS | Relied on | 75778346 | USPTO |
| SIRIUS SATELLITE RADIO | Relied on | 75796701 | USPTO |
| SIRIUS | Relied on | 75796884 | USPTO |
| SIRIUS | Relied on | 75796898 | USPTO |
| GET SIRIUS | Relied on | 75838490 | USPTO |
| SIRIUS | Relied on | 75979592 | USPTO |
| SIRIUS READY | Relied on | 76297378 | USPTO |
+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_6392e7f3-c119-4fa7-abe2-49e0f0bb107a
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_6392e7f3-c119-4fa7-abe2-49e0f0bb107a",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91188658",
"status": "other",
"office_code": "US",
"filed_date": "2009-02-02",
"parties": [
{
"name": "Sirius XM Radio Inc.",
"role": "opponent"
},
{
"name": "Jumeirah International LLC",
"role": "respondent"
}
]
}