Cancellation 92064116
OtherUSPTO
Cancellation 92064116 at USPTO between Joy Carpets & Co., Inc. and Top-Joy International Trading (Shanghai) Co., Ltd., over the mark TOP JOY, filed Jul 19, 2016. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jul 19, 2016
- Marks involved
- 8
Parties
Who is involved
The parties as named in the office record.
Petitioner
Joy Carpets & Co., Inc.
Respondent
Top-Joy International Trading (Shanghai) Co., Ltd.
Timeline
How the case has moved
Dates from the USPTO record and the TOP JOY filing.
TOP JOY filed
Application 86611695 filed at the USPTO.TOP JOY registered
Cancellation filed
Joy Carpets & Co., Inc. started cancellation 92064116 at USPTO against TOP JOY.
Marks
Marks involved
1 contested mark, 7 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| TOP JOY | Contested | 86611695 | USPTO |
| JOY TUFF | Relied on | 76407085 | USPTO |
| JOY "IT'S A JOY" | Relied on | 76410946 | USPTO |
| JOY IN A BOX | Relied on | 76581874 | USPTO |
| JOY | Relied on | 77775801 | USPTO |
| TOTALLY TILES JOY "IT'S A JOY!" | Relied on | 78627007 | USPTO |
| JOY CARPETS | Relied on | 86069064 | USPTO |
| JOY | Relied on | 86156607 | USPTO |
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_89a632b0-afbb-46b6-9b51-9b9326982145
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_89a632b0-afbb-46b6-9b51-9b9326982145",
"object": "proceeding",
"proceeding_type": "cancellation",
"proceeding_number": "92064116",
"status": "other",
"office_code": "US",
"filed_date": "2016-07-19",
"parties": [
{
"name": "Joy Carpets & Co., Inc.",
"role": "petitioner"
},
{
"name": "Top-Joy International Trading (Shanghai) Co., Ltd.",
"role": "respondent"
}
]
}