Opposition 91240312
OtherUSPTO
Opposition 91240312 at USPTO between Exelon Corporation and Lishuang Xu, over the mark EXON, filed Mar 28, 2018. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Mar 28, 2018
- Marks involved
- 14
Parties
Who is involved
The parties as named in the office record.
Respondent
Lishuang Xu
Timeline
How the case has moved
Dates from the USPTO record and the EXON filing.
EXON filed
Application 87200300 filed at the USPTO.Opposition filed
Exelon Corporation started opposition 91240312 at USPTO against EXON.
Marks
Marks involved
1 contested mark, 13 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| EXON | Contested | 87200300 | USPTO |
| EXELON | Relied on | 75494120 | USPTO |
| EXELON | Relied on | 75979886 | USPTO |
| EXELON ENERGY | Relied on | 76115024 | USPTO |
| EXELON | Relied on | 77105327 | USPTO |
| EXELON | Relied on | 77494996 | USPTO |
| EXELON GENERATION | Relied on | 85568878 | USPTO |
| EXELON UTILITIES | Relied on | 85634521 | USPTO |
| EXELON UTILITIES | Relied on | 85634536 | USPTO |
| EXELON GENERATION | Relied on | 85634550 | USPTO |
| EXELON GENERATION | Relied on | 85634582 | USPTO |
| EXELON | Relied on | 85980323 | USPTO |
+2 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_8daacb4c-0501-4273-818f-13902a832c77
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_8daacb4c-0501-4273-818f-13902a832c77",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91240312",
"status": "other",
"office_code": "US",
"filed_date": "2018-03-28",
"parties": [
{
"name": "Exelon Corporation",
"role": "opponent"
},
{
"name": "Lishuang Xu",
"role": "respondent"
}
]
}