Cancellation · USPTO

Cancellation 92080205

OtherUSPTO

Cancellation 92080205 at USPTO between Amazon Technologies, Inc. and Zhu Lianyong, over the mark TOPAMZ, filed Jul 27, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 27, 2022
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Petitioner

Amazon Technologies, Inc.

Respondent

Zhu Lianyong

Timeline

How the case has moved

Dates from the USPTO record and the TOPAMZ filing.

  1. TOPAMZ filed

    Application 97044839 filed at the USPTO.
  2. TOPAMZ registered

  3. Cancellation filed

    Amazon Technologies, Inc. started cancellation 92080205 at USPTO against TOPAMZ.
Marks

Marks involved

4 contested marks, 16 marks the challenger relies on.

MarkRoleApplicationOffice
TOPAMZContested97044839USPTO
AMZLANDContested97050759USPTO
AMZSTOREContested97080361USPTO
AMZCHOICEContested97109660USPTO
AMAZONRelied on75981644USPTO
AMAZONRelied on77572206USPTO
AMAZONRelied on77572552USPTO
AMAZONRelied on78005143USPTO
AMAZONRelied on86315391USPTO
AMAZONRelied on86315405USPTO
AMAZON BASICSRelied on86508761USPTO
AMAZONRelied on86983875USPTO

+8 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_ebdd3d14-9d07-4b6f-814a-c87ca8fbc843
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ebdd3d14-9d07-4b6f-814a-c87ca8fbc843",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92080205",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-07-27",
  "parties": [
    {
      "name": "Amazon Technologies, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Zhu Lianyong",
      "role": "respondent"
    }
  ]
}