Cancellation 92092045
OtherUSPTO
Cancellation 92092045 at USPTO between PopSockets LLC and Zheng, Jiezhong, over the mark POPLOCK, filed Jun 22, 2026. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jun 22, 2026
- Marks involved
- 23
Parties
Who is involved
The parties as named in the office record.
Respondent
Zheng, Jiezhong
Timeline
How the case has moved
Dates from the USPTO record and the POPLOCK filing.
POPLOCK filed
Application 98672120 filed at the USPTO.POPLOCK registered
Cancellation filed
PopSockets LLC started cancellation 92092045 at USPTO against POPLOCK.
Marks
Marks involved
1 contested mark, 22 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| POPLOCK | Contested | 98672120 | USPTO |
| POPSOCKETS | Relied on | 86149688 | USPTO |
| POPSOCKETS | Relied on | 87198127 | USPTO |
| POPSOCKETS | Relied on | 87674518 | USPTO |
| POP | Relied on | 87726998 | USPTO |
| POPTIVISM | Relied on | 88000525 | USPTO |
| POP | Relied on | 88152124 | USPTO |
| POP | Relied on | 88152128 | USPTO |
| POPGRIP | Relied on | 88168157 | USPTO |
| POPTOP | Relied on | 88168160 | USPTO |
| POPWALLET | Relied on | 88168161 | USPTO |
| POPMINIS | Relied on | 88168164 | USPTO |
+11 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_6d08780d-1207-467a-851b-38ce6deaddf4
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_6d08780d-1207-467a-851b-38ce6deaddf4",
"object": "proceeding",
"proceeding_type": "cancellation",
"proceeding_number": "92092045",
"status": "other",
"office_code": "US",
"filed_date": "2026-06-22",
"parties": [
{
"name": "PopSockets LLC",
"role": "petitioner"
},
{
"name": "ZHENG, JIEZHONG",
"role": "respondent"
}
]
}