Opposition · USPTO

Opposition 91264286

OtherUSPTO

Opposition 91264286 at USPTO between Caterpillar Inc. and Liang Ping, over the mark BDCAT, filed Aug 18, 2020. Status in the office record: other.

View BDCATGet this data via the API
Status
Other
Result
Other
Filed
Aug 18, 2020
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Caterpillar Inc.

Company trademarks
Respondent

Liang Ping

Timeline

How the case has moved

Dates from the USPTO record and the BDCAT filing.

  1. BDCAT filed

    Application 88729449 filed at the USPTO.

  2. Opposition filed

    Caterpillar Inc. started opposition 91264286 at USPTO against BDCAT.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
BDCATContested88729449USPTO
CATERPILLARRelied on71052847USPTO
CATERPILLARRelied on71297791USPTO
CATERPILLARRelied on71386675USPTO
CATERPILLARRelied on71540643USPTO
CATERPILLARRelied on71540644USPTO
CATRelied on71575190USPTO
CATRelied on72174081USPTO
CATRelied on73392831USPTO
CATERPILLARRelied on73392834USPTO
CATRelied on74451720USPTO
CATERPILLARRelied on74451721USPTO

+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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_f143a0cd-dd0b-4fa4-916f-4215193ac361
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f143a0cd-dd0b-4fa4-916f-4215193ac361",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91264286",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-08-18",
  "parties": [
    {
      "name": "Caterpillar Inc.",
      "role": "opponent"
    },
    {
      "name": "Liang Ping",
      "role": "respondent"
    }
  ]
}