Opposition 91249082
OtherUSPTO
Opposition 91249082 at USPTO between Caterpillar Inc. and Shenzhen Leqikai Technology Co., Ltd., over the mark LUCKYCAT, filed Jun 19, 2019. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jun 19, 2019
- Marks involved
- 50
Parties
Who is involved
The parties as named in the office record.
Respondent
Shenzhen Leqikai Technology Co., Ltd.
Timeline
How the case has moved
Dates from the USPTO record and the LUCKYCAT filing.
LUCKYCAT filed
Application 88240613 filed at the USPTO.Opposition filed
Caterpillar Inc. started opposition 91249082 at USPTO against LUCKYCAT.
Marks
Marks involved
1 contested mark, 49 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| LUCKYCAT | Contested | 88240613 | USPTO |
| CAT | Relied on | 71575190 | USPTO |
| CAT | Relied on | 72137716 | USPTO |
| CAT | Relied on | 72164427 | USPTO |
| CAT | Relied on | 72174081 | USPTO |
| CAT | Relied on | 72181522 | USPTO |
| CAT | Relied on | 72299526 | USPTO |
| CAT | Relied on | 72452924 | USPTO |
| CAT | Relied on | 73001719 | USPTO |
| CAT | Relied on | 73392831 | USPTO |
| CAT | Relied on | 73392835 | USPTO |
| CAT | Relied on | 73392836 | USPTO |
+38 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_9e7e6228-0118-473e-8a4c-abb374d71292
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_9e7e6228-0118-473e-8a4c-abb374d71292",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91249082",
"status": "other",
"office_code": "US",
"filed_date": "2019-06-19",
"parties": [
{
"name": "Caterpillar Inc.",
"role": "opponent"
},
{
"name": "Shenzhen Leqikai Technology Co., Ltd.",
"role": "respondent"
}
]
}