Cancellation · USPTO

Cancellation 92080641

OtherUSPTO

Cancellation 92080641 at USPTO between Rain Bird Corporation and Liu Shengyan, over the mark BIRDBELL, filed Sep 25, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 25, 2022
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Petitioner

Rain Bird Corporation

Company trademarks
Respondent

Liu Shengyan

Timeline

How the case has moved

Dates from the USPTO record and the BIRDBELL filing.

  1. BIRDBELL filed

    Application 88673171 filed at the USPTO.
  2. BIRDBELL registered

  3. Cancellation filed

    Rain Bird Corporation started cancellation 92080641 at USPTO against BIRDBELL.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
BIRDBELLContested88673171USPTO
RAINBIRDRelied on71616244USPTO
RAIN BIRDRelied on72177093USPTO
RAIN BIRDRelied on72359255USPTO
BIRDRelied on72427185USPTO
RAIN BIRDRelied on72429262USPTO
RAIN BIRDRelied on72429350USPTO
RAIN BIRDRelied on72431727USPTO
RAIN BIRDRelied on72431781USPTO
RAIN BIRDRelied on73776298USPTO
RAIN BIRDRelied on86543047USPTO
RAIN BIRDRelied on86543236USPTO
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_5f29eec8-9153-4ade-a23a-f1db59af0cb9
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5f29eec8-9153-4ade-a23a-f1db59af0cb9",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92080641",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-09-25",
  "parties": [
    {
      "name": "Rain Bird Corporation",
      "role": "petitioner"
    },
    {
      "name": "Liu Shengyan",
      "role": "respondent"
    }
  ]
}